Tools & Wizards About Us
rrs.nl screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

rrs.nl

Riool Reinigings Service RRS - Riool verstopt? Geen stress. Bel RRS

Page Load Speed

3 sec in total

First Response

834 ms

Resources Loaded

2 sec

Page Rendered

219 ms

rrs.nl screenshot

About Website

Click here to check amazing RRS content for Netherlands. Otherwise, check out these important facts you probably never knew about rrs.nl

RRS is uw specialist voor het ontstoppen, reinigen, inspecteren en lokaliseren van riolering, afvoer, leidingen, vetafscheiders en septic tanks.

Visit rrs.nl

Key Findings

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

Performance Metrics

rrs.nl performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value3.0 s

93/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

www.rrs.nl

834 ms

css

27 ms

css

40 ms

css

45 ms

jquery.slides.less

168 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 52% of them (26 requests) were addressed to the original Rrs.nl, 22% (11 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (834 ms) belongs to the original domain Rrs.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 352.1 kB (50%)

Content Size

701.9 kB

After Optimization

349.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 22.6 kB

  • Original 30.3 kB
  • After minification 24.4 kB
  • After compression 7.8 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.9 kB, which is 19% 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 22.6 kB or 74% of the original size.

Image Optimization

-25%

Potential reduce by 83.9 kB

  • Original 339.3 kB
  • After minification 255.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. Obviously, RRS needs image optimization as it can save up to 83.9 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 154.4 kB

  • Original 220.9 kB
  • After minification 217.6 kB
  • After compression 66.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 154.4 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 91.2 kB

  • Original 111.3 kB
  • After minification 111.1 kB
  • After compression 20.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. Rrs.nl needs all CSS files to be minified and compressed as it can save up to 91.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (46%)

Requests Now

35

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.rrs.nl

www.rrs.nl

834 ms

css

css

27 ms

css

css

40 ms

css

css

45 ms

jquery.slides.less

jquery.slides.less

168 ms

homepage.less

homepage.less

183 ms

styles-min.css

styles-min.css

352 ms

scripts-min.js

scripts-min.js

613 ms

gtm.js

gtm.js

46 ms

inloggen-mijnrrs.png

inloggen-mijnrrs.png

105 ms

logo.png

logo.png

238 ms

bel-RRS.png

bel-RRS.png

176 ms

hoofdbanner-img-1_960x400_104.png

hoofdbanner-img-1_960x400_104.png

739 ms

rrs-lost-het-op_312x253_120.png

rrs-lost-het-op_312x253_120.png

289 ms

contract-op-maat_312x253_97.png

contract-op-maat_312x253_97.png

377 ms

direct-contact.png

direct-contact.png

376 ms

werken-bij-rrs_222x68_13.png

werken-bij-rrs_222x68_13.png

468 ms

contact_222x68_14.png

contact_222x68_14.png

397 ms

over-rrs_222x68_15.png

over-rrs_222x68_15.png

519 ms

zakelijk_222x68_16.png

zakelijk_222x68_16.png

421 ms

dekra-certificeerd.png

dekra-certificeerd.png

484 ms

analytics.js

analytics.js

16 ms

conversion_async.js

conversion_async.js

16 ms

hotjar-142568.js

hotjar-142568.js

132 ms

collect

collect

6 ms

collect

collect

67 ms

47 ms

47 ms

ga-audiences

ga-audiences

34 ms

modules-043c1e6abe660c48857202e419ff9d8a.js

modules-043c1e6abe660c48857202e419ff9d8a.js

34 ms

icons.png

icons.png

188 ms

menu-arrows.png

menu-arrows.png

242 ms

usp-icon.png

usp-icon.png

330 ms

socialmedia-icons-gray.png

socialmedia-icons-gray.png

330 ms

transpBG80.png

transpBG80.png

331 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

12 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

11 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

11 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

10 ms

b9QBgL0iMZfDSpmcXcE8nCSLrGe-fkSRw2DeVgOoWcQ.woff

b9QBgL0iMZfDSpmcXcE8nCSLrGe-fkSRw2DeVgOoWcQ.woff

10 ms

Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff

Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff

10 ms

b9QBgL0iMZfDSpmcXcE8nNeiznanRB67rGZDYkMvKPc.woff

b9QBgL0iMZfDSpmcXcE8nNeiznanRB67rGZDYkMvKPc.woff

16 ms

bebasneue-webfont.woff

bebasneue-webfont.woff

288 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

17 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

15 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

16 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

16 ms

jquery.cookie.js

jquery.cookie.js

94 ms

zoomloader.gif

zoomloader.gif

96 ms

popup_ajax-loader.gif

popup_ajax-loader.gif

99 ms

Accessibility Review

rrs.nl accessibility score

91

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

Image elements do not have [alt] attributes

Best Practices

rrs.nl 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

SEO Factors

rrs.nl SEO score

86

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Rrs.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 Rrs.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

rrs.nl

Open Graph description is not detected on the main page of RRS. 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: