Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

eekaa.com

eekaa.org

Page Load Speed

31.7 sec in total

First Response

389 ms

Resources Loaded

28.2 sec

Page Rendered

3.1 sec

eekaa.com screenshot

About Website

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.com

Key Findings

We 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.

Performance Metrics

eekaa.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value26.1 s

0/100

10%

Network Requests Diagram

eekaa.com

389 ms

www.eekaa.gr

2768 ms

css

95 ms

toolbar.css

312 ms

style.css

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 Optimization Overview & Recommendations

Page size can be reduced by 144.6 kB (37%)

Content Size

395.4 kB

After Optimization

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.

HTML Optimization

-71%

Potential reduce by 6.9 kB

  • Original 9.6 kB
  • After minification 8.8 kB
  • After compression 2.7 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.

Image Optimization

-1%

Potential reduce by 507 B

  • Original 79.9 kB
  • After minification 79.4 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. Eekaa images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 134.4 kB

  • Original 298.4 kB
  • After minification 298.4 kB
  • After compression 163.9 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.

CSS Optimization

-37%

Potential reduce by 2.8 kB

  • Original 7.5 kB
  • After minification 7.0 kB
  • After compression 4.7 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.

Requests Breakdown

Number of requests can be reduced by 116 (64%)

Requests Now

182

After Optimization

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.

Accessibility Review

eekaa.com accessibility score

33

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

<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

High

<html> element does not have a [lang] attribute

Best Practices

eekaa.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

eekaa.com SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EL

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: