2.9 sec in total
442 ms
2.2 sec
282 ms
Visit foobie.nl now to see the best up-to-date Foobie content for Netherlands and also check out these interesting facts you probably never knew about foobie.nl
Op Foobie vind je vele artikelen over diverse onderwerpen geschreven door onze bloggers. Van lifestyle tot gezondheid tot zakelijk. Lees het hier!
Visit foobie.nlWe analyzed Foobie.nl page load time and found that the first response time was 442 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
foobie.nl performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value4.7 s
32/100
25%
Value8.3 s
19/100
10%
Value210 ms
89/100
30%
Value0
100/100
15%
Value5.6 s
70/100
10%
442 ms
281 ms
185 ms
4 ms
8 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 60% of them (38 requests) were addressed to the original Foobie.nl, 16% (10 requests) were made to Google.com and 6% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Foobie.nl.
Page size can be reduced by 957.8 kB (57%)
1.7 MB
735.0 kB
In fact, the total size of Foobie.nl main page is 1.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. 55% of websites need less resources to load. Javascripts take 848.3 kB which makes up the majority of the site volume.
Potential reduce by 123.3 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 123.3 kB or 77% of the original size.
Potential reduce by 166.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. Obviously, Foobie needs image optimization as it can save up to 166.3 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 539.6 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 539.6 kB or 64% of the original size.
Potential reduce by 128.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. Foobie.nl needs all CSS files to be minified and compressed as it can save up to 128.6 kB or 85% of the original size.
Number of requests can be reduced by 15 (26%)
57
42
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foobie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
foobie.nl
442 ms
bootstrap.css
281 ms
foobie.css
185 ms
bootstrap-glyphicons.css
4 ms
addthis_widget.js
8 ms
jquery2.1.1.js
380 ms
bootstrap.min.js
276 ms
analytics.js
31 ms
foobie.png
637 ms
computers.png
720 ms
gezondheid.png
721 ms
wonen.png
720 ms
dieren.png
977 ms
onderwijs.png
1053 ms
eten.png
811 ms
verslagen.png
901 ms
werk.png
902 ms
financieel.png
992 ms
beauty.png
993 ms
leven.png
993 ms
recensies.png
994 ms
regios.png
1158 ms
kunst.png
1085 ms
vrijetijd.png
1097 ms
foobie_gerelateerd.png
1086 ms
samenleving.png
1088 ms
reizen.png
1143 ms
sport.png
1178 ms
natuur.png
1177 ms
muziek.png
1178 ms
zakelijk.png
1188 ms
auto.png
1234 ms
electronica.png
1248 ms
media.png
1357 ms
games.png
1357 ms
meningen.png
1269 ms
spiritueel.png
1279 ms
lijstjes.png
1325 ms
cultuur.png
1429 ms
discussie.png
1360 ms
glyphicons-halflings-regular.woff
12 ms
MetaPro-BlackItalic.otf
1536 ms
collect
11 ms
collect
56 ms
cse.js
17 ms
boost
11 ms
300lo.json
70 ms
sh.07f0d9bf220d07a763adad1e.html
22 ms
cse.js
165 ms
layers.173914a8ea2767730b7b.js
21 ms
nl.js
4 ms
jsapi
29 ms
default+nl.css
5 ms
default.css
32 ms
default+nl.I.js
9 ms
default.css
40 ms
async-ads.js
60 ms
google_custom_search_watermark.gif
34 ms
small-logo.png
14 ms
search_box_icon.png
12 ms
clear.gif
14 ms
nav_logo114.png
6 ms
views2.json
89 ms
foobie.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
Links do not have a discernible name
foobie.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
foobie.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 Foobie.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 Foobie.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.
foobie.nl
Open Graph description is not detected on the main page of Foobie. 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: