Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

prorail.nl

ProRail | Verbindt. Verbetert. Verduurzaamt. | ProRail

Page Load Speed

1.4 sec in total

First Response

266 ms

Resources Loaded

1.2 sec

Page Rendered

0 ms

prorail.nl screenshot

About Website

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

ProRail is verantwoordelijk voor het spoorwegnet van Nederland. Samen met vervoerders zetten wij ons in om reizigers en goederen veilig en op tijd op hun bestemming te laten komen. We willen meer trei...

Visit prorail.nl

Key Findings

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

Performance Metrics

prorail.nl performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

prorail.nl

266 ms

www.prorail.nl

640 ms

app.css

17 ms

uc.js

104 ms

app.js

85 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 65% of them (17 requests) were addressed to the original Prorail.nl, 23% (6 requests) were made to Cdn1.readspeaker.com and 4% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (640 ms) belongs to the original domain Prorail.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.5 kB (29%)

Content Size

608.9 kB

After Optimization

429.4 kB

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

HTML Optimization

-81%

Potential reduce by 24.8 kB

  • Original 30.4 kB
  • After minification 20.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 9.6 kB, which is 31% 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 24.8 kB or 81% of the original size.

JavaScript Optimization

-19%

Potential reduce by 75.2 kB

  • Original 396.1 kB
  • After minification 396.1 kB
  • After compression 320.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 75.2 kB or 19% of the original size.

CSS Optimization

-44%

Potential reduce by 79.5 kB

  • Original 182.3 kB
  • After minification 182.3 kB
  • After compression 102.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. Prorail.nl needs all CSS files to be minified and compressed as it can save up to 79.5 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (54%)

Requests Now

24

After Optimization

11

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

Accessibility Review

prorail.nl accessibility score

100

Accessibility Issues

Best Practices

prorail.nl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

prorail.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 Prorail.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 Prorail.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 data is detected on the main page of Pro Rail. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: