5.9 sec in total
1.9 sec
3.8 sec
221 ms
Visit banaan.nl now to see the best up-to-date Banaan content and also check out these interesting facts you probably never knew about banaan.nl
Ontdek heerlijke bananenrecepten, interessante feiten en handige tips op banaan.nl.
Visit banaan.nlWe analyzed Banaan.nl page load time and found that the first response time was 1.9 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
banaan.nl performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value12.5 s
0/100
25%
Value15.4 s
1/100
10%
Value50,270 ms
0/100
30%
Value0.001
100/100
15%
Value64.6 s
0/100
10%
1880 ms
353 ms
232 ms
230 ms
477 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that 76% of them (19 requests) were addressed to the original Banaan.nl, 8% (2 requests) were made to Pagead2.googlesyndication.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Banaan.nl.
Page size can be reduced by 242.5 kB (56%)
433.8 kB
191.4 kB
In fact, the total size of Banaan.nl main page is 433.8 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. 25% of websites need less resources to load. Javascripts take 284.3 kB which makes up the majority of the site volume.
Potential reduce by 35.4 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 35.4 kB or 68% of the original size.
Potential reduce by 1.9 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. Banaan images are well optimized though.
Potential reduce by 138.3 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 138.3 kB or 49% of the original size.
Potential reduce by 66.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. Banaan.nl needs all CSS files to be minified and compressed as it can save up to 66.9 kB or 85% of the original size.
Number of requests can be reduced by 17 (74%)
23
6
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Banaan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.banaan.nl
1880 ms
wp-emoji-release.min.js
353 ms
styles.css
232 ms
cli-style.css
230 ms
style.css
477 ms
responsive.css
242 ms
style.css
543 ms
green.css
551 ms
jquery.js
689 ms
jquery-migrate.min.js
357 ms
cookielawinfo.js
465 ms
responsive-modernizr.min.js
602 ms
adsbygoogle.js
7 ms
cookieconsent.latest.min.js
15 ms
jquery.form.min.js
391 ms
scripts.js
394 ms
responsive-scripts.min.js
471 ms
jquery.placeholder.min.js
471 ms
wp-embed.min.js
592 ms
ga.js
218 ms
cropped-banaan.jpg
247 ms
overlay.png
243 ms
ca-pub-9654285304929543.js
88 ms
zrt_lookup.html
85 ms
__utm.gif
26 ms
banaan.nl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
banaan.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
banaan.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 Banaan.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 Banaan.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.
banaan.nl
Open Graph description is not detected on the main page of Banaan. 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: