8.5 sec in total
723 ms
7.5 sec
309 ms
Welcome to oldholland.com homepage info - get ready to check Old Holland best content for Russia right away, or after learning these important things about oldholland.com
Visit oldholland.comWe analyzed Oldholland.com page load time and found that the first response time was 723 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
oldholland.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.3 s
10/100
25%
Value6.1 s
45/100
10%
Value20 ms
100/100
30%
Value0.141
78/100
15%
Value4.7 s
79/100
10%
723 ms
469 ms
288 ms
290 ms
290 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 70% of them (35 requests) were addressed to the original Oldholland.com, 20% (10 requests) were made to Static.xx.fbcdn.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Oldholland.com.
Page size can be reduced by 380.0 kB (39%)
984.5 kB
604.4 kB
In fact, the total size of Oldholland.com main page is 984.5 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. 30% of websites need less resources to load. Images take 468.5 kB which makes up the majority of the site volume.
Potential reduce by 23.8 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 23.8 kB or 80% of the original size.
Potential reduce by 5.9 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. Old Holland images are well optimized though.
Potential reduce by 293.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 293.9 kB or 70% of the original size.
Potential reduce by 56.4 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. Oldholland.com needs all CSS files to be minified and compressed as it can save up to 56.4 kB or 86% of the original size.
Number of requests can be reduced by 36 (75%)
48
12
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Old Holland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.oldholland.com
723 ms
style.css
469 ms
style.css
288 ms
thickbox.css
290 ms
attachment-file.css
290 ms
jquery.js
768 ms
jquery-migrate.min.js
505 ms
raw.js
503 ms
jquery.prettyPhoto.js
626 ms
jquery.backstretch.min.js
503 ms
smoothscroll.js
608 ms
twitter.min.js
141 ms
oldholland.js
610 ms
easy_table_creator.js
617 ms
jquery.tablesorter.min.js
790 ms
jquery.multifile.js
750 ms
cufon-yui.js
1478 ms
uni_cond_b.js
1902 ms
prettyPhoto_v.css
954 ms
comment-reply.min.js
1195 ms
thickbox.js
929 ms
wp-embed.min.js
934 ms
wp-emoji-release.min.js
631 ms
logo_old_holland_120x120_trans.png
513 ms
gb.png
137 ms
nl.png
138 ms
fr.png
134 ms
de.png
136 ms
share-button.png
135 ms
quote_bg.png
310 ms
logo-old-holland_traced_cropped_gw_3-200x200.jpg
310 ms
oldhollandHR-49-3-200x200.jpg
450 ms
oldhollandHR-72-200x200.jpg
451 ms
league_ghotic_extended-webfont.woff
381 ms
ga.js
220 ms
oldhollandHR-26_web.jpg
4185 ms
loadingAnimation.gif
318 ms
likebox.php
339 ms
__utm.gif
76 ms
bekMD-lCbkm.css
1408 ms
sEpAygasRyW.css
1455 ms
XCdv7aD40Gm.js
1559 ms
lnwXDK64af8.js
1673 ms
mn6tHWuLI-Y.js
1557 ms
x8BMxYCqTb9.js
1557 ms
1464669_836262823076333_1449980919413056443_n.png
316 ms
wL6VQj7Ab77.png
75 ms
s7jcwEQH7Sx.png
108 ms
VXcANLwwL5J.js
103 ms
50Trs1RKgUY.js
106 ms
oldholland.com 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 input fields 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
Links do not have a discernible name
oldholland.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
oldholland.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oldholland.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Oldholland.com 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.
oldholland.com
Open Graph description is not detected on the main page of Old Holland. 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: