31.7 sec in total
389 ms
28.2 sec
3.1 sec
Visit eekaa.com now to see the best up-to-date Eekaa content and also check out these interesting facts you probably never knew about eekaa.com
Visit eekaa.comWe analyzed Eekaa.com page load time and found that the first response time was 389 ms and then it took 31.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
eekaa.com performance score
name
value
score
weighting
Value12.5 s
0/100
10%
Value0
0/100
25%
Value19.5 s
0/100
10%
Value210 ms
88/100
30%
Value0.002
100/100
15%
Value26.1 s
0/100
10%
389 ms
2768 ms
95 ms
312 ms
2213 ms
Our browser made a total of 197 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Eekaa.com, 50% (98 requests) were made to Eekaa.gr and 10% (20 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (15.9 sec) relates to the external source Eekaa.gr.
Page size can be reduced by 144.6 kB (37%)
395.4 kB
250.8 kB
In fact, the total size of Eekaa.com main page is 395.4 kB. 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. Javascripts take 298.4 kB which makes up the majority of the site volume.
Potential reduce by 6.9 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 6.9 kB or 71% of the original size.
Potential reduce by 507 B
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. Eekaa images are well optimized though.
Potential reduce by 134.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 134.4 kB or 45% of the original size.
Potential reduce by 2.8 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. Eekaa.com needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 37% of the original size.
Number of requests can be reduced by 116 (64%)
182
66
The browser has sent 182 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eekaa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 72 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
eekaa.com
389 ms
www.eekaa.gr
2768 ms
css
95 ms
toolbar.css
312 ms
style.css
2213 ms
frontend.css
531 ms
advps-style.css
322 ms
styles.css
366 ms
frontend.css
357 ms
font-awesome.min.css
650 ms
bootstrap.css
15935 ms
front.css
13341 ms
style.css
561 ms
fb-calendar.css
1272 ms
style2-os.css
840 ms
lightbox.css
968 ms
font-awesome.css
4218 ms
style.css
5594 ms
superfish.css
1511 ms
prettyPhoto.css
1893 ms
flexslider.css
2072 ms
responsive.css
4910 ms
colour.css
4712 ms
css
140 ms
upw-theme-standard.min.css
5881 ms
jquery.js
11043 ms
jquery-migrate.min.js
5104 ms
flags.js
6508 ms
toolbar.js
7946 ms
load-toolbar.js
6083 ms
js
850 ms
advps.frnt.script.js
6293 ms
jquery.bxslider.min.js
6484 ms
bootstrap.min.js
10420 ms
front.js
6700 ms
chosen.jquery.min.js
7942 ms
all.js
13511 ms
wp-emoji-release.min.js
8245 ms
embed.js
9769 ms
js
5194 ms
element.js
5432 ms
helpers.js
9882 ms
jquery.dropdown.js
8411 ms
jquery-ui.min.js
260 ms
jquery.ebpFullCalendar.js
8592 ms
frontend.js
10534 ms
aflb.js
9947 ms
jquery.form.min.js
10330 ms
scripts.js
12714 ms
underscore.min.js
10384 ms
moment.min.js
11552 ms
moment-timezone.min.js
11800 ms
clndr.min.js
10713 ms
scripts.js
10818 ms
jquery.colorbox.js
10874 ms
gallery-all.js
10762 ms
jquery.hugeitmicro.min.js
10702 ms
tinynav.min.js
10387 ms
jquery.uniform.js
10328 ms
superfish.js
10297 ms
jquery.prettyPhoto.js
8385 ms
jquery.flexslider-min.js
7894 ms
scripts.js
7732 ms
wp-embed.min.js
7669 ms
css
461 ms
phone_icon_01.png
694 ms
email_icon_01.png
693 ms
gasa12.jpg
694 ms
social_facebook.png
763 ms
social_youtube.png
762 ms
dot_border_h.png
892 ms
dot_border_v.png
882 ms
search_icon.png
882 ms
loader_01.gif
884 ms
LOGO-%CE%91%CE%93%CE%93%CE%9B%CE%99%CE%9A%CE%91-%CE%A5%CE%A8%CE%97%CE%9B%CE%97-%CE%91%CE%9D%CE%91%CE%9B%CE%A5%CE%A3%CE%97-%CE%9A%CE%95%CE%A6%CE%91%CE%9B%CE%91%CE%99%CE%91-1024x382.jpg
1454 ms
site-2.png
1103 ms
site-front-1024x570.jpg
2922 ms
site-2-a.png
1097 ms
site-1a.png
1101 ms
site-3-a.png
1102 ms
site-5-a.png
1162 ms
site-4-a.png
1213 ms
button_bg.png
1216 ms
rss.png
1451 ms
list_05.png
1454 ms
aha_logo.gif
1508 ms
ERC_logo.gif
1508 ms
12105966_10207741658038486_5506789340613287984_n.jpg
2921 ms
%CE%92%CE%91%CE%9D%CE%9D%CE%95%CE%A1-150x150.jpg
1491 ms
EPALS1-150x150.jpg
2310 ms
airway-management-2-150x150.jpg
1631 ms
PubMed-Logo.png
3284 ms
logo-new-15-x-15-cm.jpg
5685 ms
%CE%92%CE%91%CE%9D%CE%9D%CE%95%CE%A1.jpg
2885 ms
630 ms
dot_border_h_transparent.png
2926 ms
phone_icon_02.png
2672 ms
email_icon_02.png
2668 ms
xd_arbiter.php
413 ms
xd_arbiter.php
827 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
231 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
414 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
624 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
624 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
487 ms
RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf
616 ms
ZvcMqxEwPfh2qDWBPxn6ngV_pQ1T3xN3K1c3sB361us.ttf
622 ms
ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf
623 ms
ZvcMqxEwPfh2qDWBPxn6nvzeo8SCrGyBsNQUDsw2Qr8.ttf
603 ms
common.js
126 ms
map.js
133 ms
util.js
388 ms
geocoder.js
148 ms
flags18.png
2300 ms
arrow_up.png
2091 ms
StaticMapService.GetMapImage
340 ms
sdk.js
4683 ms
translateelement.css
977 ms
main.js
1066 ms
onion.js
882 ms
openhand_8_8.cur
507 ms
ViewportInfoService.GetViewportInfo
157 ms
stats.js
140 ms
controls.js
242 ms
AuthenticationService.Authenticate
743 ms
GeocodeService.Search
407 ms
vt
72 ms
vt
72 ms
vt
270 ms
vt
269 ms
transparent.png
599 ms
css
140 ms
marker.js
181 ms
analytics.js
237 ms
google4.png
102 ms
mapcnt6.png
220 ms
sv5.png
222 ms
tmapctrl.png
463 ms
cb_scout5.png
718 ms
tmapctrl4.png
463 ms
imgs8.png
464 ms
element_main.js
1440 ms
collect
140 ms
infowindow.js
72 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
1059 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
1083 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
1093 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
1114 ms
StaticMapService.GetMapImage
1053 ms
vt
1031 ms
ViewportInfoService.GetViewportInfo
1025 ms
ping
321 ms
11030409.json
264 ms
fb1-right.png
299 ms
flags.png
1020 ms
ajax-loader.gif
294 ms
closebtn.svg
690 ms
closeBig.png
292 ms
arrow_down.png
554 ms
select.png
554 ms
spotlight-poi.png
261 ms
translate_24dp.png
300 ms
l
199 ms
googlelogo_color_42x16dp.png
348 ms
page.php
402 ms
common.js
260 ms
util.js
527 ms
stats.js
281 ms
embed-runner.js
2564 ms
page_1_thumb_large.jpg
500 ms
quant.js
341 ms
vt
307 ms
vt
112 ms
vt
207 ms
vt
470 ms
vt
417 ms
ik8d09sCUBr.css
286 ms
h0O-5u1ruio.css
335 ms
SRSW8M763HA.js
827 ms
3k9g4dfmgsB.js
505 ms
XokP-R2tSzH.js
452 ms
12509263_1229129343768561_8017198643843559726_n.jpg
676 ms
1236078_969775933037238_1410874134684268584_n.jpg
711 ms
12662725_155559288155128_1681043167762759224_n.jpg
755 ms
10644438_945770515507259_7894388656336193399_n.jpg
841 ms
10885090_327738797425333_2132971104832388677_n.jpg
787 ms
1379841_10150004552801901_469209496895221757_n.jpg
787 ms
12931055_1004121283015107_6110993445956632327_n.jpg
786 ms
wL6VQj7Ab77.png
61 ms
Wh-wXqXludh.png
65 ms
R9GKCzjAnbk.js
437 ms
AWWjhOengNF.js
456 ms
YnSasnyq68i.js
457 ms
kQf_jlUv-kX.js
469 ms
arrow_prev_02.png
1062 ms
arrow_next_02.png
918 ms
QuotaService.RecordEvent
102 ms
eekaa.com 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
<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
eekaa.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
eekaa.com SEO score
EL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eekaa.com can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it does not match the claimed English language. Our system also found out that Eekaa.com 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.
eekaa.com
Open Graph description is not detected on the main page of Eekaa. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: