Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fccq.ca

Services offerts aux entreprises du Québec | FCCQ

Page Load Speed

2 sec in total

First Response

79 ms

Resources Loaded

1.6 sec

Page Rendered

295 ms

fccq.ca screenshot

About Website

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

Du réseau d'affaire aux programmes d'aides, subventions, activités et ressources, la FCCQ porte les entreprises du Québec vers le succès

Visit fccq.ca

Key Findings

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

Performance Metrics

fccq.ca performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.551

13/100

15%

TTI (Time to Interactive)

Value14.1 s

10/100

10%

Network Requests Diagram

fccq.ca

79 ms

www.fccq.ca

387 ms

style.css

118 ms

swapImage.js

138 ms

mm_css_menu.js

87 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 44% of them (54 requests) were addressed to the original Fccq.ca, 18% (22 requests) were made to Static.xx.fbcdn.net and 6% (7 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (387 ms) belongs to the original domain Fccq.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 153.9 kB (18%)

Content Size

853.6 kB

After Optimization

699.7 kB

In fact, the total size of Fccq.ca main page is 853.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 646.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 41.9 kB

  • Original 51.7 kB
  • After minification 39.4 kB
  • After compression 9.8 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 12.3 kB, which is 24% 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 41.9 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 16.4 kB

  • Original 646.5 kB
  • After minification 630.1 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. FCCQ images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 67.4 kB

  • Original 123.5 kB
  • After minification 106.6 kB
  • After compression 56.0 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 67.4 kB or 55% of the original size.

CSS Optimization

-88%

Potential reduce by 28.1 kB

  • Original 31.9 kB
  • After minification 20.4 kB
  • After compression 3.8 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. Fccq.ca needs all CSS files to be minified and compressed as it can save up to 28.1 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (47%)

Requests Now

116

After Optimization

62

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

Accessibility Review

fccq.ca accessibility score

73

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

fccq.ca best practices score

58

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fccq.ca SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fccq.ca can be misinterpreted by Google and other search engines. Our service has detected that French 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 Fccq.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 description is not detected on the main page of FCCQ. 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: