Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 98% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    34% of websites

  • 100

    SEO

    Google-friendlier than
    96% of websites

edge.ca

102.1 the Edge

Page Load Speed

6 sec in total

First Response

1.1 sec

Resources Loaded

4.5 sec

Page Rendered

357 ms

edge.ca screenshot

About Website

Visit edge.ca now to see the best up-to-date Edge content for Canada and also check out these interesting facts you probably never knew about edge.ca

102.1 the Edge

Visit edge.ca

Key Findings

We analyzed Edge.ca page load time and found that the first response time was 1.1 sec 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.ca performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value1.349

0/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

www.edge.ca

1140 ms

bootstrap.css

22 ms

js_composer_front.css

24 ms

featureRotator.css

29 ms

blogNews.css

26 ms

Our browser made a total of 230 requests to load all elements on the main page. We found that 9% of them (21 requests) were addressed to the original Edge.ca, 17% (39 requests) were made to D2x3wmakafwqf5.cloudfront.net and 14% (33 requests) were made to D3of83nms6dskl.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Edge.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.1 MB (40%)

Content Size

7.7 MB

After Optimization

4.6 MB

In fact, the total size of Edge.ca main page is 7.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. 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 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 307.9 kB

  • Original 417.3 kB
  • After minification 412.6 kB
  • After compression 109.5 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 307.9 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 172.2 kB

  • Original 3.7 MB
  • After minification 3.6 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. Edge images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 1.9 MB

  • Original 2.7 MB
  • After minification 2.4 MB
  • After compression 786.4 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 1.9 MB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 712.1 kB

  • Original 814.7 kB
  • After minification 628.3 kB
  • After compression 102.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. Edge.ca needs all CSS files to be minified and compressed as it can save up to 712.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 123 (59%)

Requests Now

210

After Optimization

87

The browser has sent 210 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 84 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

edge.ca accessibility score

100

Accessibility Issues

Best Practices

edge.ca 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

edge.ca SEO score

100

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

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 Edge.ca 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 Edge.ca 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 data is detected on the main page of Edge. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: