Website review, no card needed
hamiltonmotorcompany.com website review
Visit site (opens in a new tab)Reviewed 19 November 202639 issues · 84 checks
This review found 39 issues worth fixing on hamiltonmotorcompany.com, 13 of them high impact, across 84 checks. The most urgent: page weight: 26.3 MB in 376 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84B- #22,110 of 124,051 reviewed websitesbeats 77%
- #14,241 of 69,761 online storesbeats 74%
- #13,810 of 63,450 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.0 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 90 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 96 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 102 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 103 ms |
| Jul 25, 2026 | 100 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 97 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 100 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 106 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 113 ms |
| Oct 31, 2026 | 116 ms |
| Nov 7, 2026 | 116 ms |
| Nov 14, 2026 | 113 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
How it loaded on a phone
0.5 s
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.6 s
4.1 s
Speed
4,843 HTML elements
The page has 4,843 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
1.0 MB23 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Improve image delivery
679 KiB14 images could be 679 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Klaviyo and Bing Ads and others), adding 1.9 MB and 247 ms of main-thread time.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
YouTube adds 4 ms
4 msYouTube costs a phone 4 ms of main-thread work and 1.2 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.
Reduce unused CSS
68 KiBAbout 68 KiB of CSS is downloaded but never applied on this page.
Reduce unused JavaScript
62 KiBAbout 62 KiB of JavaScript is downloaded but never used on this page.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 4.0 s
4.0 sThe first text or image appears after 4.0 s on a phone. Good is under 1.8 s.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 7.9 s
7.9 sThe page becomes fully interactive after 7.9 s. Good is under 3.8 s.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 90 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 4.0 s
4.0 sYour largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Make Every Drive Feel New.”. Most of its time is element render delay (2.5 s).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 91 ms
91 msReal visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 532 ms
532 msReal visitors wait 532 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 1 ms
1 msScripts block the page for only 1 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 26.3 MB in 376 requests
26.3 MBYour homepage downloads 26.3 MB in 376 requests on a phone: media 21.4 MB (5), images 2.3 MB (24) and other files 1.6 MB (256). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
DSC07421.jpg weighs 715 KiB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
687 KiB2 images are downloaded at several times the size a phone draws them, for example DSC07421.jpg at 4,240 px wide, shown at 390 px. Resized copies would save about 687 KiB.
1 image below the first screen load straight away
1 image further down the page (715 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 7.4 g of CO₂ per visit
7.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.44 g of CO₂e: 893.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Hidden but focusable
32 elements hidden from screen readers can still receive keyboard focus.
ARIA progressbar nodes must have an accessible name (1 element)
ARIA progressbar nodes 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.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate 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.
2 checks passed
Every image has alt text
All 162 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (22 characters)
Your title is only 22 characters: “Hamilton Motor Company”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (181 characters)
Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
239 internal links, 11 external
The homepage links to 239 pages on hamiltonmotorcompany.com and 11 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Hamilton Motor Company”.
Canonical URL set
The canonical URL is https://www.hamiltonmotorcompany.com/.
Structured data in place
Structured data found: BreadcrumbList.
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.hamiltonmotorcompany.com/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (4,671 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.hamiltonmotorcompany.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.hamiltonmotorcompany.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.hamiltonmotorcompany.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
11 pages without a meta description
https://www.hamiltonmotorcompany.com/customer_authentication/redirect, https://www.hamiltonmotorcompany.com/pages/find-an-installer, https://www.hamiltonmotorcompany.com/pages/connect, https://www.hamiltonmotorcompany.com/pages/our-hope, https://www.hamiltonmotorcompany.com/collections/toyota-apple-carplay-kits and https://www.hamiltonmotorcompany.com/collections/lexus-apple-carplay-conversion-kits and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.hamiltonmotorcompany.com/collections/honda-kits-for-carplay%C2%AE-and-android-auto%E2%84%A2, whose canonical is https://www.hamiltonmotorcompany.com/collections/honda-kits-for-carplay%c2%ae-and-android-auto%e2%84%a2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.hamiltonmotorcompany.com/customer_authentication/redirect and https://www.hamiltonmotorcompany.com/pages/about-us 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 94 found) and read each the way a search engine does.
2 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Titles are unique
Every page we checked has its own title.
Best practices
3 broken images
3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187100902&tm=shpfy_ui&Ver=2&mid=b70ff273-4ee5-4e79-90dd-0e7741a8f07a&bo=2&sid=3393f870e46b11f1a9200b232e9ea701&vid=33942050e46b11f196c24b60de00aaa0&vids=1&msclkid=N&pi.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
101 of 105 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
Thin social proof
Social proof on the homepage: 148 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 18-field form
Your longest form asks for 18 fields (9 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 2,267 words of copy
The homepage carries about 2,267 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 Kits for CarPlay”.
10 calls to action
The homepage has 10 calls to action, for example “Shop by make”, “Shop Our Products” and “Shop Kits for CarPlay”.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads 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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 1 of them by other companies (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.
28 other companies contacted
Loading the homepage contacts 28 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 hamiltonmotorcompany.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Feedapis For Bing Shopping Ms · Klaviyo Email Marketing Sms · Judge Me Reviews · Infinite Microsoft Ads Uet Tag · cloudfront.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on hamiltonmotorcompany.com, including 13 speed issues, 3 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.