Website review, no card needed

401dixiekia.com logo

401dixiekia.com website review

Visit site (opens in a new tab)Reviewed 2 November 202661 issues · 108 checks

This review found 61 issues worth fixing on 401dixiekia.com, 27 of them high impact, across 108 checks. The most urgent: use efficient cache lifetimes. 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.3 s1.8 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
316 ms209 msMay 16Oct 31304 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026221 ms
May 23, 2026235 ms
May 30, 2026237 ms
Jun 6, 2026246 ms
Jun 13, 2026252 ms
Jun 20, 2026233 ms
Jun 27, 2026262 ms
Jul 4, 2026263 ms
Jul 11, 2026259 ms
Jul 18, 2026262 ms
Jul 25, 2026236 ms
Aug 1, 2026234 ms
Aug 8, 2026238 ms
Aug 15, 2026254 ms
Aug 22, 2026278 ms
Aug 29, 2026279 ms
Sep 5, 2026277 ms
Sep 12, 2026277 ms
Sep 19, 2026264 ms
Sep 26, 2026271 ms
Oct 3, 2026285 ms
Oct 10, 2026282 ms
Oct 17, 2026303 ms
Oct 24, 2026304 ms
Oct 31, 2026304 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 401dixiekia.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 401dixiekia.com at 1.7 s1.7 s
  2. 401dixiekia.com at 3.4 s3.4 s
  3. 401dixiekia.com at 5.1 s5.1 s
  4. 401dixiekia.com at 6.7 s6.7 s
  5. 401dixiekia.com at 8.4 s8.4 s
  6. 401dixiekia.com at 10.1 s10.1 s
  7. 401dixiekia.com at 11.8 s11.8 s
  8. 401dixiekia.com at 13.5 s13.5 s

Speed

15 to fix6
  • Use efficient cache lifetimes

    10.3 s · 2.6 MB

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

  • Reduce unused JavaScript

    6.4 s · 3.1 MB

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

  • Improve image delivery

    5.5 s · 1.9 MB

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

  • Google Tag Manager adds 2.5 s

    2.5 s

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

  • Render-blocking requests

    2.6 s

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

  • Reduce unused CSS

    2.0 s · 306 KiB

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

  • Main-thread work: 12.0 s

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

  • Mobile performance score: 6

    6/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and sm360.ca and others), adding 9.8 MB and 5.2 s of main-thread time.

  • Google CDN adds 871 ms

    871 ms

    Google CDN costs a phone 871 ms of main-thread work and 1.5 MB 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.

  • sm360.ca adds 500 ms

    500 ms

    sm360.ca costs a phone 500 ms of main-thread work and 5.0 MB 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.

  • 20 long tasks on the main thread

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

  • Facebook adds 406 ms

    406 ms

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

  • impel.io adds 292 ms

    292 ms

    impel.io costs a phone 292 ms of main-thread work and 483 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.

  • 1,613 HTML elements

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

  • Legacy JavaScript

    100 ms · 30 KiB

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

  • Font display

    100 ms

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 29 ms

    29 ms

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

Core Web Vitals

12 to fix33
  • 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 CLS: 0.60

    0.60

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

  • Largest Contentful Paint: 31.6 s

    31.6 s

    Your largest element takes 31.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “EV Rebates Now Available!”.

  • Speed Index: 18.8 s

    18.8 s

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

  • Time to Interactive: 62.3 s

    62.3 s

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

  • Total Blocking Time: 3.4 s

    3.4 s

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

  • Cumulative Layout Shift: 0.656

    0.656

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user INP: 221 ms

    221 ms

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

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

    +33%

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

  • Real-user TTFB: 916 ms

    916 ms

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

  • 11 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

2 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user FCP: 1.5 s

    1.5 s

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

Images and page weight

4 to fix36
  • Page weight: 11.7 MB in 265 requests

    11.7 MB

    Your homepage downloads 11.7 MB in 265 requests on a phone: scripts 6.1 MB (92), images 2.7 MB (68) and fonts 1.5 MB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    -768x420-ev-rebate17714445375001787166388408.png weighs 801 KiB. On a phone connection a single image that size takes seconds.

  • 28 images in older formats

    28 images (2.4 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.

  • An image on the first screen is lazy-loaded

    2026-10-on-kia-header-mobile-768x500-niroev.jpg 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 3.3 g of CO₂ per visit

    3.32 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

18 to fixGoogle 6380
  • Required ARIA attributes must be provided (8 elements)

    Required ARIA attributes must be provided: 8 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 1 button without a name

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

  • Orphan list items

    Some list items are not inside a list.

  • ARIA commands must have an accessible name (1 element)

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

  • 1 text element with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 6 images without alt text

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

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

    All page content should be contained by landmarks: 38 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 (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

  • 6 form fields without a label

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

  • Elements marked as presentational should be consistently ignored (14 elements)

    Elements marked as presentational should be consistently ignored: 14 elements on the page fail this check, rated minor by axe-core.

  • 3 links without text

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

  • Frames without titles

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

5 to fixGoogle 7585
  • No canonical URL

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

  • Structured data has 1 problem

    Structured data found (AutoDealer and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

  • 1 link crawlers can't follow

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

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

  • 151 internal links, 23 external

    The homepage links to 151 pages on 401dixiekia.com and 23 external pages.

5 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “At 401 Dixie Kia, check out our new and used Kia vehicles today. We are your number one dealership for Kia service in M…”.

  • One H1 headline

    Your main headline reads: “401 Dixie Kia”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “401 Dixie Kia | Kia Dealership in Mississauga”.

  • 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.401dixiekia.com/en/sitemap-xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.401dixiekia.com/en/dilawri-certified has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.401dixiekia.com/en/electric-vehicles has 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 68 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 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 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6974
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=25069142&Ver=2&mid=ad13c9db-f675-491a-bd9e-78b6c14497b5&bo=1&sid=1305f630d70311f1894b57997e6b810f&vid=13060350d70311f192c6433ef57bcb74&vids=1&msclkid=N&pi=918639831&lg.

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'split')”.

  • 8 distorted images

    8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No form on the homepage

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

  • About 1,443 words of copy

    The homepage carries about 1,443 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book an Appointment” and “Call to action on image”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Contact us”, “Apply for Financing” and “Lease or Buy”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 7 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.

  • 47 cookies set on arrival

    47

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

  • No consent tool detected

    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.

  • 45 other companies contacted

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

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 401dixiekia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 61 issues on 401dixiekia.com, including 27 speed issues and 5 SEO issues. 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