Access we.ca. Read, Watch and Get Inspired with WE Stories

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value26.4 s

0/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value1,710 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

we.ca

51 ms

www.we.ca

33 ms

64 ms

41 ms

mmu5eud.css

84 ms

Our browser made a total of 285 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original We.ca, 85% (243 requests) were made to Staticsb.we.org and 2% (7 requests) were made to We.org. The less responsive or slowest element that took the longest time to load (844 ms) relates to the external source Staticsb.we.org.

Content Size

32.4 MB

After Optimization

32.2 MB

In fact, the total size of We.ca main page is 32.4 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. Only a small number of websites need less resources to load. Images take 32.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 217.9 kB

Original 255.0 kB
After minification 255.0 kB
After compression 37.1 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 217.9 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 848 B

Original 32.1 MB
After minification 32.1 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. We images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 32.2 kB

Original 72.4 kB
After minification 72.4 kB
After compression 40.2 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 32.2 kB or 44% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

Original 5 B

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.

Requests Now

277

After Optimization

250

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

[role]s are not contained by their required parent element

High

ARIA toggle fields do not have accessible names

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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/).

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