6.9 sec in total
401 ms
3.8 sec
2.7 sec
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.ioWe 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.
edo.io performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value4.2 s
44/100
25%
Value3.0 s
94/100
10%
Value230 ms
87/100
30%
Value0.003
100/100
15%
Value4.5 s
83/100
10%
401 ms
54 ms
27 ms
39 ms
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 size can be reduced by 1.5 MB (11%)
12.9 MB
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.
Potential reduce by 15.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. 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.
Potential reduce by 936.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. Edo images are well optimized though.
Potential reduce by 307.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.
Potential reduce by 202.6 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.
Number of requests can be reduced by 9 (21%)
43
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.
edo.io
401 ms
www.edo.io
54 ms
style.css
27 ms
css
39 ms
jquery-latest.min.js
5 ms
jquery.scrollTo.min.js
29 ms
jquery.cookie.min.js
57 ms
3417200797.js
289 ms
scripts.js
27 ms
analytics.js
53 ms
mixpanel-2-latest.min.js
57 ms
home_visual.jpg
81 ms
en-play-badge.png
94 ms
efceed6a735b4d76b1bce52135374c5d.png
402 ms
IN45RwLPEn8
148 ms
96d25397b1214dbd83a60ec5f5619493.png
224 ms
383d0278fe5841c0b5f5fc561a176244.png
165 ms
3fb0bfbb074747898a18730e2c0bbec2.png
299 ms
d7c54f3c776343128acaaa7131273650.png
165 ms
cf930ba6739f446aaaf084aa90972b25.png
299 ms
b2d5bdb7613e421c9909ee447782a64e.png
301 ms
app-store-badge.png
31 ms
logo_write.png
67 ms
it.png
53 ms
logo_blu.png
37 ms
crowd_love.jpg
35 ms
timeline_new.png
52 ms
spaces_new.png
39 ms
notes_new.png
41 ms
iphone_banner.png
45 ms
apple_logo.png
46 ms
googledocs.png
48 ms
drive.png
51 ms
search.png
54 ms
security.png
55 ms
recap_banner.png
61 ms
facebook.png
63 ms
twitter.png
58 ms
badge_blue.png
28 ms
collect
27 ms
9 ms
home_visual.jpg
1281 ms
app-store-badge.png
388 ms
crowd_love.jpg
1539 ms
logo_blu.png
962 ms
spaces_new.png
2511 ms
notes_new.png
1744 ms
iphone_banner.png
2223 ms
apple_logo.png
1118 ms
googledocs.png
1287 ms
drive.png
1363 ms
search.png
1468 ms
security.png
1465 ms
twitter.png
1587 ms
recap_banner.png
2875 ms
facebook.png
1650 ms
logo_write.png
1683 ms
www-embed-player-vflfNyN_r.css
93 ms
www-embed-player.js
127 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
39 ms
ad_status.js
33 ms
edo.io accessibility score
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
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
edo.io 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
General
Impact
Issue
Detected JavaScript libraries
edo.io SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
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.
edo.io
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: