Tools & Wizards About Us
frenchforlife.ca screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

frenchforlife.ca

Page Load Speed

3.5 sec in total

First Response

1.1 sec

Resources Loaded

2.2 sec

Page Rendered

147 ms

frenchforlife.ca screenshot

About Website

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

Visit frenchforlife.ca

Key Findings

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

Performance Metrics

frenchforlife.ca performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

frenchforlife.ca

1127 ms

gutenslider-init.css

84 ms

styles.css

165 ms

style.css

128 ms

style.min.css

126 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 69% of them (37 requests) were addressed to the original Frenchforlife.ca, 28% (15 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Frenchforlife.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 747.6 kB (65%)

Content Size

1.2 MB

After Optimization

404.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frenchforlife.ca main page is 1.2 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. CSS take 512.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 69.5 kB

  • Original 86.2 kB
  • After minification 84.9 kB
  • After compression 16.7 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 69.5 kB or 81% of the original size.

Image Optimization

-16%

Potential reduce by 41.3 kB

  • Original 257.1 kB
  • After minification 215.9 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. Obviously, Frenchforlife needs image optimization as it can save up to 41.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 203.6 kB

  • Original 296.4 kB
  • After minification 295.0 kB
  • After compression 92.7 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 203.6 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 433.2 kB

  • Original 512.2 kB
  • After minification 510.5 kB
  • After compression 79.0 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. Frenchforlife.ca needs all CSS files to be minified and compressed as it can save up to 433.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (78%)

Requests Now

37

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frenchforlife.ca

frenchforlife.ca

1127 ms

gutenslider-init.css

gutenslider-init.css

84 ms

styles.css

styles.css

165 ms

style.css

style.css

128 ms

style.min.css

style.min.css

126 ms

style.min.css

style.min.css

127 ms

style.min.css

style.min.css

129 ms

elementor-icons.min.css

elementor-icons.min.css

166 ms

frontend-lite.min.css

frontend-lite.min.css

290 ms

swiper.min.css

swiper.min.css

168 ms

post-1813.css

post-1813.css

167 ms

all.min.css

all.min.css

249 ms

v4-shims.min.css

v4-shims.min.css

205 ms

global.css

global.css

206 ms

post-10.css

post-10.css

208 ms

font-awesome.min.css

font-awesome.min.css

253 ms

css

css

34 ms

style.min.css

style.min.css

291 ms

customify-pro-c4a474a43c52c47b49c105be2550a56a.css

customify-pro-c4a474a43c52c47b49c105be2550a56a.css

250 ms

css

css

76 ms

language-cookie.js

language-cookie.js

251 ms

jquery.min.js

jquery.min.js

329 ms

jquery-migrate.min.js

jquery-migrate.min.js

300 ms

custom.js

custom.js

299 ms

v4-shims.min.js

v4-shims.min.js

341 ms

theme.min.js

theme.min.js

296 ms

customify-pro-cd464ff7ea71826a1230080a3d3abeee.js

customify-pro-cd464ff7ea71826a1230080a3d3abeee.js

296 ms

webpack.runtime.min.js

webpack.runtime.min.js

322 ms

frontend-modules.min.js

frontend-modules.min.js

355 ms

waypoints.min.js

waypoints.min.js

354 ms

core.min.js

core.min.js

353 ms

frontend.min.js

frontend.min.js

354 ms

cropped-cropped-FFL-Official-logo.png

cropped-cropped-FFL-Official-logo.png

67 ms

Flag_of_Canada_(Pantone).png

Flag_of_Canada_(Pantone).png

67 ms

Welcome-to-our-new-website11.png

Welcome-to-our-new-website11.png

239 ms

Did-you-know-1-300x300.png

Did-you-know-1-300x300.png

68 ms

FFL-Official-logo.png

FFL-Official-logo.png

69 ms

mb-gov.jpg

mb-gov.jpg

68 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

170 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

171 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

203 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

202 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

203 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

202 ms

fa-brands-400.woff

fa-brands-400.woff

171 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LDr0fJg.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LDr0fJg.woff

201 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMDr0fJg.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMDr0fJg.woff

201 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMDr0fJg.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMDr0fJg.woff

203 ms

KFOkCnqEu92Fr1Mu51xIIzQ.woff

KFOkCnqEu92Fr1Mu51xIIzQ.woff

191 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff

KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff

191 ms

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

191 ms

KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff

KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff

191 ms

KFOjCnqEu92Fr1Mu51TzBic6CsI.woff

KFOjCnqEu92Fr1Mu51TzBic6CsI.woff

193 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff

KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff

192 ms

Accessibility Review

frenchforlife.ca accessibility score

91

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.

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

Document doesn't have a <title> element

High

Links do not have a discernible name

Best Practices

frenchforlife.ca best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

frenchforlife.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

Document doesn't have a <title> element

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 Frenchforlife.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 Frenchforlife.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

frenchforlife.ca

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