2.1 sec in total
317 ms
1.4 sec
377 ms
Click here to check amazing TRN content. Otherwise, check out these important facts you probably never knew about trn.eu
TRN helpt je de snelste, meest betrouwbare weg te vinden naar duurzame groei dankzij een klantgerichte benadering, data en creativiteit.
Visit trn.euWe analyzed Trn.eu page load time and found that the first response time was 317 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
trn.eu performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value4.9 s
29/100
25%
Value5.2 s
59/100
10%
Value110 ms
97/100
30%
Value0.029
100/100
15%
Value5.1 s
75/100
10%
317 ms
95 ms
169 ms
194 ms
197 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 72% of them (31 requests) were addressed to the original Trn.eu, 7% (3 requests) were made to Ajax.googleapis.com and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (669 ms) belongs to the original domain Trn.eu.
Page size can be reduced by 218.7 kB (64%)
339.8 kB
121.1 kB
In fact, the total size of Trn.eu main page is 339.8 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. 40% of websites need less resources to load. Javascripts take 200.8 kB which makes up the majority of the site volume.
Potential reduce by 19.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. 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 19.9 kB or 76% of the original size.
Potential reduce by 4.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, TRN needs image optimization as it can save up to 4.4 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 112.7 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 112.7 kB or 56% of the original size.
Potential reduce by 81.6 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. Trn.eu needs all CSS files to be minified and compressed as it can save up to 81.6 kB or 83% of the original size.
Number of requests can be reduced by 26 (68%)
38
12
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TRN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
trn.eu
317 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
95 ms
css_TsVRTbLFUpEZAfw-_bWPJu840QT523CPjUVJ5MRWfyk.css
169 ms
css_KNaHRUyjnHH18p-jc9goQf4SPYn_bydm3js6FC_uroY.css
194 ms
css_Zv9XU9-FH6dWluXIqsTrRvupdiaCmAkks8sfzwc8rzU.css
197 ms
css
45 ms
css_YwadY40UenV4UCiTyWfjDe35aDduIkfipnpi9cVtw78.css
182 ms
css_xZor_VBEKoUpXcb6UmHGmENCo6DovNENO_fn9aW2Tbw.css
197 ms
jquery.min.js
7 ms
jquery.scroll.js
210 ms
jquery.touchSwipe.min.js
250 ms
home.js
270 ms
thickbox.js
275 ms
jquery.min.js
27 ms
jquery.min.js
35 ms
jquery.once.js
274 ms
drupal.js
296 ms
jquery.bgiframe.js
299 ms
jquery.hoverIntent.js
333 ms
superfish.js
360 ms
nice_menus.js
361 ms
panels.js
363 ms
mobile_menu.js
368 ms
mobile_navigation.js
375 ms
googleanalytics.js
416 ms
jquery.formalize.js
450 ms
omega-mediaqueries.js
451 ms
conversion.js
37 ms
ga.js
8 ms
__utm.gif
80 ms
logo.jpg
186 ms
vacature-socialmedia.jpg
669 ms
zwart.png
103 ms
scrollArrow.png
104 ms
men.png
103 ms
fb-wit.png
104 ms
in-wit.png
194 ms
pin-wit.png
195 ms
61 ms
DXI1ORHCpsQm3Vp6mXoaTYraN7vELC11_xip9Rz-hMs.woff
6 ms
MTP_ySUJH_bn48VBG8sNSoraN7vELC11_xip9Rz-hMs.woff
12 ms
EInbV5DfGHOiMmvb1Xr-horaN7vELC11_xip9Rz-hMs.woff
13 ms
46 ms
trn.eu accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
trn.eu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
trn.eu SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trn.eu can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Trn.eu 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.
trn.eu
Open Graph description is not detected on the main page of TRN. 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: