3.8 sec in total
346 ms
3.1 sec
339 ms
Click here to check amazing Oranjeroute content. Otherwise, check out these important facts you probably never knew about oranjeroute.nl
Ontdek de roots van het Huis van Oranje-Nassau in Duitsland!
Visit oranjeroute.nlWe analyzed Oranjeroute.nl page load time and found that the first response time was 346 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
oranjeroute.nl performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value10.5 s
0/100
25%
Value6.9 s
33/100
10%
Value190 ms
90/100
30%
Value0.001
100/100
15%
Value9.9 s
27/100
10%
346 ms
137 ms
302 ms
1062 ms
185 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Oranjeroute.nl, 24% (18 requests) were made to Germany.travel and 19% (14 requests) were made to S2.germany.travel. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source S2.germany.travel.
Page size can be reduced by 856.5 kB (47%)
1.8 MB
977.0 kB
In fact, the total size of Oranjeroute.nl main page is 1.8 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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 55.2 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 55.2 kB or 72% of the original size.
Potential reduce by 27.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. Oranjeroute images are well optimized though.
Potential reduce by 696.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 696.4 kB or 63% of the original size.
Potential reduce by 77.5 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. Oranjeroute.nl needs all CSS files to be minified and compressed as it can save up to 77.5 kB or 85% of the original size.
Number of requests can be reduced by 40 (57%)
70
30
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oranjeroute. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
oranjeroute.nl
346 ms
home-page.html
137 ms
style.css
302 ms
base_gallery.css
1062 ms
731_msOranjeroute.css
185 ms
jquery-ui.css
188 ms
jquery.min.js
12 ms
jquerycycleallmin.js
187 ms
jquerymousewheel.js
181 ms
jScrollPane.js
185 ms
jquery_uimin.js
371 ms
jquery_cookie.js
274 ms
jquery_tinytip.js
274 ms
jquery_url.js
275 ms
jquery_box_map.js
277 ms
js
36 ms
js-mtk
561 ms
application_gallery.js
366 ms
application.js
458 ms
application_travelplanner.js
369 ms
jquery_validate.js
1155 ms
e.js
329 ms
jquery_supersized_core.js
365 ms
addthis_widget.js
12 ms
900_print.css
95 ms
common.js
29 ms
map.js
29 ms
util.js
11 ms
poly.js
10 ms
zmags_thumb.js
98 ms
ga.js
93 ms
jquery-1.8.3.min.js
389 ms
270 ms
t.js
410 ms
Background.png
1147 ms
bgTop.png
135 ms
logo_DR.gif
609 ms
header_Diez-Stadt-am-Fluss-1.jpg
823 ms
header_Potsdam-boogschutter.jpg
835 ms
header_Schwerin_-gehendes-Paar-mit-Schuhen-in-der-Hand.jpg
831 ms
btn_facebook.jpg
606 ms
bgSideBoxGreyLight_top.png
606 ms
dottedLine_dark.png
673 ms
bgLayoutColumn100_bottom.png
680 ms
bg_navi.png
1062 ms
lgo_oranier_route_nl.png
1140 ms
ico_breadcrumb_devider.png
1062 ms
ico_newsletter.png
1060 ms
bg_footer.png
1142 ms
iconArrowLanguage.png
128 ms
bgLogoLayer.png
158 ms
logo_BM.png
183 ms
transparentTextLayer.png
185 ms
Reinildis_van_Ditzhuyzen_Michiel_van_Nieuwkerk2009_klein.jpg
243 ms
dzt-staticmap-v3.jpg
405 ms
mtk_overlay.png
188 ms
iconPrint.png
235 ms
iconShare.png
242 ms
bgFoot.png
244 ms
de.jpg
27 ms
tiles.json
221 ms
300lo.json
64 ms
t.gif
31 ms
87745.png
388 ms
iconSetStartSlide.png
121 ms
__utm.gif
34 ms
sh.8e5f85691f9aaa082472a194.html
26 ms
collect
61 ms
ga-audiences
40 ms
items.json
242 ms
vvcnt.php
317 ms
cnt_js.php
255 ms
cntcc
264 ms
182.png
265 ms
oranjeroute.nl accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
oranjeroute.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
oranjeroute.nl 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
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oranjeroute.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 Oranjeroute.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.
oranjeroute.nl
Open Graph description is not detected on the main page of Oranjeroute. 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: