6.2 sec in total
1.2 sec
4.6 sec
446 ms
Welcome to 112haarlem.nl homepage info - get ready to check 112Haarlem best content right away, or after learning these important things about 112haarlem.nl
Visit 112haarlem.nlWe analyzed 112haarlem.nl page load time and found that the first response time was 1.2 sec 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.
112haarlem.nl performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value6.2 s
11/100
25%
Value5.0 s
64/100
10%
Value100 ms
98/100
30%
Value0.003
100/100
15%
Value6.3 s
61/100
10%
1150 ms
2065 ms
93 ms
166 ms
167 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 85% of them (50 requests) were addressed to the original 112haarlem.nl, 7% (4 requests) were made to Pagead2.googlesyndication.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain 112haarlem.nl.
Page size can be reduced by 281.8 kB (19%)
1.5 MB
1.2 MB
In fact, the total size of 112haarlem.nl main page is 1.5 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 27.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 27.6 kB or 77% of the original size.
Potential reduce by 39.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. 112Haarlem images are well optimized though.
Potential reduce by 191.0 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 191.0 kB or 60% of the original size.
Potential reduce by 23.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. 112haarlem.nl needs all CSS files to be minified and compressed as it can save up to 23.6 kB or 79% of the original size.
Number of requests can be reduced by 26 (46%)
57
31
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 112Haarlem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
112haarlem.nl
1150 ms
www.112haarlem.nl
2065 ms
style.css
93 ms
base.js
166 ms
menu.js
167 ms
jquery-1.7.2.min.js
260 ms
lightbox251.js
178 ms
lightbox251.css
182 ms
tools.js
181 ms
youtube.js
245 ms
widget.css
246 ms
styles.css
283 ms
twitter-feed.css
283 ms
jquery.js
367 ms
jquery-migrate.min.js
327 ms
tw-sack.min.js
327 ms
show_ads.js
4 ms
jquery.form.min.js
341 ms
scripts.js
354 ms
wp-embed.min.js
358 ms
wp-emoji-release.min.js
144 ms
bg.jpg
218 ms
light.gif
305 ms
header.jpg
308 ms
menu.gif
217 ms
searchbox.gif
218 ms
p2000shop_468_60.gif
540 ms
16-dijkz5.jpg
579 ms
14-gouwstraat1.jpg
467 ms
10-verspronckweg3.jpg
624 ms
10-kleverlaan4.jpg
660 ms
6-prinsbernhardlaan5.jpg
579 ms
owietplantage1.jpg
551 ms
30-oostermoer1.jpg
704 ms
27-antoniestraat5.jpg
802 ms
26-n20882.jpg
761 ms
26-spaarnwouderstraat4.jpg
760 ms
brandweer.png
705 ms
ambulance.png
749 ms
p2000shop_120_120.gif
786 ms
uwadv.gif
787 ms
sidesep.gif
829 ms
main_shadow.gif
842 ms
icons.gif
843 ms
sidebar_shadow.gif
859 ms
widgetsep.png
860 ms
feeds.gif
876 ms
rood.png
917 ms
ca-pub-8254927207439752.js
237 ms
zrt_lookup.html
232 ms
show_ads_impl.js
184 ms
footer.jpg
907 ms
ga.js
15 ms
__utm.gif
53 ms
loading.gif
734 ms
close.png
740 ms
ads
169 ms
osd.js
3 ms
__utm.gif
4 ms
112haarlem.nl accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
112haarlem.nl 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
112haarlem.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 112haarlem.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 112haarlem.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.
112haarlem.nl
Open Graph description is not detected on the main page of 112Haarlem. 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: