5.7 sec in total
381 ms
4.5 sec
856 ms
Visit e-table.gr now to see the best up-to-date E Table content for Greece and also check out these interesting facts you probably never knew about e-table.gr
Δωρεάν online κρατήσεις σε εστιατόρια, ταβέρνες και μεζεδοπωλεία με αποκλειστικά προνόμια! Χωρίς κουπόνια, χωρίς τηλέφωνο με άμεση επιβεβαίωση!
Visit e-table.grWe analyzed E-table.gr page load time and found that the first response time was 381 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
e-table.gr performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value5.4 s
21/100
25%
Value6.3 s
42/100
10%
Value1,030 ms
26/100
30%
Value0.029
100/100
15%
Value13.4 s
11/100
10%
381 ms
693 ms
812 ms
283 ms
677 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 57% of them (67 requests) were addressed to the original E-table.gr, 3% (4 requests) were made to Google.com and 3% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain E-table.gr.
Page size can be reduced by 836.0 kB (23%)
3.7 MB
2.9 MB
In fact, the total size of E-table.gr main page is 3.7 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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 143.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. This page needs HTML code to be minified as it can gain 51.3 kB, which is 31% 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 143.5 kB or 85% of the original size.
Potential reduce by 110.3 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. E Table images are well optimized though.
Potential reduce by 371.2 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 371.2 kB or 60% of the original size.
Potential reduce by 211.0 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. E-table.gr needs all CSS files to be minified and compressed as it can save up to 211.0 kB or 82% of the original size.
Number of requests can be reduced by 39 (37%)
105
66
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Table. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
e-table.gr
381 ms
www.e-table.gr
693 ms
www.e-table.gr
812 ms
main.css
283 ms
plugins.js
677 ms
javascript.js
450 ms
pmtrack.min.js
461 ms
tl.js
897 ms
datepicker-greek.js
448 ms
lib.v4.js
449 ms
gtm.js
244 ms
magnify_glass.png
124 ms
computer_online.png
124 ms
car.png
124 ms
header_bg.jpg
563 ms
logo_greek.png
246 ms
fine-dine.jpg
305 ms
loyalty.jpg
556 ms
vtour.jpg
740 ms
fam-groupDining.jpg
557 ms
chinesefood.jpg
639 ms
fam-fishTavern.jpg
584 ms
italianfood.jpg
792 ms
fam-brunch.jpg
793 ms
melivemousiki.jpg
794 ms
fam-mexican.jpg
793 ms
tavern.jpg
866 ms
fam-japanese.jpg
988 ms
mezedopoleio.jpg
968 ms
fam-awarded.jpg
1001 ms
romantika.jpg
997 ms
fam-beerRestaurant.jpg
965 ms
fb661e5bceaa9ae98e57c4cdc0d6f332_t.jpg
1068 ms
13b6b82e44cc1bb4fcfd00e91a14e240_t.jpg
1096 ms
b818eedbf1538f2b8b5a75d555e70fa4_t.jpg
1093 ms
424e5ff6ca53323f55903f6ffdc82fee_t.jpg
1186 ms
9fa6702e08b90a06f2b9a01294c48f90_t.jpg
1185 ms
3c10e0cdf7b32d3899c6b77fa6ade2c6_t.jpg
1186 ms
f97c124d311dbec1a1b7243e1191387c_t.jpg
1342 ms
7b53d5c59cfdce0c7d74acf2d98dc05a_t.jpg
1275 ms
43d3cf4189c0c9a27c69d5dc45d325c8_t.jpg
1281 ms
6ebb528d6864cca30c1721bc3a075e8b_t.jpg
1271 ms
b040d4c0adc6e5746adffa905d19af06_t.jpg
1165 ms
23375b90431c49cad5e49fd8d27c8035_t.jpg
1267 ms
fabe34308be036cce1a38c9e4e9c0cec_t.jpg
1360 ms
fontawesome-webfont.woff
1389 ms
glyphicons-halflings-regular.woff
1291 ms
8977f326c14ab0f15527ee777f36fce9_t.jpg
1353 ms
651b6e7479cdd55615d3fced36987d31_t.jpg
1432 ms
analytics.js
78 ms
conversion_async.js
63 ms
560263687c08a7e64a000032.js
378 ms
eng_pxl.js
349 ms
84db829555a0eceea716b5cf4ccaf022_t.jpg
1340 ms
bbc78e9c061fa73931fdd5a7e569a630_t.jpg
1202 ms
278 ms
ec.js
235 ms
010308d589a20cd730a65297125e94cd_t.JPG
1146 ms
project.js
176 ms
3223711588.js
453 ms
cookieconsent.min.js
97 ms
965e808ddec31bfb80bfc48fd0ae0bcb_t.PNG
1244 ms
1a01dc8aa24c7566511e4eff386379d7_t.jpg
1132 ms
collect
22 ms
collect
95 ms
pmtrack.php
576 ms
cc_af.js
211 ms
804a3b3de93ffd3b01a5ae0683ac3cf3_t.jpg
1015 ms
77 ms
8a1812b7aafa1468895070b08b80d81a_t.jpg
1131 ms
track.json
715 ms
t
332 ms
resync.gif
205 ms
discover_bg.jpg
1121 ms
b=22406775
19 ms
tagjs
4 ms
ga-audiences
38 ms
98 ms
adsct
285 ms
Pug
188 ms
pixel
188 ms
iphone_app.png
945 ms
reviews_bg.jpg
994 ms
huffington-post-logo.jpg
984 ms
ingr.jpg
988 ms
lifo.png
1012 ms
fbds.js
326 ms
cb
155 ms
click_at_life.png
978 ms
cb
95 ms
sd
94 ms
tap.php
84 ms
proto_thema.png
901 ms
marketing_week.png
902 ms
epixeiro.png
891 ms
ncm
5 ms
fortune_greece.png
892 ms
enlefko.png
898 ms
cb
4 ms
skai.png
873 ms
action24.jpg
864 ms
25 ms
conversion.js
15 ms
17 ms
28 ms
19 ms
16 ms
dark-top.css
22 ms
rt=ifr
55 ms
bp7yqdr3
96 ms
60 ms
logo.png
51 ms
g.json
74 ms
intercom.bcfdf787.js
50 ms
tp=ANXS
20 ms
echo.515e8809.js
18 ms
362738.gif
19 ms
e-table.gr accessibility score
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 input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
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
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
e-table.gr 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
Page has valid source maps
e-table.gr 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
EL
EL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-table.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it matches the claimed language. Our system also found out that E-table.gr 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.
e-table.gr
Open Graph data is detected on the main page of E Table. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: