Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

Page Load Speed

5.6 sec in total

First Response

1.2 sec

Resources Loaded

4.3 sec

Page Rendered

111 ms

freemail.gr screenshot

About Website

Visit freemail.gr now to see the best up-to-date Freemail content for Greece and also check out these interesting facts you probably never knew about freemail.gr

Visit freemail.gr

Key Findings

We analyzed Freemail.gr page load time and found that the first response time was 1.2 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

freemail.gr performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.121

84/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

freemail.gr

1158 ms

www.freemail.gr

1242 ms

libs.css

450 ms

styles.css

882 ms

libs.js

1182 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 87% of them (13 requests) were addressed to the original Freemail.gr, 13% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Freemail.gr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (74%)

Content Size

1.7 MB

After Optimization

447.0 kB

In fact, the total size of Freemail.gr main page is 1.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. 20% of websites need less resources to load. Javascripts take 807.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 371.7 kB

  • Original 448.4 kB
  • After minification 447.3 kB
  • After compression 76.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 371.7 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 910 B

  • Original 87.8 kB
  • After minification 86.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. Freemail images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 569.3 kB

  • Original 807.0 kB
  • After minification 775.5 kB
  • After compression 237.7 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 569.3 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 306.6 kB

  • Original 352.3 kB
  • After minification 298.0 kB
  • After compression 45.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. Freemail.gr needs all CSS files to be minified and compressed as it can save up to 306.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (23%)

Requests Now

13

After Optimization

10

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freemail. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

freemail.gr accessibility score

64

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Low

No form fields have multiple labels

High

Image elements do not have [alt] attributes

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

freemail.gr best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

freemail.gr SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freemail.gr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Freemail.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Freemail. 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: