7.2 sec in total
629 ms
6.1 sec
473 ms
Welcome to khn.nl homepage info - get ready to check KHN best content for Netherlands right away, or after learning these important things about khn.nl
KHN (Koninklijke Horeca Nederland) is dé branchevereniging voor de horeca.
Visit khn.nlWe analyzed Khn.nl page load time and found that the first response time was 629 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
khn.nl performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value7.2 s
5/100
25%
Value5.2 s
60/100
10%
Value2,440 ms
5/100
30%
Value0.556
13/100
15%
Value13.1 s
12/100
10%
629 ms
3010 ms
369 ms
277 ms
536 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 50% of them (50 requests) were addressed to the original Khn.nl, 13% (13 requests) were made to Pbs.twimg.com and 10% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Khn.nl.
Page size can be reduced by 576.9 kB (29%)
2.0 MB
1.4 MB
In fact, the total size of Khn.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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 32.3 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 32.3 kB or 74% of the original size.
Potential reduce by 37.2 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. KHN images are well optimized though.
Potential reduce by 423.7 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 423.7 kB or 73% of the original size.
Potential reduce by 83.7 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. Khn.nl needs all CSS files to be minified and compressed as it can save up to 83.7 kB or 86% of the original size.
Number of requests can be reduced by 45 (47%)
96
51
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KHN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.khn.nl
629 ms
home
3010 ms
layout.css
369 ms
museo.css
277 ms
jquery.mmenu.all.css
536 ms
jquery.min.js
73 ms
spcjs.php
202 ms
jquery.reject.css
357 ms
jquery.reject.js
551 ms
WebResource.axd
557 ms
ScriptResource.axd
550 ms
ScriptResource.axd
453 ms
polar-embedded.js
149 ms
jquery.touchSwipe.min.js
393 ms
jquery.carouFredSel-6.2.1.js
782 ms
jquery.mmenu.min.all.js
506 ms
jquery.scroll.js
584 ms
general.js
583 ms
euopties.js
583 ms
spc.php
85 ms
fl.js
38 ms
analytics.js
64 ms
logo@2x.png
139 ms
menu_item_active.png
96 ms
knssp9zozu.jpg
158 ms
z58gl34zh9.jpg
339 ms
wvi6nt5y2b.jpg
340 ms
1cqbijakzb.jpg
357 ms
3biz6f8f3v.jpg
338 ms
wordLidTekstLayer.png
341 ms
mt21ac5qdu.jpg
411 ms
wyjgy7onvn.jpg
355 ms
wsaazowt58.jpg
415 ms
zezhj3ecpz.jpg
512 ms
twitter_icon@2x.jpg
421 ms
facebook_icon@2x.jpg
471 ms
zoek.png
451 ms
zoek_foutmelding.png
477 ms
rnv2e2jis0.jpg
675 ms
3z4bhvr11r.jpg
692 ms
bmcw0s38p4.jpg
880 ms
rbl76whffa.jpg
774 ms
49ix08y2y4.jpg
791 ms
leesmeer_wit.png
591 ms
bgBannerLidworden.jpg
709 ms
museo500-webfont.woff
758 ms
museo300-webfont.woff
825 ms
2b557a6f-a2f0-4967-ad17-7c8856d6e7a2.js
286 ms
26c91d9d9c4100137c13079b3aebf89b.jpg
281 ms
lg.php
25 ms
widgets.js
136 ms
likebox.php
539 ms
footer_kroontje.png
870 ms
facebook_icon.jpg
811 ms
twitter_icon.jpg
817 ms
linkedin_icon.jpg
833 ms
youtube_icon.jpg
875 ms
collect
63 ms
empty.htm
744 ms
235717
104 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
30 ms
showcase_pijl.png
696 ms
eubalk_dot.png
685 ms
I&AchatOffline.png
729 ms
blank.gif
64 ms
syndication
122 ms
563635537261907969
345 ms
emsprite-999454c3064386a86e338ea6d8a2b120.png
46 ms
235717-large-87b253902b9dc4e6.jpg
164 ms
235717-large-182c8b1b65fb33fd.jpg
150 ms
235717-large-074b51c8b041f2ba.jpg
152 ms
collect
10 ms
roNeOY-tz5Y.css
39 ms
UHhaxo8Cs3k.css
39 ms
_rx8naC75Dy.js
44 ms
x5F9OMjKyLw.js
61 ms
ICDbTSzjQEg.js
43 ms
TTCre3391I0.js
59 ms
1546178_664960200213075_758918691_n.jpg
43 ms
wL6VQj7Ab77.png
6 ms
s7jcwEQH7Sx.png
7 ms
I6-MnjEovm5.js
2 ms
vlXaquuXMrr.js
5 ms
2705.png
139 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
31 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
83 ms
pQ7OqBIK_normal.jpeg
139 ms
PCcoNHsr_normal.jpg
159 ms
DZ3tmX6j_normal.jpeg
193 ms
tjPP0xJZ_normal.jpg
226 ms
pasfoto_linkedin_normal.jpg
247 ms
WnIhH_8o_normal.jpg
253 ms
1RA7N-VO_normal.png
255 ms
Y-cUdumQ_normal.jpeg
255 ms
G4psp5Um_normal.jpeg
257 ms
1xzXyFbU_normal.jpg
277 ms
CcYG4AnXEAA6UXS.jpg:small
283 ms
CcOMtaLWoAA5VJH.jpg:small
287 ms
CcJazpVWEAAkQMB.jpg:small
302 ms
jot
26 ms
khn.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
Links do not have a discernible name
khn.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
Browser errors were logged to the console
Page has valid source maps
khn.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
Tap targets are not sized appropriately
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Khn.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 Khn.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.
khn.nl
Open Graph description is not detected on the main page of KHN. 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: