6 sec in total
362 ms
5 sec
605 ms
Click here to check amazing Geschiedenis 24 content. Otherwise, check out these important facts you probably never knew about geschiedenis24.nl
Andere Tijden, het geschiedenisprogramma van de NTR en VPRO met reportages over (bijna) vergeten gebeurtenissen uit de recente geschiedenis.
Visit geschiedenis24.nlWe analyzed Geschiedenis24.nl page load time and found that the first response time was 362 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
geschiedenis24.nl performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value9.6 s
0/100
25%
Value8.3 s
19/100
10%
Value60 ms
100/100
30%
Value0.011
100/100
15%
Value8.4 s
39/100
10%
362 ms
355 ms
656 ms
170 ms
177 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Geschiedenis24.nl, 62% (31 requests) were made to Npogeschiedenis.nl and 12% (6 requests) were made to Files.vpro.nl. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Images.poms.omroep.nl.
Page size can be reduced by 87.7 kB (60%)
146.1 kB
58.5 kB
In fact, the total size of Geschiedenis24.nl main page is 146.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 55.4 kB which makes up the majority of the site volume.
Potential reduce by 38.9 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 10.5 kB, which is 21% 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 38.9 kB or 78% of the original size.
Potential reduce by 1.1 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. Geschiedenis 24 images are well optimized though.
Potential reduce by 37.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 37.7 kB or 68% of the original size.
Potential reduce by 9.9 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. Geschiedenis24.nl needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 84% of the original size.
Number of requests can be reduced by 9 (24%)
37
28
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geschiedenis 24. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
geschiedenis24.nl
362 ms
www.geschiedenis24.nl
355 ms
www.npogeschiedenis.nl
656 ms
www.npogeschiedenis.nl
170 ms
www.npogeschiedenis.nl
177 ms
www.npogeschiedenis.nl
171 ms
www.npogeschiedenis.nl
170 ms
www.npogeschiedenis.nl
337 ms
font.css
730 ms
font.css
745 ms
style.css
171 ms
npo_cc_styles.css
115 ms
groepsfoto%20voor%20Anne.jpg.jpg
256 ms
Jaren60WEB.jpg.jpg
254 ms
nieuwsbrief.jpg
256 ms
ovt_logo.jpg
174 ms
Andere-Tijden.jpeg
255 ms
4.%20AHN%2021-04-1965_frame_991.jpg.jpg
347 ms
verborgen-verleden.jpg.jpg
425 ms
Bosch%20digitaal.jpg.jpg
589 ms
MijnKamp.jpg
544 ms
16726582.jpeg
509 ms
Zwartendijk.jpg.jpg
507 ms
Cees%20Fasseur.jpg
600 ms
untitled.jpg
736 ms
require.js
860 ms
722581.jpg
1005 ms
logo.svg
175 ms
search-zoom-28-white.png
181 ms
npo_logo_29x29.png
181 ms
gs-icons-sbcd8e56b0b.png
181 ms
transwhite95.png
179 ms
histomap-lv2.jpg
203 ms
NPO_geschiedenis_logo_(vierkant-1028px).jpg
344 ms
Family_watching_television_1958-small.jpg
347 ms
footer.png
346 ms
footer.png
345 ms
MetaWeb-Normal.woff
237 ms
KievitWeb.woff
244 ms
KievitWeb-Medi.woff
356 ms
MetaWeb-Bold.woff
366 ms
impl.js
253 ms
strap.js
253 ms
konami.js
254 ms
jquery.min.js
6 ms
cconsent-1.6.2.min.js
334 ms
bg_gradient.gif
113 ms
sprite2.png
218 ms
masonry.js
267 ms
omrndbd_-webfont-b53f41a7ef0bf4c19c2604a4475b2e5a.woff
546 ms
geschiedenis24.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
Image elements do not have [alt] attributes
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.
geschiedenis24.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
geschiedenis24.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 Geschiedenis24.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 Geschiedenis24.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.
geschiedenis24.nl
Open Graph data is detected on the main page of Geschiedenis 24. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: