mazda.ca website review

98 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

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

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

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

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

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

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

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

6 third-party services load with your homepage (Optanon, azure.com and Google Tag Manager and others), adding 589 KiB and 321 ms of main-thread time.

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

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

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 16.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LEASE FROM 0.99% 0% FOR 36 MONTHS‡​‡​ INCLUDES A 1.5% LOYAL…”.

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

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

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

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

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

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

The layout shifts by 0.118 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 2.8 MB in 127 requests on a phone: images 1.2 MB (61), scripts 1.2 MB (23) and stylesheets 253 KiB (17). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 0_c23_3buildandprice_desktop.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 103 KiB.

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

3 images (213 KiB) 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 0.81 g of CO₂e: 96.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

7 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

5 tap targets are too small or too close together to hit reliably with a finger.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

11 links have no real href, so search engines can't follow them.

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

The homepage links to 143 pages on mazda.ca and 21 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://www.mazda.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://www.mazda.ca/link/f0d70ee0ddb44c9ea06e11744c929b6e.aspx has no <title>, so Google invents the link text in results.

/ and https://www.mazda.ca/en all use the title “Mazda Canada: SUVs, EVs, Mid-Size Cars, Compacts and Crossovers”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mazda.ca/link/f0d70ee0ddb44c9ea06e11744c929b6e.aspx has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mazda.ca/link/f0d70ee0ddb44c9ea06e11744c929b6e.aspx, https://www.mazda.ca/en, https://www.mazda.ca/fr, https://www.mazda.ca/en/vehicles/cx-5, https://www.mazda.ca/en/vehicles/cx-30 and https://www.mazda.ca/en/vehicles/cx-70-inline6turbo and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

62 of 82 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 (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'querySelector') Object.animateFixed (https://www.mazda.ca/globalassets/static/…”.

Large scripts ship without source maps.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 2,482 words of visible text.

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

Opening the homepage sets 9 cookies (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.