Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

ptz.dk

SecPro Sikring A/S | Din leverandør af sikringsprodukter

Page Load Speed

3.5 sec in total

First Response

764 ms

Resources Loaded

2.5 sec

Page Rendered

257 ms

ptz.dk screenshot

About Website

Visit ptz.dk now to see the best up-to-date Ptz content and also check out these interesting facts you probably never knew about ptz.dk

Vi er din professionelle samarbejdspartner og distributør af alarm og videoovervågning. Vi forhandler førende mærker som Milesight,...

Visit ptz.dk

Key Findings

We analyzed Ptz.dk page load time and found that the first response time was 764 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

ptz.dk performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value59.8 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value1.093

1/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

ptz.dk

764 ms

css

24 ms

css

37 ms

styles.css

552 ms

widgets.css

189 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 88% of them (70 requests) were addressed to the original Ptz.dk, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Ptz.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 729.9 kB (41%)

Content Size

1.8 MB

After Optimization

1.1 MB

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

HTML Optimization

-80%

Potential reduce by 35.9 kB

  • Original 44.8 kB
  • After minification 39.0 kB
  • After compression 8.9 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. This page needs HTML code to be minified as it can gain 5.8 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.9 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 72.2 kB

  • Original 936.7 kB
  • After minification 864.5 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. Ptz images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 495.8 kB

  • Original 663.7 kB
  • After minification 506.9 kB
  • After compression 167.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 495.8 kB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 126.0 kB

  • Original 148.8 kB
  • After minification 115.2 kB
  • After compression 22.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. Ptz.dk needs all CSS files to be minified and compressed as it can save up to 126.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (61%)

Requests Now

77

After Optimization

30

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

Accessibility Review

ptz.dk accessibility score

95

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.

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

Links do not have a discernible name

Best Practices

ptz.dk best practices score

75

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ptz.dk SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    DA

  • Language Claimed

    DA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ptz.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it matches the claimed language. Our system also found out that Ptz.dk 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

Open Graph description is not detected on the main page of Ptz. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: