Tools & Wizards About Us
essor.ca screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

essor.ca

Quebec Insurance Brokers − ESSOR Insurance

Page Load Speed

1.8 sec in total

First Response

58 ms

Resources Loaded

1.1 sec

Page Rendered

641 ms

essor.ca screenshot

About Website

Welcome to essor.ca homepage info - get ready to check ESSOR best content for Canada right away, or after learning these important things about essor.ca

It pays to do business with an ESSOR Insurance broker. Discover our vast selection of insurance products and financial services.

Visit essor.ca

Key Findings

We analyzed Essor.ca page load time and found that the first response time was 58 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

essor.ca performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

essor.ca

58 ms

www.essor.ca

154 ms

en

227 ms

cceb5e99c2.js

50 ms

ee87a6a95e.js

77 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 65% of them (30 requests) were addressed to the original Essor.ca, 13% (6 requests) were made to Use.fontawesome.com and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (421 ms) relates to the external source Static.hotjar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 196.1 kB (12%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 141.5 kB

  • Original 166.8 kB
  • After minification 165.8 kB
  • After compression 25.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 141.5 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 54.5 kB

  • Original 1.0 MB
  • After minification 986.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. ESSOR images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 42 B

  • Original 423.5 kB
  • After minification 423.5 kB
  • After compression 423.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 61 B

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 6.9 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. Essor.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (42%)

Requests Now

36

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

essor.ca

essor.ca

58 ms

www.essor.ca

www.essor.ca

154 ms

en

en

227 ms

cceb5e99c2.js

cceb5e99c2.js

50 ms

ee87a6a95e.js

ee87a6a95e.js

77 ms

css_AyfxnyUhSZV8zaq1oRtQcF7RhQnUY0PjPIhAKmsP8BI.css

css_AyfxnyUhSZV8zaq1oRtQcF7RhQnUY0PjPIhAKmsP8BI.css

31 ms

css

css

58 ms

swiper-bundle.min.css

swiper-bundle.min.css

56 ms

css_TBClDz4AQfoT2F-i7VuUprU-_G_fDn6YTwTmRhKDv0g.css

css_TBClDz4AQfoT2F-i7VuUprU-_G_fDn6YTwTmRhKDv0g.css

110 ms

all.js

all.js

92 ms

v4-shims.js

v4-shims.js

66 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

45 ms

js_QZ-iYYIPtEG6nVnU8CebCdblGYFRTFTt1jQ2iManvlY.js

js_QZ-iYYIPtEG6nVnU8CebCdblGYFRTFTt1jQ2iManvlY.js

102 ms

swiper-bundle.min.js

swiper-bundle.min.js

70 ms

js_M97LwGvnoqbNUF1b7eVDx3Cduoabep2ZJ1uCUpzd2X0.js

js_M97LwGvnoqbNUF1b7eVDx3Cduoabep2ZJ1uCUpzd2X0.js

238 ms

gtm.js

gtm.js

88 ms

gtag.js

gtag.js

90 ms

js_WiVPl8Ji7sVzLFgu63RFU-kJ3osvwuD-_1dRFlQkAZI.js

js_WiVPl8Ji7sVzLFgu63RFU-kJ3osvwuD-_1dRFlQkAZI.js

91 ms

cceb5e99c2.css

cceb5e99c2.css

19 ms

font-awesome-css.min.css

font-awesome-css.min.css

13 ms

hotjar-1618082.js

hotjar-1618082.js

421 ms

essor-logo-en.png

essor-logo-en.png

301 ms

logo-brackets.png

logo-brackets.png

303 ms

essor-header-background.png

essor-header-background.png

352 ms

essor-header-sebastien.png

essor-header-sebastien.png

387 ms

int-website-agents-promo-banner2-1080x1080-en.png

int-website-agents-promo-banner2-1080x1080-en.png

352 ms

500x500_petit.png

500x500_petit.png

302 ms

500x500_petit_0.png

500x500_petit_0.png

351 ms

500x500_petit_1.png

500x500_petit_1.png

355 ms

500x500_petit_2.png

500x500_petit_2.png

352 ms

500x500_petit_3.png

500x500_petit_3.png

354 ms

Virage_infolettre_clavardage_640x600_EN.png

Virage_infolettre_clavardage_640x600_EN.png

355 ms

assurance-habitation.jpg

assurance-habitation.jpg

386 ms

Banniere_assurance-auto.jpg

Banniere_assurance-auto.jpg

388 ms

vehicules-loisirs-2-1900x800.jpg

vehicules-loisirs-2-1900x800.jpg

387 ms

assurance-groupe.jpg

assurance-groupe.jpg

417 ms

logo-white-en.png

logo-white-en.png

385 ms

logo-intact-white-en.png

logo-intact-white-en.png

386 ms

icon-intact.png

icon-intact.png

387 ms

logo-intact-footer.png

logo-intact-footer.png

388 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

293 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo.woff

308 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo.woff

341 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo.woff

342 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

57 ms

icomoon.ttf

icomoon.ttf

122 ms

Accessibility Review

essor.ca accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

essor.ca best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

essor.ca SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Essor.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 Essor.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

essor.ca

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