Tools & Wizards About Us
routenet.nl screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

routenet.nl

Routenet Routeplanner

Page Load Speed

3.1 sec in total

First Response

377 ms

Resources Loaded

2.7 sec

Page Rendered

69 ms

routenet.nl screenshot

About Website

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

Met de Routenet routeplanner plan je routes door heel europa van deur tot deur. Gebruik de Routenet routeplanner voor routes, reiskosten declaraties of CO2 uitstoot van je auto

Visit routenet.nl

Key Findings

We analyzed Routenet.nl page load time and found that the first response time was 377 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

routenet.nl performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value2,450 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

routenet.nl

377 ms

bootstrap.min.css

179 ms

bundle.min.css

268 ms

js

65 ms

launcher.js

77 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 46% of them (11 requests) were addressed to the original Routenet.nl, 13% (3 requests) were made to Cdn.userreport.com and 8% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Mmcdn.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.9 kB (19%)

Content Size

736.0 kB

After Optimization

595.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Routenet.nl main page is 736.0 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. 25% of websites need less resources to load. Javascripts take 480.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 31.9 kB

  • Original 45.4 kB
  • After minification 45.4 kB
  • After compression 13.5 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 31.9 kB or 70% of the original size.

Image Optimization

-11%

Potential reduce by 14.5 kB

  • Original 130.1 kB
  • After minification 115.6 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, Routenet needs image optimization as it can save up to 14.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 70.8 kB

  • Original 480.9 kB
  • After minification 480.5 kB
  • After compression 410.1 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 70.8 kB or 15% of the original size.

CSS Optimization

-30%

Potential reduce by 23.8 kB

  • Original 79.7 kB
  • After minification 79.7 kB
  • After compression 55.9 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. Routenet.nl needs all CSS files to be minified and compressed as it can save up to 23.8 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (68%)

Requests Now

22

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

routenet.nl

routenet.nl

377 ms

bootstrap.min.css

bootstrap.min.css

179 ms

bundle.min.css

bundle.min.css

268 ms

js

js

65 ms

launcher.js

launcher.js

77 ms

adsbygoogle.js

adsbygoogle.js

390 ms

home.js

home.js

1687 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

374 ms

bundle.js

bundle.js

893 ms

popper.min.js

popper.min.js

461 ms

prebid-ads-banner-ad.js

prebid-ads-banner-ad.js

463 ms

cmp.php

cmp.php

501 ms

cmp_nl.min.js

cmp_nl.min.js

274 ms

routenet_logo.png

routenet_logo.png

175 ms

country-flag.png

country-flag.png

341 ms

logo_onderweg.png

logo_onderweg.png

175 ms

userreport.js

userreport.js

76 ms

fa-solid-900.ttf

fa-solid-900.ttf

869 ms

hit

hit

65 ms

show_ads_impl.js

show_ads_impl.js

514 ms

settings.js

settings.js

3 ms

SystemSettings.js

SystemSettings.js

296 ms

cmp.php

cmp.php

104 ms

bV8xLndfNzM3NTQucl9HRFBSLmxfbmwuZF8yODU1OC54XzExLnYucC50XzI4NTU4Lnh0XzEx.js

bV8xLndfNzM3NTQucl9HRFBSLmxfbmwuZF8yODU1OC54XzExLnYucC50XzI4NTU4Lnh0XzEx.js

1034 ms

Accessibility Review

routenet.nl accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

Buttons do not have an accessible name

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

High

Some elements have a [tabindex] value greater than 0

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

routenet.nl SEO score

93

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

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

routenet.nl

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