Tools & Wizards About Us
foobie.nl screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

foobie.nl

Het meeste informatie blog van Nederland - Foobie.nl

Page Load Speed

4.7 sec in total

First Response

599 ms

Resources Loaded

3.8 sec

Page Rendered

269 ms

foobie.nl screenshot

About Website

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.nl

Key Findings

We analyzed Foobie.nl page load time and found that the first response time was 599 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

foobie.nl performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

foobie.nl

599 ms

js

84 ms

style.min.css

70 ms

mediaelementplayer-legacy.min.css

75 ms

wp-mediaelement.min.css

75 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 40% of them (18 requests) were addressed to the original Foobie.nl, 31% (14 requests) were made to Fonts.gstatic.com and 18% (8 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (621 ms) belongs to the original domain Foobie.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 166.5 kB (23%)

Content Size

720.5 kB

After Optimization

554.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foobie.nl main page is 720.5 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. 50% of websites need less resources to load. Javascripts take 357.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 139.0 kB

  • Original 166.6 kB
  • After minification 157.5 kB
  • After compression 27.7 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 139.0 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 5.6 kB
  • After minification 5.6 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. Foobie images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 357.8 kB
  • After minification 357.8 kB
  • After compression 355.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. This website has mostly compressed JavaScripts.

CSS Optimization

-13%

Potential reduce by 25.4 kB

  • Original 190.4 kB
  • After minification 190.4 kB
  • After compression 165.0 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 25.4 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (90%)

Requests Now

29

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 29 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 16 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

foobie.nl

foobie.nl

599 ms

js

js

84 ms

style.min.css

style.min.css

70 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

75 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

75 ms

styles.css

styles.css

179 ms

widget-options.css

widget-options.css

264 ms

style.css

style.css

272 ms

css

css

80 ms

style.css

style.css

370 ms

td_legacy_main.css

td_legacy_main.css

561 ms

demo_style.css

demo_style.css

283 ms

tdb_less_front.css

tdb_less_front.css

285 ms

jetpack.css

jetpack.css

61 ms

frontend-gtag.min.js

frontend-gtag.min.js

349 ms

jquery.min.js

jquery.min.js

72 ms

jquery-migrate.min.js

jquery-migrate.min.js

71 ms

adsbygoogle.js

adsbygoogle.js

137 ms

index.js

index.js

329 ms

index.js

index.js

351 ms

tdModalPostImages.js

tdModalPostImages.js

350 ms

underscore.min.js

underscore.min.js

40 ms

js_posts_autoload.min.js

js_posts_autoload.min.js

404 ms

tagdiv_theme.min.js

tagdiv_theme.min.js

621 ms

comment-reply.min.js

comment-reply.min.js

39 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

429 ms

e-202419.js

e-202419.js

42 ms

js_files_for_front.min.js

js_files_for_front.min.js

434 ms

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

85 ms

KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf

85 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

172 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

173 ms

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

176 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

174 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

175 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

174 ms

newspaper.woff

newspaper.woff

330 ms

KFOkCnqEu92Fr1Mu51xIIzcXKMny.ttf

KFOkCnqEu92Fr1Mu51xIIzcXKMny.ttf

173 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsHYl4BO.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsHYl4BO.ttf

174 ms

show_ads_impl.js

show_ads_impl.js

292 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYCSUhiCnAw.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYCSUhiCnAw.ttf

91 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexYMUdjFnmg.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexYMUdjFnmg.ttf

92 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexYMUdjFnmg.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexYMUdjFnmg.ttf

92 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexYMUdjFnmg.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexYMUdjFnmg.ttf

244 ms

foobie-2-300x103.png

foobie-2-300x103.png

107 ms

Accessibility Review

foobie.nl accessibility score

97

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

foobie.nl best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

foobie.nl SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    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 does not match the claimed English 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.

Social Sharing Optimization

foobie.nl

Open Graph data is detected on the main page of Foobie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: