Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wqcc.wqsb.qc.ca

Account Suspended

Page Load Speed

464 ms in total

First Response

70 ms

Resources Loaded

288 ms

Page Rendered

106 ms

wqcc.wqsb.qc.ca screenshot

About Website

Visit wqcc.wqsb.qc.ca now to see the best up-to-date Wqcc Wqsb content for Canada and also check out these interesting facts you probably never knew about wqcc.wqsb.qc.ca

Visit wqcc.wqsb.qc.ca

Key Findings

We analyzed Wqcc.wqsb.qc.ca page load time and found that the first response time was 70 ms and then it took 394 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

wqcc.wqsb.qc.ca performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value21.4 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

wqcc.wqsb.qc.ca

70 ms

suspendedpage.cgi

37 ms

all.css

78 ms

fa-solid-900.woff

52 ms

fa-regular-400.woff

76 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 40% of them (2 requests) were addressed to the original Wqcc.wqsb.qc.ca, 60% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (78 ms) relates to the external source Use.fontawesome.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.5 kB (23%)

Content Size

15.1 kB

After Optimization

11.6 kB

In fact, the total size of Wqcc.wqsb.qc.ca main page is 15.1 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. Only 10% of websites need less resources to load. HTML takes 7.6 kB which makes up the majority of the site volume.

HTML Optimization

-46%

Potential reduce by 3.5 kB

  • Original 7.6 kB
  • After minification 7.3 kB
  • After compression 4.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 3.5 kB or 46% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 7.5 kB
  • After minification 7.5 kB
  • After compression 7.5 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. Wqcc.wqsb.qc.ca has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wqcc Wqsb. According to our analytics all requests are already optimized.

Accessibility Review

wqcc.wqsb.qc.ca accessibility score

74

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

wqcc.wqsb.qc.ca best practices score

75

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

SEO Factors

wqcc.wqsb.qc.ca SEO score

93

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

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

    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 Wqcc.wqsb.qc.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 Wqcc.wqsb.qc.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 Wqcc Wqsb. 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: