Access legrand.ca. Legrand CA | Delivering and Managing Power, Light, and Data

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value19.4 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

legrand.ca

110 ms

legrand.ca

20 ms

www.legrand.ca

422 ms

5ce5a686c250690001276595.js

217 ms

awy7nwh.css

36 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 36% of them (33 requests) were addressed to the original Legrand.ca, 41% (37 requests) were made to Cdn2.webdamdb.com and 11% (10 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Cdn2.webdamdb.com.

Content Size

2.6 MB

After Optimization

2.1 MB

In fact, the total size of Legrand.ca main page is 2.6 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. 55% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 420.5 kB

Original 460.2 kB
After minification 299.9 kB
After compression 39.6 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 160.2 kB, which is 35% 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 420.5 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 9.9 kB

Original 2.1 MB
After minification 2.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. Legrand images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 6.1 kB

Original 41.4 kB
After minification 41.4 kB
After compression 35.3 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 6.1 kB or 15% 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

After Optimization

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legrand. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS 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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a valid value for its [lang] attribute.

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

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

These are opportunities to improve keyboard navigation in your application.

High

Some elements have a [tabindex] value greater than 0

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

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

legrand.ca

Open Graph description is not detected on the main page of Legrand. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

Legrand CA | Delivering and Managing Power, Light, and Data

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

legrand.ca

legrand.ca

www.legrand.ca

5ce5a686c250690001276595.js

awy7nwh.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

legrand.ca

legrand.ca

www.legrand.ca

5ce5a686c250690001276595.js

awy7nwh.css

css

common.css

style.css

ps-utid.js

p.css

DMF36-N82WJ-UH7CT-58HE2-ARD2Z

ca.svg

1280_AJ4Yu2xgZ4D01rT8.png

icons.svg

ma.svg

sa.svg

tn.svg

br.svg

cl.svg

co.svg

mx.svg

pe.svg

us.svg

cn.svg

in.svg

sg.svg

ae.svg

be.svg

fr.svg

de.svg

it.svg

nl.svg

pl.svg

pt.svg

ru.svg

es.svg

au.svg

logo-legrand.svg

legrand-footer-logo.svg

1280_IenFn5PN471.jpg

1280_o0uRXd1w9uc2.jpg

1280_2faHIDXH3y06.jpg

1280_2V2CSVuIMcg2.jpg