Website review, no card needed

suzuki.ca logo

suzuki.ca website review

Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 81 checks

This review found 41 issues worth fixing on suzuki.ca, 18 of them high impact, across 81 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.4 s1.2 sApr 25Oct 103.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.6 s
May 2, 20261.5 s
May 9, 20261.4 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jun 13, 20261.9 s
Jun 20, 20262.4 s
Jun 27, 20262.7 s
Jul 4, 20262.9 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.1 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
217 ms139 msApr 25Oct 10208 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026150 ms
May 2, 2026150 ms
May 9, 2026148 ms
May 16, 2026148 ms
May 23, 2026150 ms
May 30, 2026153 ms
Jun 6, 2026154 ms
Jun 13, 2026154 ms
Jun 20, 2026155 ms
Jun 27, 2026156 ms
Jul 4, 2026162 ms
Jul 11, 2026167 ms
Jul 18, 2026173 ms
Jul 25, 2026179 ms
Aug 1, 2026186 ms
Aug 8, 2026189 ms
Aug 15, 2026192 ms
Aug 22, 2026195 ms
Aug 29, 2026196 ms
Sep 5, 2026196 ms
Sep 12, 2026196 ms
Sep 19, 2026197 ms
Sep 26, 2026201 ms
Oct 3, 2026203 ms
Oct 10, 2026208 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of suzuki.ca (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. suzuki.ca at 0.5 s0.5 s
  2. suzuki.ca at 1.0 s1.0 s
  3. suzuki.ca at 1.5 s1.5 s
  4. suzuki.ca at 2.0 s2.0 s
  5. suzuki.ca at 2.5 s2.5 s
  6. suzuki.ca at 3.0 s3.0 s
  7. suzuki.ca at 3.5 s3.5 s
  8. suzuki.ca at 4.0 s4.0 s

Speed

13 to fix29
  • Improve image delivery

    6.2 s · 2.0 MB

    11 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.2 s faster on a phone.

  • Use efficient cache lifetimes

    5.3 s · 1,015 KiB

    19 files are served with short cache lifetimes, so returning visitors download them again (1,015 KiB).

  • Render-blocking requests

    5.1 s

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

  • Reduce unused JavaScript

    3.5 s · 898 KiB

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

  • Reduce unused CSS

    1.5 s · 284 KiB

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

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 4.1 s

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

  • 8 third-party services on the page

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

  • Google Tag Manager adds 844 ms

    844 ms

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

  • Facebook adds 428 ms

    428 ms

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

  • 18 long tasks on the main thread

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

  • 1,658 HTML elements

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

  • Klaviyo adds 124 ms

    124 ms

    Klaviyo costs a phone 124 ms of main-thread work and 322 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.

  • Font display

    200 ms

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

  • Minify JavaScript

    150 ms · 33 KiB

    33 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 32 KiB

    32 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    40 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 68 ms

    68 ms

    Your server sent the HTML in 68 ms, well inside Google's 600 ms guideline.

Core Web Vitals

15 to fix0
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • Largest Contentful Paint: 33.7 s

    33.7 s

    Your largest element takes 33.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SV-7GX With every beat, the experience expands. Introducing…”.

  • Time to Interactive: 40.1 s

    40.1 s

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

  • Speed Index: 12.9 s

    12.9 s

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

  • First Contentful Paint: 5.5 s

    5.5 s

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

  • Total Blocking Time: 823 ms

    823 ms

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Real-user INP: 205 ms

    205 ms

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

  • Real-user CLS: 0.25

    0.25

    For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 37% slower for real visitors

    +37%

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

  • Largest content (LCP) got 97% slower for real visitors

    +97%

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Cumulative Layout Shift: 0.175

    0.175

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

  • 2 images without width and height

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

Images and page weight

3 to fix45
  • Page weight: 22.6 MB in 245 requests

    22.6 MB

    Your homepage downloads 22.6 MB in 245 requests on a phone: media 14.4 MB (3), images 4.7 MB (24) and scripts 2.3 MB (131). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

    7 images (2.0 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.

  • About 6.4 g of CO₂ per visit

    6.42 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 10099
  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9285
  • No H1 headline

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

  • No social preview image

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

  • 5 links with vague text

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

  • 229 internal links, 6 external

    The homepage links to 229 pages on suzuki.ca and 6 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Official Suzuki Canada website. Check out Suzuki motorcycles, ATVs, and outboard motors, browse parts and accessories, …”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Suzuki Canada Home - Suzuki Canada Inc.”.

  • Canonical URL set

    The canonical URL is https://www.suzuki.ca/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.suzuki.ca/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    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.

  • No llms.txt

    There is no https://www.suzuki.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (861 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.suzuki.ca/promotions, https://www.suzuki.ca/clean-ocean-project, https://www.suzuki.ca/recalls, https://www.suzuki.ca/fr and https://www.suzuki.ca/product/2026-v-strom-1050 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.suzuki.ca/store and https://www.suzuki.ca/fr have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    9 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Looks like your website URL has changed. To ensure the proper functioning of your banner, update the re…”.

2 checks passed
  • Tap targets are thumb-sized

    33 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

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

  • No direct contact details

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

  • No risk reducer

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

  • About 854 words of copy

    The homepage carries about 854 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “LEARN MORE”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop Now”, “Learn More” and “Shop ATV Explore Shop ATV”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 16 cookies set on arrival

    16

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

  • 30 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at suzuki.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
React
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on suzuki.ca, including 28 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25