4 sec in total
439 ms
3.2 sec
293 ms
Click here to check amazing KPN content for Netherlands. Otherwise, check out these important facts you probably never knew about kpn.nl
Met KPN Combivoordeel stel je al jouw thuis en mobiele abonnementen zelf samen. Internet, mobiel, TV, entertainment en meer. Via het netwerk van Nederland.
Visit kpn.nlWe analyzed Kpn.nl page load time and found that the first response time was 439 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
kpn.nl performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value19.1 s
0/100
25%
Value7.4 s
27/100
10%
Value430 ms
65/100
30%
Value0
100/100
15%
Value16.3 s
5/100
10%
439 ms
115 ms
85 ms
614 ms
36 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 42% of them (22 requests) were addressed to the original Kpn.nl, 15% (8 requests) were made to Kpn.blueconic.net and 15% (8 requests) were made to Kpn.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Kpn.com.
Page size can be reduced by 1.3 MB (62%)
2.2 MB
829.7 kB
In fact, the total size of Kpn.nl main page is 2.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. 50% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 136.2 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. This page needs HTML code to be minified as it can gain 29.8 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 136.2 kB or 87% of the original size.
Potential reduce by 41.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. KPN images are well optimized though.
Potential reduce by 992.2 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 992.2 kB or 73% of the original size.
Potential reduce by 158.1 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. Kpn.nl needs all CSS files to be minified and compressed as it can save up to 158.1 kB or 84% of the original size.
Number of requests can be reduced by 24 (55%)
44
20
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KPN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
kpn.nl
439 ms
screen.css
115 ms
1629614474.js
85 ms
blueconic.min.js
614 ms
satelliteLib-70479c0fd48d12c904ac8537f56f61e796abb1dc.js
36 ms
bbEmbedPlayer.js
387 ms
special.css
211 ms
main-optimized.min.js
488 ms
geo2.js
145 ms
event
37 ms
KPN-Sans-Light-WF.woff
322 ms
event
8 ms
149 ms
menu_tablet_mobile.svg
1369 ms
search.svg
144 ms
d154631b-b83c-47e7-bb34-0f4c63263462_kpn_samsung-galaxy-s7-deskL.jpg
194 ms
31b33ebd-1141-425b-8062-ff7f254c9c06_kpn_spotify-premium-deskL.jpg
339 ms
bf30c04e-ca77-450e-a079-db4022837859_forum-deskL.jpg
276 ms
a62db1ed-9ae4-4ab2-b871-de0b0e42ede6_netflix-app-1920-deskL.jpg
580 ms
logo-kpn-groot.png
1356 ms
859c159c-ce91-45f9-8287-730f252a4832_160217-megamenu-samsung-galaxy-s7-serie.png
1370 ms
ae8069f8-d5bf-4d35-9077-1da379ac3f4b_alles-in-1%20kpn.png
1385 ms
69a6d4c1-5aff-424f-bb6b-01fe8db2d53e_5-euro-korting-kpn-compleet.png
1369 ms
logo-kpn-klein.png
1373 ms
kpn-logo.png
1442 ms
main.js
294 ms
init.js
295 ms
satellite-5422c3fe4d8a3c54d100045b.js
44 ms
s-code-contents-43d7a7650c738bfe3d87a71a4a63162ef9e7b51e.js
85 ms
KPN-Sans-Normal-WF.woff
446 ms
KPN-Sans-Bold-WF.woff
383 ms
KPN-Accent-Light-WF.woff
317 ms
KPN-Accent-Normal-WF.woff
332 ms
KPN-Accent-Bold-WF.woff
389 ms
KPN-Icons.woff
427 ms
ba2294b51bcfaaaa799999f169090631
166 ms
95 ms
a5360e123bbce46d89107f479935c248
339 ms
utils.js
180 ms
sidenav.js
226 ms
autocomplete.js
247 ms
select.js
260 ms
tooltip.js
273 ms
et.va.js
14 ms
jquery.min.js
63 ms
s76044969887007
40 ms
jquery-ui.min.js
22 ms
cookie-620x120.jpg
164 ms
83 ms
110 ms
kpn_logo.png
970 ms
dcx.va-2.0.0.8.min.js
37 ms
kpn.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
kpn.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
Browser errors were logged to the console
Page has valid source maps
kpn.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kpn.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 Kpn.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.
kpn.nl
Open Graph description is not detected on the main page of KPN. 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: