4.1 sec in total
316 ms
3 sec
737 ms
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.beWe 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.
eggo.be performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value28.0 s
0/100
25%
Value11.8 s
4/100
10%
Value4,940 ms
0/100
30%
Value0.185
66/100
15%
Value27.7 s
0/100
10%
316 ms
320 ms
411 ms
91 ms
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 size can be reduced by 379.5 kB (17%)
2.2 MB
1.9 MB
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.
Potential reduce by 21.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. 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.
Potential reduce by 31.9 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. Eggo images are well optimized though.
Potential reduce by 216.4 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 216.4 kB or 72% of the original size.
Potential reduce by 109.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. 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.
Number of requests can be reduced by 25 (57%)
44
19
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.
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
all_chalet-parisnineteensixty-webfont_3.css
182 ms
all_chalet-newyorknineteensixty_4.css
182 ms
all_futura-condensedlight_5.css
191 ms
all_normalize_6.css
193 ms
all_screen_7.css
206 ms
all_shame_8.css
267 ms
all_print_9.css
268 ms
all_breadcrumbs_10.css
269 ms
all_custom_11.css
284 ms
modernizr-2.6.2.min.js
380 ms
jquery.min.js
34 ms
all_underscore_1.js
503 ms
all_backbone_2.js
614 ms
all_skrollr.min_3.js
350 ms
all_plugins_4.js
350 ms
all_slider_5.js
373 ms
all_kitchen_6.js
440 ms
all_infiniteScroller_7.js
439 ms
all_maps_8.js
470 ms
all_main_9.js
485 ms
all_color_order_10.js
537 ms
all_scroll-depth_11.js
538 ms
conversion.js
17 ms
analytics.js
20 ms
ipad-home.png
1126 ms
catalog-home.png
856 ms
stove-home.png
513 ms
shop-home-1.jpg
322 ms
shop-home-2.jpg
320 ms
activityi;src=5036330;type=invmedia;cat=khaaylob;ord=852914419956.5052
56 ms
jquery-1.9.1.min.js
515 ms
dinm.woff
495 ms
collect
26 ms
collect
61 ms
ga-audiences
43 ms
logo-en.png
92 ms
make-br-your-project.jpeg
306 ms
sprite.png
91 ms
bg-home-app.jpg
179 ms
bg-home-catalog.jpg
269 ms
spoon-home.png
534 ms
bg-home-why_eggo.jpg
446 ms
bg-home-shop.jpg
360 ms
bg-home-green.jpg
507 ms
join-us-br-on-social-media.jpeg
954 ms
chalet-parisnineteensixty-webfont.woff
381 ms
futura-condensedlight.woff
468 ms
eggo.be 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
ARIA IDs are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eggo.be 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
Missing source maps for large first-party JavaScript
eggo.be 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
FR
EN
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.
eggo.be
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: