Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

fooss.nl

Fooss.nl - De woonwinkel voor uw design meubelen en woonaccessoires

Page Load Speed

7.6 sec in total

First Response

308 ms

Resources Loaded

5.5 sec

Page Rendered

1.8 sec

fooss.nl screenshot

About Website

Welcome to fooss.nl homepage info - get ready to check Fooss best content right away, or after learning these important things about fooss.nl

Online woonwinkel met een groot assortiment Meubels, Design stoelen, Barkrukken, Lampen en Woonaccessoires. ✓Snelle Levering ✓Laagste Prijs

Visit fooss.nl

Key Findings

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

Performance Metrics

fooss.nl performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

fooss.nl

308 ms

www.fooss.nl

2677 ms

4be50708c50ef011b29f8977aeea7520.css

475 ms

gtm.js

120 ms

lazy.png

115 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 95% of them (19 requests) were addressed to the original Fooss.nl, 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Fooss.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 198.7 kB (48%)

Content Size

411.6 kB

After Optimization

212.9 kB

In fact, the total size of Fooss.nl main page is 411.6 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. 30% of websites need less resources to load. HTML takes 233.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 196.8 kB

  • Original 233.6 kB
  • After minification 233.2 kB
  • After compression 36.8 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 196.8 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 1.5 kB

  • Original 106.0 kB
  • After minification 104.5 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. Fooss images are well optimized though.

CSS Optimization

-1%

Potential reduce by 441 B

  • Original 72.1 kB
  • After minification 72.1 kB
  • After compression 71.7 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. Fooss.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (38%)

Requests Now

16

After Optimization

10

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fooss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Accessibility Review

fooss.nl accessibility score

87

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

fooss.nl SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fooss.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 Fooss.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

Open Graph description is not detected on the main page of Fooss. 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: