5.9 sec in total
1.1 sec
4.5 sec
285 ms
Welcome to eating.be homepage info - get ready to check Eating best content for Belgium right away, or after learning these important things about eating.be
Restaurants, vins métiers gourmands Eating.be, le guide des grandes maisons et des bonnes adresses en Belgique
Visit eating.beWe analyzed Eating.be page load time and found that the first response time was 1.1 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
eating.be performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value10.0 s
0/100
25%
Value5.0 s
63/100
10%
Value90 ms
99/100
30%
Value0.824
4/100
15%
Value3.4 s
93/100
10%
1131 ms
460 ms
306 ms
22 ms
33 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 46% of them (33 requests) were addressed to the original Eating.be, 31% (22 requests) were made to Static.xx.fbcdn.net and 13% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Eating.be.
Page size can be reduced by 183.1 kB (8%)
2.2 MB
2.0 MB
In fact, the total size of Eating.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. 55% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 20.5 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 20.5 kB or 75% of the original size.
Potential reduce by 116.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. Eating images are well optimized though.
Potential reduce by 25.5 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 25.5 kB or 49% of the original size.
Potential reduce by 20.3 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. Eating.be needs all CSS files to be minified and compressed as it can save up to 20.3 kB or 80% of the original size.
Number of requests can be reduced by 31 (44%)
70
39
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eating. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
homepage
1131 ms
functions.js
460 ms
styles.asp
306 ms
css
22 ms
css
33 ms
reset.css
320 ms
main.css
411 ms
jquery.bxslider.css
326 ms
jquery.min.js
28 ms
html5shiv.js
330 ms
jquery.bxslider.min.js
590 ms
custom.js
471 ms
mwTag.js
1176 ms
ga.js
30 ms
__utm.gif
11 ms
2_restaurant_la_manufacture_bruxelles_eating.jpg
1174 ms
2_restaurant_le_chalet_de_la_foret_uccle_eating.jpg
884 ms
2_restaurant_la_fermette_fala_n_dinant_eating.jpg
977 ms
3_la_fermette_sarah_bohet_micha_l_vancraeynest_fala_n_dinant_eating.jpg
919 ms
3_le_chalet_de_la_foret_pascal_devalkeneer_uccle_eating.jpg
645 ms
3_la_manufacture_olivier_schwennicke_bruxelles_eating.jpg
1107 ms
20_restaurant_durbuy_o_eating.jpg
1154 ms
12_restaurant_bruxelles_la_maison_du_luxembourg_eating.jpg
1152 ms
20_restaurant_mons_le_comptoir_de_marie_luc_broutard_eating.jpg
1531 ms
20_restaurant_barvaux_la_chambre_d_amis_glen_et_carine_de_bruyne_eating.jpg
1275 ms
12_restaurant_ixelles_la_canne_en_ville_eating.jpg
1530 ms
sanpellegrino.jpg
1291 ms
theme_1.jpg
1299 ms
theme_2.jpg
1300 ms
theme_3.jpg
1400 ms
theme_4.jpg
1417 ms
theme_5.jpg
1432 ms
d99a10ba80a61280ee614057cd42f8cf4e427a2f.html
271 ms
sprites.png
827 ms
menu_bg.gif
929 ms
sprites_small.png
944 ms
bx_loader.gif
915 ms
rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf
31 ms
likebox.php
259 ms
xYm_UD1pmAz.css
284 ms
TGpOWuX6Pv8.css
355 ms
mEbI724fKQ-.css
421 ms
_rx8naC75Dy.js
620 ms
x5F9OMjKyLw.js
640 ms
ICDbTSzjQEg.js
489 ms
TTCre3391I0.js
488 ms
C-h3nYPqETO.js
552 ms
rFmE1g6Dkoz.js
688 ms
7cm7D75Y0Sf.js
652 ms
oRoBXlHCpEy.js
555 ms
336JejShbZp.js
651 ms
sj-JwAJi4AH.js
712 ms
DKRU1bYTkTw.js
684 ms
ZNPAadQNc33.js
710 ms
W0OV23mIOyO.js
711 ms
36TdwhIHusi.js
719 ms
styles.asp
139 ms
12345413_1006352969422414_9088727548200070032_n.jpg
359 ms
11924288_963362700388108_5802935448577802429_n.jpg
426 ms
1925296_677739428956007_1059258005_n.jpg
494 ms
12439320_10208796646737135_7431104360294229789_n.jpg
586 ms
12088317_934439536634791_8507330247637390667_n.jpg
581 ms
12032201_1638020599815895_4906433275181268552_n.jpg
588 ms
21016_111286745875729_2494887786814614597_n.jpg
590 ms
10492326_110858652623015_3561026462100558967_n.jpg
601 ms
10933992_10152977263582311_6375984484984378634_n.jpg
735 ms
wL6VQj7Ab77.png
77 ms
s7jcwEQH7Sx.png
77 ms
pUFVdPjIRct.png
71 ms
print.css
134 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
136 ms
eating.be accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
eating.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
eating.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eating.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eating.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.
eating.be
Open Graph data is detected on the main page of Eating. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: