Tools & Wizards About Us
febo.nl screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

febo.nl

FEBO, gemaakt voor jou en elke dag vers

Page Load Speed

2.9 sec in total

First Response

279 ms

Resources Loaded

1.6 sec

Page Rendered

986 ms

febo.nl screenshot

About Website

Welcome to febo.nl homepage info - get ready to check FEBO best content for Netherlands right away, or after learning these important things about febo.nl

Officiële website Febo. Meer dan 66 winkels. Alle snacks, dagelijks vers bereid volgens authentiek recept. Daar snackt toch iedereen naar!

Visit febo.nl

Key Findings

We analyzed Febo.nl page load time and found that the first response time was 279 ms and then it took 2.6 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.

Performance Metrics

febo.nl performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.653

8/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

www.febo.nl

279 ms

wp-emoji-release.min.js

77 ms

styles.min.css

150 ms

fonts.base.min.css

152 ms

wp.febo.core.min.css

152 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 74% of them (31 requests) were addressed to the original Febo.nl, 10% (4 requests) were made to Cdnjs.cloudflare.com and 10% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (831 ms) belongs to the original domain Febo.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 515.1 kB (10%)

Content Size

5.1 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Febo.nl main page is 5.1 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. Images take 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 51.3 kB

  • Original 58.6 kB
  • After minification 56.9 kB
  • After compression 7.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 51.3 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 39.9 kB

  • Original 4.4 MB
  • After minification 4.4 MB

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. FEBO images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 381.9 kB

  • Original 581.0 kB
  • After minification 580.9 kB
  • After compression 199.1 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 381.9 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 42.0 kB

  • Original 50.4 kB
  • After minification 50.2 kB
  • After compression 8.4 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. Febo.nl needs all CSS files to be minified and compressed as it can save up to 42.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (58%)

Requests Now

36

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.febo.nl

www.febo.nl

279 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

77 ms

styles.min.css

styles.min.css

150 ms

fonts.base.min.css

fonts.base.min.css

152 ms

wp.febo.core.min.css

wp.febo.core.min.css

152 ms

wp.febo.home.min.css

wp.febo.home.min.css

156 ms

webfont.js

webfont.js

80 ms

jquery.js

jquery.js

236 ms

jquery-migrate.min.js

jquery-migrate.min.js

164 ms

wp.max.base.min.js

wp.max.base.min.js

220 ms

TweenLite.min.js

TweenLite.min.js

86 ms

TimelineMax.min.js

TimelineMax.min.js

57 ms

CSSPlugin.min.js

CSSPlugin.min.js

65 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

56 ms

wp.max.core.min.js

wp.max.core.min.js

220 ms

modernizr.min.js

modernizr.min.js

220 ms

wp.febo.core.min.js

wp.febo.core.min.js

228 ms

js

js

107 ms

wp.febo.home.min.js

wp.febo.home.min.js

295 ms

wp-embed.min.js

wp-embed.min.js

295 ms

febo_logo.png

febo_logo.png

167 ms

header_nieuw.jpg

header_nieuw.jpg

831 ms

thuisbezorgd2.jpg

thuisbezorgd2.jpg

321 ms

actie-nieuw.jpg

actie-nieuw.jpg

299 ms

Slide-1.png

Slide-1.png

564 ms

helden-kroket.jpg

helden-kroket.jpg

330 ms

vers-gemaakt.png

vers-gemaakt.png

645 ms

home-socialmedia-bg.png

home-socialmedia-bg.png

449 ms

actie-nieuw1.jpg

actie-nieuw1.jpg

640 ms

actie2-img.jpg

actie2-img.jpg

699 ms

bestanden-FB-720x620bezorg.jpg

bestanden-FB-720x620bezorg.jpg

675 ms

IMG_3487-1024x768.jpg

IMG_3487-1024x768.jpg

643 ms

analytics.js

analytics.js

12 ms

vagroundedstd-light.woff

vagroundedstd-light.woff

678 ms

vagroundedstd-bold.woff

vagroundedstd-bold.woff

683 ms

filmotypekingston.woff

filmotypekingston.woff

683 ms

vagroundedstd-thin.woff

vagroundedstd-thin.woff

717 ms

icomoon.ttf

icomoon.ttf

743 ms

common.js

common.js

123 ms

util.js

util.js

149 ms

geocoder.js

geocoder.js

143 ms

collect

collect

19 ms

Accessibility Review

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

febo.nl best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

febo.nl SEO score

92

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 doesn't use 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 Febo.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 Febo.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

febo.nl

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