4 sec in total
286 ms
3.3 sec
436 ms
Welcome to foopla.nl homepage info - get ready to check Foopla best content right away, or after learning these important things about foopla.nl
Lees het als eerst in onze blogs
Visit foopla.nlWe analyzed Foopla.nl page load time and found that the first response time was 286 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
foopla.nl performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
286 ms
405 ms
23 ms
187 ms
181 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 66% of them (35 requests) were addressed to the original Foopla.nl, 8% (4 requests) were made to Facebook.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Foopla.nl.
Page size can be reduced by 444.1 kB (17%)
2.7 MB
2.2 MB
In fact, the total size of Foopla.nl main page is 2.7 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 38.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. 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 38.2 kB or 78% of the original size.
Potential reduce by 127.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. Foopla images are well optimized though.
Potential reduce by 253.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 253.2 kB or 62% of the original size.
Potential reduce by 25.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. Foopla.nl needs all CSS files to be minified and compressed as it can save up to 25.6 kB or 82% of the original size.
Number of requests can be reduced by 22 (43%)
51
29
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foopla. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
foopla.nl
286 ms
www.foopla.nl
405 ms
css
23 ms
coin-slider-styles.css
187 ms
29e6312275a8.css
181 ms
4914a8c6c18b.js
449 ms
css
33 ms
css
43 ms
jquery.cookie.js
186 ms
jquery-ui.min.js
186 ms
mediaelement-and-player.min.js
275 ms
scheduler.js
363 ms
conversion.js
21 ms
dc.js
81 ms
container_bg.png
174 ms
layout-left_allin.png
307 ms
layout-right_promotion.png
381 ms
foopla_logo.jpg
252 ms
header_reviews.jpg
252 ms
header_contact.jpg
252 ms
header-plexiglas.png
914 ms
header-aluminium-wit.png
1026 ms
header-aluminium-rvs.png
1024 ms
header-forex.png
1022 ms
foto_op_plexiglas.png
662 ms
foto_op_aluminium-wit.png
700 ms
foto_op_aluminium-rvs.png
921 ms
foto_op_forex.png
1042 ms
foto_op_hout.png
1268 ms
product-plexiglas.png
1641 ms
icon_googleplus.png
1195 ms
icon_facebook.png
1194 ms
icon_twitter.png
1202 ms
icon_ideal.png
1220 ms
icon_billink.png
1374 ms
fbds.js
69 ms
all.js
292 ms
wiltukorting.png
1358 ms
block_bg_select.jpg
1363 ms
block_bg_orange.jpg
1377 ms
check_complete.png
1424 ms
stempel-allin.png
1661 ms
__utm.gif
76 ms
148 ms
119 ms
13 ms
xd_arbiter.php
80 ms
xd_arbiter.php
136 ms
9 ms
xd_arbiter.php
39 ms
like.php
104 ms
qeKvIRsJabD.js
142 ms
LVx-xkvaJ0b.png
153 ms
foopla.nl accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
foopla.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
foopla.nl SEO score
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foopla.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 Foopla.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.
foopla.nl
Open Graph description is not detected on the main page of Foopla. 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: