Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

oiiq.org

Maintenance sur le site de l'OIIQ

Page Load Speed

3.8 sec in total

First Response

49 ms

Resources Loaded

3.3 sec

Page Rendered

374 ms

oiiq.org screenshot

About Website

Click here to check amazing OIIQ content for Canada. Otherwise, check out these important facts you probably never knew about oiiq.org

L’OIIQ est le plus grand ordre professionnel dans le domaine de la santé au Québec. Il compte quelque 80 000 membres. Sa mission est d’assurer la protection du public et le développement de la profess...

Visit oiiq.org

Key Findings

We analyzed Oiiq.org page load time and found that the first response time was 49 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

oiiq.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.123

83/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

oiiq.org

49 ms

www.oiiq.org

235 ms

otSDKStub.js

40 ms

lodash.js

74 ms

util.js

44 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 92% of them (78 requests) were addressed to the original Oiiq.org, 4% (3 requests) were made to Cdn.cookielaw.org and 1% (1 request) were made to Googletagservices.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Oiiq.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.6 kB (8%)

Content Size

2.9 MB

After Optimization

2.7 MB

In fact, the total size of Oiiq.org main page is 2.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. 55% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 124.9 kB

  • Original 149.9 kB
  • After minification 147.9 kB
  • After compression 25.0 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 124.9 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 47.1 kB

  • Original 2.4 MB
  • After minification 2.4 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. OIIQ images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 61.6 kB

  • Original 352.7 kB
  • After minification 352.6 kB
  • After compression 291.1 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 61.6 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (67%)

Requests Now

79

After Optimization

26

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

Accessibility Review

oiiq.org accessibility score

60

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.

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Some elements have a [tabindex] value greater than 0

Best Practices

oiiq.org 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

oiiq.org SEO score

83

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

High

Tap targets are not sized appropriately

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 Oiiq.org 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 Oiiq.org 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 data is detected on the main page of OIIQ. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: