Tools & Wizards About Us

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

eggo.be

Cuisine, meuble de rangement et dressing sur mesure | èggo

Page Load Speed

4.1 sec in total

First Response

316 ms

Resources Loaded

3 sec

Page Rendered

737 ms

About Website

Visit eggo.be now to see the best up-to-date Eggo content for Belgium and also check out these interesting facts you probably never knew about eggo.be

Des cuisines et meubles de rangement de qualité à des prix avantageux ! Découvrez nos modèles et prenez rendez-vous en ligne dans votre showroom èggo.

Visit eggo.be

Key Findings

We analyzed Eggo.be page load time and found that the first response time was 316 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 65% of websites can load faster.

Performance Metrics

eggo.be performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value28.0 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value4,940 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value27.7 s

0/100

10%

Network Requests Diagram

eggo.be

316 ms

www.eggo.be

320 ms

en

411 ms

all_dinm_1.css

91 ms

all_chalet-londonnineteensixty_2.css

181 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 87% of them (45 requests) were addressed to the original Eggo.be, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Eggo.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 347.6 kB (16%)

Content Size

2.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eggo.be main page is 2.2 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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 21.8 kB

  • Original 26.8 kB
  • After minification 17.6 kB
  • After compression 5.0 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. This page needs HTML code to be minified as it can gain 9.2 kB, which is 34% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.8 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 31.9 kB

  • Original 1.8 MB
  • After minification 1.8 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. Eggo images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 184.4 kB

  • Original 267.4 kB
  • After minification 201.3 kB
  • After compression 83.0 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 184.4 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 109.4 kB

  • Original 125.0 kB
  • After minification 98.6 kB
  • After compression 15.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. Eggo.be needs all CSS files to be minified and compressed as it can save up to 109.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (57%)

Requests Now

44

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eggo. 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 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

eggo.be accessibility score

72

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

eggo.be 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

Missing source maps for large first-party JavaScript

SEO Factors

eggo.be SEO score

99

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eggo.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Eggo.be 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 data is detected on the main page of Eggo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: