Website review, no card needed

hondacanada.ca logo

hondacanada.ca website review

Visit site (opens in a new tab)Reviewed 30 October 202642 issues · 84 checks

This review found 42 issues worth fixing on hondacanada.ca, 14 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
2.7 s1.9 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.3 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
117 ms80 msMay 9Oct 2490 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202695 ms
May 16, 202692 ms
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202686 ms
Jun 13, 202684 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202688 ms
Jul 11, 202689 ms
Jul 18, 202690 ms
Jul 25, 202693 ms
Aug 1, 202688 ms
Aug 8, 202689 ms
Aug 15, 202690 ms
Aug 22, 202691 ms
Aug 29, 202688 ms
Sep 5, 202691 ms
Sep 12, 202696 ms
Sep 19, 2026102 ms
Sep 26, 2026110 ms
Oct 3, 2026113 ms
Oct 10, 2026107 ms
Oct 17, 202698 ms
Oct 24, 202690 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 hondacanada.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hondacanada.ca at 0.4 s0.4 s
  2. hondacanada.ca at 0.8 s0.8 s
  3. hondacanada.ca at 1.1 s1.1 s
  4. hondacanada.ca at 1.5 s1.5 s
  5. hondacanada.ca at 1.9 s1.9 s
  6. hondacanada.ca at 2.3 s2.3 s
  7. hondacanada.ca at 2.6 s2.6 s
  8. hondacanada.ca at 3.0 s3.0 s

Speed

6 to fix55
  • Reduce unused JavaScript

    4.5 s · 1.1 MB

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

  • Use efficient cache lifetimes

    2.8 s · 557 KiB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    900 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.

  • 8 long tasks on the main thread

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

  • Google Maps adds 105 ms

    105 ms

    Google Maps costs a phone 105 ms of main-thread work and 328 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Maps, Google Tag Manager and Optanon and others), adding 758 KiB and 304 ms of main-thread time.

  • Improve image delivery

    147 KiB

    5 images could be 147 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    61 KiB

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

  • Reduce unused CSS

    21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page.

  • 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.

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.

  • Server response: 33 ms

    33 ms

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

Core Web Vitals

9 to fix100
  • 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.

  • Largest Contentful Paint: 13.8 s

    13.8 s

    Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Smiling Honda employees inspect a vehicle as it rolls off t…”.

  • Time to Interactive: 14.6 s

    14.6 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 958 ms

    958 ms

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

  • Total Blocking Time: 508 ms

    508 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 87 ms

    87 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 2.5 MB in 59 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 59 requests on a phone: scripts 1.8 MB (31), images 488 KiB (12) and fonts 71 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Canada_612x350_Desktop_Homepage2colLandscapeCard.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.7 g of CO₂ per visit

    0.70 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8291
  • Invalid ARIA attributes

    3 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (15 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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 links without text

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

  • Headings skip levels

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

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

9 to fixGoogle 3158
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • No structured data

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

  • No social preview image

    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

    No XML sitemap at https://www.hondacanada.ca/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link crawlers can't follow

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

  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 26 internal links, 41 external

    The homepage links to 26 pages on hondacanada.ca and 41 external pages.

3 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Explore Honda Canada's vehicles, innovations in mobility, and commitment to sustainability. Discover our latest models …”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Honda Canada: Innovation, Performance, and Sustainability”.

  • Canonical URL set

    The canonical URL is https://www.hondacanada.ca/en/.

AI search readiness

2 to fix53
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No Organization structured data

    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.

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.hondacanada.ca/en/honda-green-dealers and https://www.hondacanada.ca/en/acura-green-dealers have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.hondacanada.ca/en/honda-green-dealers, https://www.hondacanada.ca/en/manufacturing, https://www.hondacanada.ca/en/community, https://www.hondacanada.ca/en/safety and https://www.hondacanada.ca/en/history have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • 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 8 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 2 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.honda.ca/context' from origin 'https://www.hondacanada.ca' has been blocked by…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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 form on the homepage

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

  • 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 352 words of copy

    The homepage carries about 352 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “LEARN MORE” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    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.

  • 11 cookies set on arrival

    11

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

  • 12 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 hondacanada.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Akamai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on hondacanada.ca, including 15 speed issues, 9 SEO issues and 3 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