Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

w3.uqo.ca

Service des technologies de l'information | UQO | Université du Québec en Outaouais

Page Load Speed

2 sec in total

First Response

73 ms

Resources Loaded

1.6 sec

Page Rendered

311 ms

w3.uqo.ca screenshot

About Website

Visit w3.uqo.ca now to see the best up-to-date W 3 UQO content for Canada and also check out these interesting facts you probably never knew about w3.uqo.ca

Pour toute demande de soutien informatique vous pouvez composer le poste 2211 ou le numéro de téléphone 819-595-2211 ou créer une requête via le système de requêtes informatiques de l’UQO disponible à...

Visit w3.uqo.ca

Key Findings

We analyzed W3.uqo.ca page load time and found that the first response time was 73 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

w3.uqo.ca performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value1,700 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

w3.uqo.ca

73 ms

sti

67 ms

sti

1149 ms

ajax-progress.module.css

63 ms

align.module.css

61 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original W3.uqo.ca, 66% (54 requests) were made to Uqo.ca and 29% (24 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Uqo.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 681.9 kB (37%)

Content Size

1.9 MB

After Optimization

1.2 MB

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

HTML Optimization

-92%

Potential reduce by 187.6 kB

  • Original 204.8 kB
  • After minification 85.5 kB
  • After compression 17.2 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 119.3 kB, which is 58% 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 187.6 kB or 92% of the original size.

Image Optimization

-2%

Potential reduce by 18.9 kB

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

JavaScript Optimization

-4%

Potential reduce by 4.0 kB

  • Original 112.8 kB
  • After minification 112.8 kB
  • After compression 108.8 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

-93%

Potential reduce by 471.5 kB

  • Original 507.3 kB
  • After minification 227.7 kB
  • After compression 35.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. W3.uqo.ca needs all CSS files to be minified and compressed as it can save up to 471.5 kB or 93% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (69%)

Requests Now

55

After Optimization

17

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

Accessibility Review

w3.uqo.ca accessibility score

80

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

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

High

ARIA IDs are not unique

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

Links do not have a discernible name

Tables and lists

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

Impact

Issue

High

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

Best Practices

w3.uqo.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

w3.uqo.ca SEO score

79

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

High

robots.txt is not valid

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

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise W3.uqo.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that W3.uqo.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 W 3 UQO. 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: