4.1 sec in total
312 ms
3.6 sec
205 ms
Visit haagsedirecte.nl now to see the best up-to-date Haagse Directe content and also check out these interesting facts you probably never knew about haagsedirecte.nl
Visit haagsedirecte.nlWe analyzed Haagsedirecte.nl page load time and found that the first response time was 312 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
haagsedirecte.nl performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value11.1 s
0/100
25%
Value7.7 s
24/100
10%
Value620 ms
48/100
30%
Value0.089
92/100
15%
Value11.7 s
17/100
10%
312 ms
82 ms
566 ms
181 ms
181 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 87% of them (75 requests) were addressed to the original Haagsedirecte.nl, 7% (6 requests) were made to and 2% (2 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Haagsedirecte.nl.
Page size can be reduced by 1.1 MB (8%)
13.2 MB
12.1 MB
In fact, the total size of Haagsedirecte.nl main page is 13.2 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. 55% of websites need less resources to load. Images take 12.5 MB which makes up the majority of the site volume.
Potential reduce by 20.6 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 20.6 kB or 84% of the original size.
Potential reduce by 603.3 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. Haagse Directe images are well optimized though.
Potential reduce by 462.5 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 462.5 kB or 66% of the original size.
Potential reduce by 20.3 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. Haagsedirecte.nl needs all CSS files to be minified and compressed as it can save up to 20.3 kB or 82% of the original size.
Number of requests can be reduced by 3 (4%)
78
75
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Haagse Directe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
haagsedirecte.nl
312 ms
application-33d62f96aa55fc7a73e88ddcc5cdfb37.css
82 ms
application-127dbb5f2f04fc37a6490b8d4fa3e4d6.js
566 ms
tfr3fao.js
181 ms
shapes-e6f23e94cfe840a0a76915a07093dd8b.js
181 ms
HD-background-gradient-9411ffecff3f8279db4d3bd3083503d0.png
98 ms
p.gif
132 ms
tfr3fao-a.css
302 ms
ga.js
147 ms
00.jpg
478 ms
-20002.jpg
325 ms
-20003.jpg
423 ms
-20004.jpg
564 ms
-20005.jpg
500 ms
-20006.jpg
604 ms
-20007.jpg
495 ms
-20008.jpg
626 ms
-20009.jpg
602 ms
-20010.jpg
588 ms
-20011.jpg
779 ms
-20012.jpg
729 ms
-20013.jpg
680 ms
-20014.jpg
788 ms
-20015.jpg
948 ms
-20016.jpg
791 ms
-20017.jpg
840 ms
-20018.jpg
897 ms
-20019.jpg
1036 ms
-20020.jpg
954 ms
-20021.jpg
961 ms
-20022.jpg
938 ms
-20023.jpg
1069 ms
-20024.jpg
1034 ms
-20025.jpg
1328 ms
-20026.jpg
1143 ms
-20027.jpg
1145 ms
-20028.jpg
1124 ms
-20029.jpg
1227 ms
-20030.jpg
1162 ms
01.jpg
1220 ms
-20031.jpg
1329 ms
-20032.jpg
1327 ms
-20033.jpg
1272 ms
-20034.jpg
1316 ms
-20035.jpg
1415 ms
9cAAgARAAoACgAAABAAEAABABMAHAACACQAJAAMACYALwANADEAPQAXAEQASwAkAE4ATgAsAFAAXQAtAG8AbwA7AIIAmAA8AJoAnwBTAKIArQBZALMAuABlALoAwQBrAMQAygBzAM4AzgB6AAAAAQAAAADG1C6ZAAAAAMkncR4AAAAAySd8uQ==
39 ms
AJoAnwBWAKIArQBcALMAuABoALoAwQBuAMQAygB2AM4AzgB9AAAAAQAAAADG1C6ZAAAAAMkndQQAAAAAySd8yw==
37 ms
BAAIAEAAKAAoAAAAPABEAAQATABwABAAkAD0ADgBEAEYAKABIAEsAKwBOAE4ALwBQAF0AMABvAG8APgCCAJgAPwCaAJ8AVgCiALEAXACzALgAbAC6AMEAcgDEAMoAegDOAM4AgQAAAAEAAAAAxtQumQAAAADJJ3S3AAAAAMknfNQ=
35 ms
gwACABAACgAKAAAAEAAQAAEAEwAcAAIAJAArAAwALQA9ABQARABLACUATgBOAC0AUABdAC4AbwBvADwAggCNAD0AkgCYAEkAmgCfAFAAogCtAFYAswC4AGIAugDBAGgAxADKAHAAAAAAAAEAAAAAxtQumQAAAADJJ3D7AAAAAMknfL4=
34 ms
gwACABEACgAKAAAADwARAAEAEwAcAAQAJAA9AA4ARABGACgASABLACsATgBOAC8AUABdADAAbwBvAD4AfQB9AD8AggCYAEAAmgCfAFcAogCtAF0AswC4AGkAugDBAG8AxADKAHcAzgDOAH4AAAABAAAAAMbULpkAAAAAySd05QAAAADJJ3zQ
32 ms
+pAAIADAAKAAoAAAAPABEAAQATABwABAAkAD0ADgBEAF0AKABvAG8AQgCCAJgAQwCaAJ8AWgCiALEAYACzALgAcAC6AMEAdgDEAMoAfgAAAAAAAQAAAADG1C6ZAAAAAMkndJIAAAAAySd81w==
29 ms
__utm.gif
18 ms
-20036.jpg
1138 ms
-20037.jpg
1031 ms
-20038.jpg
1193 ms
-20039.jpg
950 ms
-20040.jpg
1044 ms
-20041.jpg
948 ms
-20042.jpg
1024 ms
-20043.jpg
941 ms
09.jpg
958 ms
-20045.jpg
981 ms
-20046.jpg
958 ms
-20047.jpg
1012 ms
-20048.jpg
886 ms
-20049.jpg
911 ms
-20050.jpg
1046 ms
-20051.jpg
1052 ms
-20052.jpg
914 ms
-20053.jpg
899 ms
-20054.jpg
847 ms
-20055.jpg
950 ms
-20056.jpg
927 ms
bellopro-webfont.woff
860 ms
-20057.jpg
893 ms
-20058.jpg
971 ms
10.jpg
859 ms
-20001.jpg
947 ms
05.jpg
858 ms
03.jpg
949 ms
11.jpg
813 ms
-20044.jpg
854 ms
-20059.jpg
898 ms
-20060.jpg
813 ms
prev-57caaa1748a42ab2eacaa100ba69851c.png
806 ms
next-4ceb256ee13ffdacad13c839951828de.png
834 ms
haagsedirecte.nl accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
haagsedirecte.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
haagsedirecte.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haagsedirecte.nl 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 Haagsedirecte.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.
haagsedirecte.nl
Open Graph description is not detected on the main page of Haagse Directe. 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: