Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

edge.org

Edge.org

Page Load Speed

4.9 sec in total

First Response

39 ms

Resources Loaded

2.4 sec

Page Rendered

2.5 sec

edge.org screenshot

About Website

Click here to check amazing Edge content for United States. Otherwise, check out these important facts you probably never knew about edge.org

Visit edge.org

Key Findings

We analyzed Edge.org page load time and found that the first response time was 39 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

edge.org performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value30.1 s

0/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.601

11/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

edge.org

39 ms

system.base.css

20 ms

system.menus.css

21 ms

system.messages.css

21 ms

system.theme.css

23 ms

Our browser made a total of 238 requests to load all elements on the main page. We found that 55% of them (132 requests) were addressed to the original Edge.org, 9% (22 requests) were made to Facebook.com and 8% (19 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (798 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (24%)

Content Size

9.9 MB

After Optimization

7.5 MB

In fact, the total size of Edge.org main page is 9.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 296.8 kB

  • Original 361.1 kB
  • After minification 356.2 kB
  • After compression 64.3 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 296.8 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 874.0 kB

  • Original 7.8 MB
  • After minification 6.9 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. Obviously, Edge needs image optimization as it can save up to 874.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 900.1 kB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 438.6 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 900.1 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 324.0 kB

  • Original 387.4 kB
  • After minification 312.6 kB
  • After compression 63.3 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. Edge.org needs all CSS files to be minified and compressed as it can save up to 324.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 107 (50%)

Requests Now

215

After Optimization

108

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

Accessibility Review

edge.org accessibility score

95

Accessibility Issues

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

Links do not have a discernible name

Best Practices

edge.org best practices score

67

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

SEO Factors

edge.org SEO score

91

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edge.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Edge.org 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 Edge. 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: