sja.ca website review

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

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

Google Tag Manager costs a phone 2.3 s of main-thread work and 2.1 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.

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

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

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

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

7 images could be 7.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Facebook and momentjs.com and others), adding 3.1 MB and 3.5 s of main-thread time.

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

627 KiB could be saved by minifying CSS.

50 KiB could be saved by minifying JavaScript.

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

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

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

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 22.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our most popular courses are on sale! Save $10 on Emergency…”.

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

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

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

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

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

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

3 images 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' largest content (lcp) went from 1.8 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.4 MB in 195 requests on a phone: images 7.9 MB (49), scripts 3.4 MB (73) and stylesheets 1,004 KiB (8). Under 2 MB keeps phones on slow connections fast.

3 images weigh 7.5 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example Standard_intermediate First Aid_St John Ambulance_0.png at 1,920 px wide, shown at 338 px. Resized copies would save about 5.4 MB.

3 images (7.5 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.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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.

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

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

Your meta description is 247 characters; Google truncates after about 160, so the end of your pitch is cut.

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://sja.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 211 pages on sja.ca and 12 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://sja.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.

Your homepage links to https://sja.ca/en/sja_geolocation/NTL, https://sja.ca/en/sja_geolocation/AB, https://sja.ca/en/sja_geolocation/BC, https://sja.ca/en/sja_geolocation/MB, https://sja.ca/en/sja_geolocation/NB and https://sja.ca/en/sja_geolocation/NL and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.

We fetched 15 pages linked from your homepage (of 78 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=121002781&tm=gtm002&Ver=2&mid=3239cd5b-5414-4e4b-ae12-0571bd1d1292&bo=1&sid=ec90fe30d2a911f1a7faab039a1b4c17&vid=ec90e690d2a911f1a7dee7f93918acc7&vids=1&msclkid=N&gtm_.

3 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 ()”.

Requests the geolocation permission on page load.

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

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.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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