3.6 sec in total
333 ms
2.7 sec
559 ms
Visit npogeschiedenis.nl now to see the best up-to-date Npogeschiedenis content for Netherlands and also check out these interesting facts you probably never knew about npogeschiedenis.nl
Andere Tijden, het geschiedenisprogramma van de NTR en VPRO met reportages over (bijna) vergeten gebeurtenissen uit de recente geschiedenis.
Visit npogeschiedenis.nlWe analyzed Npogeschiedenis.nl page load time and found that the first response time was 333 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
npogeschiedenis.nl performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value13.8 s
0/100
25%
Value9.6 s
11/100
10%
Value900 ms
31/100
30%
Value0.018
100/100
15%
Value13.6 s
11/100
10%
333 ms
433 ms
231 ms
23 ms
19 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Npogeschiedenis.nl, 75% (41 requests) were made to Anderetijden.nl and 11% (6 requests) were made to Images.poms.omroep.nl. The less responsive or slowest element that took the longest time to load (761 ms) relates to the external source Anderetijden.nl.
Page size can be reduced by 144.8 kB (7%)
2.2 MB
2.0 MB
In fact, the total size of Npogeschiedenis.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. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 45.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 45.6 kB or 84% of the original size.
Potential reduce by 77.4 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. Npogeschiedenis images are well optimized though.
Potential reduce by 8.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. This website has mostly compressed JavaScripts.
Potential reduce by 13.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. Npogeschiedenis.nl needs all CSS files to be minified and compressed as it can save up to 13.6 kB or 22% of the original size.
Number of requests can be reduced by 7 (15%)
47
40
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Npogeschiedenis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
npogeschiedenis.nl
333 ms
433 ms
anderetijden.nl
231 ms
jquery.min.js
23 ms
piano-analytics.js
19 ms
tag.min.js
293 ms
npoplayer.js
233 ms
npoplayer.css
239 ms
mtiFontTrackingCode.js
93 ms
style.css
190 ms
ntr.anderetijden.homepage.min.js
198 ms
scripts.js
517 ms
scripts.js
286 ms
Andere-Tijden-noline.svg
113 ms
VPRO.svg
111 ms
NTR.svg
109 ms
NPO.svg
201 ms
Facebook.svg
202 ms
Twitter.svg
202 ms
Instagram.svg
216 ms
1.css
83 ms
9bfe6c87-a6dc-43ab-9797-ff3c656e65f0.woff
495 ms
2ba6fbd5-9c17-4733-af15-f49fbecc5c15.woff
410 ms
icons.ttf
228 ms
newsletter.jpg
393 ms
VPRO-white.svg
209 ms
NTR-white.svg
229 ms
3293834c-c7fe-4d69-a914-f94198711fe4.woff
476 ms
14609.w1000.2ca6007.0a40012.jpg
390 ms
2149973.jpg
28 ms
14615.w590.0322a8e.c684e0d.jpg
195 ms
14617.w330.r16-9.c570687.jpg
294 ms
14405.w350.r16-9.2cf3240.jpg
379 ms
2100.w350.r16-9.137b89e.jpg
379 ms
3666.w350.r16-9.7e95887.jpg
397 ms
14591.w380.r3-2.7c4e26c.png
537 ms
14596.w380.r3-2.cc2d29b.png
542 ms
14457.w380.7bdf7a5.68cde4e.jpg
453 ms
14607.w380.r3-2.6d6a335.jpg
455 ms
14561.w380.c9a4d24.73ea291.png
597 ms
14557.w380.36bcb87.4d8496f.jpg
479 ms
14612.w200.r3-2.d853711.png
547 ms
14611.w200.r3-2.a8c8d97.jpg
549 ms
14592.w200.r3-2.70c9bcf.png
573 ms
14593.w200.r3-2.ca37783.png
630 ms
14594.w200.r3-2.115af8c.jpg
636 ms
14589.w200.r3-2.8294177.png
640 ms
14579.w250.63ba8ed.e6fd974.jpg
642 ms
14597.w250.r1-1.6eecf0d.png
761 ms
12951.w250.r1-1.091d0b5.jpg
689 ms
1995142.jpg
29 ms
1995146.jpg
33 ms
1859357.jpg
33 ms
1859358.jpg
34 ms
1852196.jpg
352 ms
npogeschiedenis.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.
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
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.
npogeschiedenis.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
Missing source maps for large first-party JavaScript
npogeschiedenis.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
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Npogeschiedenis.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 Npogeschiedenis.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.
npogeschiedenis.nl
Open Graph data is detected on the main page of Npogeschiedenis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: