Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

edo.io

edo.io

Page Load Speed

6.9 sec in total

First Response

401 ms

Resources Loaded

3.8 sec

Page Rendered

2.7 sec

edo.io screenshot

About Website

Visit edo.io now to see the best up-to-date Edo content for Switzerland and also check out these interesting facts you probably never knew about edo.io

Edo.io is a technology company that builds simple, functional and essential products.

Visit edo.io

Key Findings

We analyzed Edo.io page load time and found that the first response time was 401 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

edo.io performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value4.5 s

83/100

10%

Network Requests Diagram

edo.io

401 ms

www.edo.io

54 ms

style.css

27 ms

css

39 ms

jquery-latest.min.js

5 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 36% of them (22 requests) were addressed to the original Edo.io, 26% (16 requests) were made to Edosite.blob.core.windows.net and 13% (8 requests) were made to Cdn.optimizely.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Edosite.blob.core.windows.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (11%)

Content Size

12.9 MB

After Optimization

11.4 MB

In fact, the total size of Edo.io main page is 12.9 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. 50% of websites need less resources to load. Images take 12.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 15.7 kB

  • Original 20.1 kB
  • After minification 12.7 kB
  • After compression 4.4 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 7.4 kB, which is 37% 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 15.7 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 936.3 kB

  • Original 12.1 MB
  • After minification 11.2 MB

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. Edo images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 307.0 kB

  • Original 487.0 kB
  • After minification 483.8 kB
  • After compression 180.0 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 307.0 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 202.6 kB

  • Original 244.2 kB
  • After minification 244.1 kB
  • After compression 41.5 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. Edo.io needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (21%)

Requests Now

43

After Optimization

34

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

Accessibility Review

edo.io accessibility score

51

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

edo.io best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

edo.io SEO score

92

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edo.io can be misinterpreted by Google and other search engines. Our service has detected that English 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 Edo.io 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 Edo. 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: