uqo.ca website review

About 759 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

17 files are served with short cache lifetimes, so returning visitors download them again (277 KiB).

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

Your mobile performance score is 47 (desktop: 80). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Didomi and Facebook and others), adding 2.1 MB and 1.1 s of main-thread time.

Google Tag Manager costs a phone 620 ms of main-thread work and 1,003 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 96 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

6 images could be 178 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

A phone's processor spends 2.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,938 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

userway.org costs a phone 54 ms of main-thread work and 583 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

14 long tasks block the main thread while loading, the longest for 155 ms. During a long task the page ignores taps.

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

Desktop scores 80 but mobile only 47. A gap that wide usually means heavy scripts and images that hit phones hardest.

6 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 21.7 s. Good is under 3.8 s.

The first text or image appears after 5.0 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.

Real visitors wait 879 ms for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 434 ms in total while the page loads. Good is under 200 ms.

1 image have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 119 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 14.5 MB in 95 requests on a phone: media 11.3 MB (1), scripts 1.7 MB (38) and images 693 KiB (20). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 4.12 g of CO₂e: 494.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 links inside paragraphs rely on colour alone to stand out.

1 element hidden from screen readers can still receive keyboard focus.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

Elements use prohibited ARIA attributes (1 element).

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements with visible text labels do not have matching accessible names. (6 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://uqo.ca/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 384 pages on uqo.ca and 59 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://uqo.ca/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://uqo.ca/samllogin/Microsoft_Entra_ID and https://uqo.ca/user are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://uqo.ca/samllogin/Microsoft_Entra_ID and https://uqo.ca/user all use the title “Sign in to your account”. Search engines can't tell which page to show for a search, so each competes with the others.

https://uqo.ca/emplois, https://uqo.ca/english, https://uqo.ca/samllogin/Microsoft_Entra_ID, https://uqo.ca/joindre, https://uqo.ca/user and https://uqo.ca/etudiants/admission/etapes and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://uqo.ca/english, https://uqo.ca/samllogin/Microsoft_Entra_ID and https://uqo.ca/user have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 123 found) and read each the way a search engine does.

9 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 613 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager and LinkedIn Insight (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.