Tools & Wizards About Us
prtg.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

prtg.com

Packet Pushers - Paessler PRTG Hosted Monitor

Page Load Speed

1.6 sec in total

First Response

30 ms

Resources Loaded

1 sec

Page Rendered

508 ms

prtg.com screenshot

About Website

Visit prtg.com now to see the best up-to-date PRTG content and also check out these interesting facts you probably never knew about prtg.com

Welcome, Packet Pushers fans! Find here all information about the hosted network monitoring solution Paessler PRTG ➤ Grab your special discount today!

Visit prtg.com

Key Findings

We analyzed Prtg.com page load time and found that the first response time was 30 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

prtg.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

prtg.com

30 ms

hosted-discount

260 ms

jquery-1.7.1.js

37 ms

module_67623384395_Fallback_Header_EN.min.css

74 ms

module_67642297150_Fallback_Footer_EN.min.css

219 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Prtg.com, 46% (28 requests) were made to Go.paessler.com and 18% (11 requests) were made to F.hubspotusercontent30.net. The less responsive or slowest element that took the longest time to load (344 ms) relates to the external source Go.paessler.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.4 kB (15%)

Content Size

501.1 kB

After Optimization

423.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prtg.com main page is 501.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 223.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 53.0 kB

  • Original 63.0 kB
  • After minification 59.7 kB
  • After compression 10.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 53.0 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 13.8 kB

  • Original 223.2 kB
  • After minification 209.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. PRTG images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 6.4 kB

  • Original 201.9 kB
  • After minification 201.9 kB
  • After compression 195.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-32%

Potential reduce by 4.2 kB

  • Original 13.0 kB
  • After minification 13.0 kB
  • After compression 8.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Prtg.com needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (50%)

Requests Now

48

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PRTG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

prtg.com

prtg.com

30 ms

hosted-discount

hosted-discount

260 ms

jquery-1.7.1.js

jquery-1.7.1.js

37 ms

module_67623384395_Fallback_Header_EN.min.css

module_67623384395_Fallback_Header_EN.min.css

74 ms

module_67642297150_Fallback_Footer_EN.min.css

module_67642297150_Fallback_Footer_EN.min.css

219 ms

otSDKStub.js

otSDKStub.js

46 ms

cookieHandling.min.js

cookieHandling.min.js

53 ms

roboto.min.css

roboto.min.css

249 ms

lightcase.min.js

lightcase.min.js

70 ms

onload.min.js

onload.min.js

273 ms

sticky-sidebar.min.js

sticky-sidebar.min.js

81 ms

layout.min.css

layout.min.css

74 ms

basic.css

basic.css

284 ms

hls.js@latest

hls.js@latest

45 ms

embed.js

embed.js

43 ms

project.js

project.js

120 ms

module_6099417555_Header_Replacement_Script_EN.min.js

module_6099417555_Header_Replacement_Script_EN.min.js

123 ms

module_5871670862_Footer_Replacement_Script_EN.min.js

module_5871670862_Footer_Replacement_Script_EN.min.js

152 ms

2990530.js

2990530.js

161 ms

index.js

index.js

183 ms

36d52041-4818-40f8-a238-6135ebae43be.json

36d52041-4818-40f8-a238-6135ebae43be.json

31 ms

location

location

138 ms

gtm.js

gtm.js

224 ms

paessler-logo-color.svg

paessler-logo-color.svg

113 ms

header-pphm.svg

header-pphm.svg

88 ms

cloud-illustration.png

cloud-illustration.png

198 ms

packet-pusher-pricing-pphm-3.png

packet-pusher-pricing-pphm-3.png

140 ms

cloud-white.svg

cloud-white.svg

86 ms

pricing-white.svg

pricing-white.svg

96 ms

distributed-white.svg

distributed-white.svg

89 ms

global-white.svg

global-white.svg

99 ms

config-white.svg

config-white.svg

344 ms

cloud-key-white.svg

cloud-key-white.svg

139 ms

PRTG-Hosted_Logo_blue_invers.svg

PRTG-Hosted_Logo_blue_invers.svg

168 ms

yes-check-white.svg

yes-check-white.svg

144 ms

split-gradient-ppem.svg

split-gradient-ppem.svg

163 ms

split-gradient-grey-light.svg

split-gradient-grey-light.svg

179 ms

Roboto-regular.woff2

Roboto-regular.woff2

128 ms

Roboto-500.woff2

Roboto-500.woff2

169 ms

Roboto-300.woff

Roboto-300.woff

209 ms

Roboto-100.woff2

Roboto-100.woff2

239 ms

Roboto-700.woff2

Roboto-700.woff2

208 ms

Roboto-900.woff2

Roboto-900.woff2

240 ms

otBannerSdk.js

otBannerSdk.js

84 ms

2990530.js

2990530.js

198 ms

web-interactives-embed.js

web-interactives-embed.js

119 ms

fb.js

fb.js

128 ms

leadflows.js

leadflows.js

152 ms

2990530.js

2990530.js

134 ms

Roboto-regular.woff

Roboto-regular.woff

58 ms

Roboto-500.woff

Roboto-500.woff

108 ms

Roboto-700.woff

Roboto-700.woff

20 ms

Roboto-100.woff

Roboto-100.woff

34 ms

Roboto-900.woff

Roboto-900.woff

55 ms

269d9497250e4f29aa6e5571df7b49b6

269d9497250e4f29aa6e5571df7b49b6

18 ms

a6661d8b926449f9abec5dbf77dd717c

a6661d8b926449f9abec5dbf77dd717c

4 ms

edda68b8c0594dfbb713b959b181be97

edda68b8c0594dfbb713b959b181be97

4 ms

7662baab85804590872fe54f71799843

7662baab85804590872fe54f71799843

6 ms

ac775e5c40d242cb8e85c1a2882e6ae4

ac775e5c40d242cb8e85c1a2882e6ae4

6 ms

a2a5ff75e2bc4bb9b907456fc6b79714

a2a5ff75e2bc4bb9b907456fc6b79714

7 ms

2c7385a360ab4f418508911f82fb5862

2c7385a360ab4f418508911f82fb5862

5 ms

Accessibility Review

prtg.com accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

Best Practices

prtg.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

prtg.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prtg.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Prtg.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

prtg.com

Open Graph data is detected on the main page of PRTG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: