herzing.ca website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.

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

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

hcaptcha.com costs a phone 1.9 s of main-thread work and 2.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (hcaptcha.com, Facebook and TikTok and others), adding 3.9 MB and 2.5 s of main-thread time.

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

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

Polyfills for old browsers add 125 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

65 KiB could be saved by minifying JavaScript.

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

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

LiveChat costs a phone 70 ms of main-thread work and 646 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.

popupsmart.com costs a phone 30 ms of main-thread work and 551 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.

9 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

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

Real visitors wait 265 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 146 ms to 274 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 8.9 MB in 241 requests on a phone: scripts 3.7 MB (78), images 3.6 MB (85) and HTML 859 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example herzing-winnipeg-2025-v2-crop.jpg at 1,103 px wide, shown at 351 px. Resized copies would save about 13 KiB.

1 image (141 KiB) is 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.

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

6 dropdowns have no label.

1 button has no accessible name, so screen readers announce just “button”.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

7 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

The homepage links to 198 pages on herzing.ca and 32 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/programs/construction-management-technician and /programs/damage-insurance have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 88 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=97162022&tm=gtm002&Ver=2&mid=7ee79244-5ba3-4987-a394-b888b70d70b3&bo=1&sid=72639900d3e511f197c671a65add4c55&vid=7263a3e0d3e511f19a8cfd2790bc00f2&vids=1&msclkid=N&pi=91.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

Large scripts ship without source maps.

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

Your longest form asks for 13 fields (12 required). Every extra field lowers completion.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 1,311 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Hotjar, Meta Pixel and Microsoft Ads and 2 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 30 cookies, 4 of them by other companies (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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.