Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 0

    Best Practices

  • 100

    SEO

    Google-friendlier than
    94% of websites

paulroescher.nl

Paul Roescher: keukens, badkamers, vloeren, tegels en kasten

Page Load Speed

3.1 sec in total

First Response

281 ms

Resources Loaded

2 sec

Page Rendered

799 ms

paulroescher.nl screenshot

About Website

Welcome to paulroescher.nl homepage info - get ready to check Paul Roescher best content for Netherlands right away, or after learning these important things about paulroescher.nl

Al meer dan 50 jaar de specialist in keukens, badkamers, vloeren en kasten. Bezoek de grootste showroom van Europa en profiteer van de laagste prijs.

Visit paulroescher.nl

Key Findings

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

Performance Metrics

paulroescher.nl performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value1,620 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

paulroescher.nl

281 ms

www.paulroescher.nl

559 ms

css2

27 ms

style.min.css

192 ms

libs.js

507 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 55% of them (16 requests) were addressed to the original Paulroescher.nl, 17% (5 requests) were made to Googletagmanager.com and 17% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (878 ms) belongs to the original domain Paulroescher.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.7 kB (17%)

Content Size

844.5 kB

After Optimization

698.8 kB

In fact, the total size of Paulroescher.nl main page is 844.5 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. 70% of websites need less resources to load. Images take 520.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 54.7 kB

  • Original 64.6 kB
  • After minification 54.6 kB
  • After compression 9.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 10.0 kB, which is 16% 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 54.7 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 4.0 kB

  • Original 520.7 kB
  • After minification 516.7 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. Paul Roescher images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 86.8 kB

  • Original 210.8 kB
  • After minification 210.8 kB
  • After compression 124.0 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 86.8 kB or 41% of the original size.

CSS Optimization

-1%

Potential reduce by 277 B

  • Original 48.4 kB
  • After minification 48.4 kB
  • After compression 48.1 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. Paulroescher.nl has all CSS files already compressed.

Requests Breakdown

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

Requests Now

21

After Optimization

14

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

Accessibility Review

paulroescher.nl accessibility score

93

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

SEO Factors

paulroescher.nl SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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