Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

prijsplanner.nl

Welcome to nginx!

Page Load Speed

6.4 sec in total

First Response

1.7 sec

Resources Loaded

4.5 sec

Page Rendered

248 ms

prijsplanner.nl screenshot

About Website

Visit prijsplanner.nl now to see the best up-to-date Prijsplanner content and also check out these interesting facts you probably never knew about prijsplanner.nl

Visit prijsplanner.nl

Key Findings

We analyzed Prijsplanner.nl page load time and found that the first response time was 1.7 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

prijsplanner.nl performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value0.8 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

prijsplanner.nl

1665 ms

app.css

196 ms

custom.css

192 ms

foundation-icons.css

213 ms

logo.png

259 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that all of those requests were addressed to Prijsplanner.nl and no external sources were called. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Prijsplanner.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 472.2 kB (27%)

Content Size

1.7 MB

After Optimization

1.2 MB

In fact, the total size of Prijsplanner.nl main page is 1.7 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 74.9 kB

  • Original 86.5 kB
  • After minification 81.9 kB
  • After compression 11.7 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 74.9 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 56 B

  • Original 1.1 MB
  • After minification 1.1 MB

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. Prijsplanner images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 196.3 kB

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

CSS Optimization

-87%

Potential reduce by 200.9 kB

  • Original 230.2 kB
  • After minification 216.3 kB
  • After compression 29.3 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. Prijsplanner.nl needs all CSS files to be minified and compressed as it can save up to 200.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (7%)

Requests Now

92

After Optimization

86

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

Accessibility Review

prijsplanner.nl accessibility score

89

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

prijsplanner.nl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

prijsplanner.nl SEO score

64

Search Engine Optimization Advices

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 Prijsplanner.nl 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 Prijsplanner.nl 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 Prijsplanner. 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: