norquest.ca website review

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

About 440 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and fw-cdn.com and others), adding 1.4 MB and 1.6 s of main-thread time.

About 738 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

Google Tag Manager costs a phone 901 ms of main-thread work and 730 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).

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

66 KiB could be saved by minifying JavaScript.

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

Facebook costs a phone 263 ms of main-thread work and 255 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.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

6 KiB could be saved by minifying CSS.

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

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.

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

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

The first text or image appears after 5.7 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.

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 271 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.0 MB in 126 requests on a phone: images 8.4 MB (20), media 2.0 MB (2) and scripts 1.7 MB (43). Under 2 MB keeps phones on slow connections fast.

5 images weigh 7.7 MB together. On a phone connection a single image that size takes seconds.

8 images (8.2 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

4 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example ciil-disability-justice-and-employment.png at 940 px wide, shown at 300 px. Resized copies would save about 47 KiB.

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

5 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

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

Your title is 84 characters, so Google will cut it off around 60: “Edmonton's community college. Find your path. - NorQuest College - Edmonton, Alberta”.

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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 120 pages on norquest.ca and 22 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.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.norquest.ca/programs-and-courses/browse-programs-and-courses, whose canonical is https://www.norquest.ca/programs-courses/browse-programs-and-courses. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.norquest.ca/programs-and-courses/continuing-education and https://www.norquest.ca/programs-and-courses/microcredentials took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97232700&tm=gtm002&Ver=2&mid=738b453c-c69f-447a-af98-038a20f308a2&bo=1&sid=4464fcb0d26d11f1b879331640eb98a6&vid=44652b40d26d11f19b7af1326ddffa46&vids=1&msclkid=N&gtm_t.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“`StorageType.persistent` is deprecated. Please use standardized `navigator.storage` instead.”).

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

4 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”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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 647 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 19 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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