8.1 sec in total
342 ms
7.3 sec
522 ms
Welcome to hoorngids.nl homepage info - get ready to check Hoorn Gids best content for Netherlands right away, or after learning these important things about hoorngids.nl
Lokale streekomroep SWF·HoornRadio Radio·Podcast·Video·Netkrant Nieuws uit Hoorn in beeld Gast in Radio Actueel: wethouder Dick Bennis Voetganger door trein geraakt op spoorwegovergang Berkhouterweg D...
Visit hoorngids.nlWe analyzed Hoorngids.nl page load time and found that the first response time was 342 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.
hoorngids.nl performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value13.0 s
0/100
25%
Value10.9 s
6/100
10%
Value1,390 ms
16/100
30%
Value1.017
2/100
15%
Value12.0 s
16/100
10%
342 ms
1384 ms
2682 ms
406 ms
167 ms
Our browser made a total of 174 requests to load all elements on the main page. We found that 51% of them (88 requests) were addressed to the original Hoorngids.nl, 9% (15 requests) were made to Maps.google.com and 7% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Hoorngids.nl.
Page size can be reduced by 708.0 kB (36%)
2.0 MB
1.3 MB
In fact, the total size of Hoorngids.nl main page is 2.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 136.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 136.6 kB or 79% of the original size.
Potential reduce by 62.8 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. Hoorn Gids images are well optimized though.
Potential reduce by 500.1 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 500.1 kB or 67% of the original size.
Potential reduce by 8.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. Hoorngids.nl needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 84% of the original size.
Number of requests can be reduced by 52 (31%)
166
114
The browser has sent 166 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hoorn Gids. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
hoorngids.nl
342 ms
www.hoorngids.nl
1384 ms
1
2682 ms
site.js
406 ms
common.js
167 ms
validation.js
172 ms
common.css
178 ms
combined.css
354 ms
jquery.fancybox-1.3.4.css
184 ms
news.css
298 ms
Poll.css
259 ms
jwplayer.js
405 ms
News.js
206 ms
jquery.fancybox-1.3.4.js
274 ms
layer_5727_29aa9f3311084cbb8c15e55562218809.png
194 ms
layer_5728_ec140854df2242f6b36c07a8044aa341.png
132 ms
0.png
114 ms
1.png
112 ms
2.png
120 ms
3.jpg
107 ms
4.jpg
192 ms
5.jpg
211 ms
7.jpg
208 ms
8.jpg
220 ms
9.jpg
226 ms
10.jpg
277 ms
11.jpg
279 ms
12.jpg
303 ms
13.jpg
314 ms
14.jpg
326 ms
15.jpg
327 ms
16.jpg
381 ms
17.jpg
374 ms
18.jpg
399 ms
19.jpg
416 ms
20.jpg
420 ms
21.png
439 ms
3615440_1_org.jpg
473 ms
3615422_1_org.jpg
558 ms
3615409_1_org.jpg
826 ms
3615393_1_org.jpg
533 ms
3615392_1_org.jpg
829 ms
3615355_1_org.jpg
547 ms
3615342_1_org.jpg
572 ms
3615341_1_org.jpg
809 ms
3615291_1_org.jpg
649 ms
3615227_1_org.jpg
722 ms
3615224_1_org.jpg
672 ms
3615200_1_org.jpg
766 ms
3615198_1_org.jpg
778 ms
ga.js
25 ms
__utm.gif
17 ms
106
732 ms
za.js
761 ms
3615175_1_org.jpg
779 ms
3615168_1_org.jpg
802 ms
banner_Radio_Bontekoe_1.png
974 ms
3615440_1_org.jpg
749 ms
3615422_1_org.jpg
749 ms
3615409_1_org.jpg
769 ms
3615393_1_org.jpg
801 ms
3615392_1_org.jpg
816 ms
3615355_1_org.jpg
828 ms
3615342_1_org.jpg
769 ms
3615341_1_org.jpg
810 ms
3615291_1_org.jpg
821 ms
3615227_1_org.jpg
837 ms
facebookLinkImage.png
820 ms
twitterLinkImage.png
825 ms
ml_arrow_white.png
805 ms
gs_loop_white.png
807 ms
106_1282b121333e413792e247d773133575.jpg
466 ms
106_871a5c2921a7444094c83ebf29dbb38f.jpg
500 ms
106_95ae0d4d26834e9e890194cb5db48bc1.jpg
492 ms
track
396 ms
likebox.php
247 ms
like.php
187 ms
widgets.js
264 ms
in.js
85 ms
plusone.js
177 ms
js
57 ms
0_0.png
168 ms
1_0.png
172 ms
2_0.png
170 ms
3_0.jpg
170 ms
4_0.jpg
167 ms
5_0.jpg
165 ms
7_0.jpg
234 ms
8_0.jpg
233 ms
9_0.jpg
249 ms
10_0.jpg
248 ms
11_0.jpg
247 ms
12_0.jpg
246 ms
13_0.jpg
390 ms
14_0.jpg
389 ms
twitter_search.json
528 ms
common.js
12 ms
map.js
25 ms
util.js
25 ms
marker.js
24 ms
StaticMapService.GetMapImage
160 ms
secureAnonymousFramework
18 ms
onion.js
61 ms
openhand_8_8.cur
111 ms
share
261 ms
sprite_connect_v14.png
257 ms
qeKvIRsJabD.js
221 ms
LVx-xkvaJ0b.png
241 ms
ViewportInfoService.GetViewportInfo
72 ms
stats.js
53 ms
controls.js
67 ms
cb=gapi.loaded_0
189 ms
cb=gapi.loaded_1
233 ms
fastbutton
348 ms
410ucuAGgaJ.css
199 ms
tSbl8xBI27R.css
194 ms
q68gy-v_YMF.js
192 ms
FJmpeSpHpjS.js
213 ms
0wM5s1Khldu.js
213 ms
1bNoFZUdlYZ.js
224 ms
spotlight-poi.png
164 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
276 ms
css
224 ms
transparent.png
124 ms
vt
61 ms
vt
175 ms
vt
57 ms
vt
57 ms
vt
81 ms
vt
192 ms
vt
140 ms
google4.png
134 ms
mapcnt6.png
135 ms
sv5.png
136 ms
tmapctrl.png
134 ms
cb_scout5.png
135 ms
tmapctrl4.png
137 ms
imgs8.png
161 ms
432244_390816714279935_128161354_n.jpg
203 ms
786_1211964925498439_1724893636693398444_n.jpg
130 ms
12705295_10206970922444687_1528079808817180077_n.jpg
213 ms
10390569_1535172106767469_7296123777147738950_n.jpg
170 ms
12744496_1089433734435100_5204248540509604102_n.jpg
169 ms
10399677_985566791520274_231230452229961272_n.jpg
146 ms
11701039_920037258039898_9016796802172013569_n.jpg
168 ms
10888491_778683242211160_3745181750052189848_n.jpg
202 ms
wL6VQj7Ab77.png
127 ms
s7jcwEQH7Sx.png
126 ms
postmessageRelay
194 ms
7MdLVpnw_normal.jpeg
215 ms
2a1030bffd287d5d54a91a9089251d60_normal.jpeg
215 ms
logo_normal.JPG
260 ms
m2qEJmP4_normal.png
317 ms
7cb28547fad6aa04cbc9c617e51071a2_normal.png
306 ms
2s3ho0dqtw7e6jamx6ik_normal.jpeg
435 ms
YJzti5WI_normal.jpg
329 ms
jgcHV5Wb_normal.jpg
511 ms
ZNnXw_Np_normal.jpg
327 ms
mJJczfiy_normal.jpg
334 ms
cb=gapi.loaded_0
63 ms
cb=gapi.loaded_1
60 ms
AuthenticationService.Authenticate
279 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
44 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
72 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
100 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
112 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
132 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.nl.html
96 ms
I6-MnjEovm5.js
23 ms
pQrUxxo5oQp.js
22 ms
3193398744-postmessagerelay.js
48 ms
rpc:shindig_random.js
47 ms
cb=gapi.loaded_0
4 ms
jot
82 ms
hoorngids.nl 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
hoorngids.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hoorngids.nl SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hoorngids.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Hoorngids.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.
hoorngids.nl
Open Graph description is not detected on the main page of Hoorn Gids. 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: