Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

translink.nl

Translink

Page Load Speed

5.2 sec in total

First Response

229 ms

Resources Loaded

4.7 sec

Page Rendered

257 ms

translink.nl screenshot

About Website

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

Translink

Visit translink.nl

Key Findings

We analyzed Translink.nl page load time and found that the first response time was 229 ms and then it took 5 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

translink.nl performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.191

64/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

Home

229 ms

GetResource.ashx

187 ms

modernizr-2.6.2-respond-1.1.0.min.js

264 ms

WebResource.axd

3052 ms

ScriptResource.axd

3058 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 91% of them (39 requests) were addressed to the original Translink.nl, 5% (2 requests) were made to S7.addthis.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Translink.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 600.3 kB (36%)

Content Size

1.7 MB

After Optimization

1.1 MB

In fact, the total size of Translink.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. 35% of websites need less resources to load. Images take 896.7 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 40.9 kB

  • Original 60.4 kB
  • After minification 59.6 kB
  • After compression 19.4 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 40.9 kB or 68% of the original size.

Image Optimization

-6%

Potential reduce by 57.1 kB

  • Original 896.7 kB
  • After minification 839.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. Translink images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 464.6 kB

  • Original 675.0 kB
  • After minification 636.7 kB
  • After compression 210.4 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 464.6 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 37.6 kB

  • Original 44.7 kB
  • After minification 32.7 kB
  • After compression 7.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. Translink.nl needs all CSS files to be minified and compressed as it can save up to 37.6 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

42

After Optimization

29

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

Accessibility Review

translink.nl accessibility score

71

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

translink.nl best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

translink.nl SEO score

85

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Translink.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Translink.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 Translink. 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: