Website review, no card needed
hautopart.com website review
Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 86 checks
This review found 37 issues worth fixing on hautopart.com, 12 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
81B- #41,714 of 125,141 reviewed websitesbeats 61%
- #27,559 of 70,110 online storesbeats 54%
- #26,544 of 63,714 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 95 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 100 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 103 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 102 ms |
| Aug 29, 2026 | 101 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 103 ms |
| Oct 24, 2026 | 103 ms |
| Oct 31, 2026 | 103 ms |
| Nov 7, 2026 | 103 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.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.1 s
Speed
Improve image delivery
5.3 s · 2.2 MB11 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.3 s faster on a phone.
5,356 HTML elements
The page has 5,356 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and useamp.com and others), adding 2.1 MB and 642 ms of main-thread time.
Reduce unused JavaScript
703 KiBAbout 703 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
500 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Google Tag Manager adds 377 ms
377 msGoogle Tag Manager costs a phone 377 ms of main-thread work and 849 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.
Use efficient cache lifetimes
396 KiB14 files are served with short cache lifetimes, so returning visitors download them again (396 KiB).
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 99 ms
99 msShopify costs a phone 99 ms of main-thread work and 685 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 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.
Duplicated JavaScript
41 KiB41 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
29 KiBAbout 29 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.
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: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 24.9 s
24.9 sThe page becomes fully interactive after 24.9 s. Good is under 3.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 217 ms
217 msScripts block taps and scrolling for 217 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 95 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 102 ms
102 msReal visitors wait 102 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 717 ms
717 msReal visitors wait 717 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.048
0.048The layout barely moves while loading (CLS 0.048, good is under 0.1).
Images and page weight
1 image over 500 KB
8nm94-l3q95.gif weighs 11.1 MB. On a phone connection a single image that size takes seconds.
Page weight: 6.7 MB in 326 requests
6.7 MBYour homepage downloads 6.7 MB in 326 requests on a phone: images 3.2 MB (30), scripts 1.8 MB (110) and other files 1.0 MB (121). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (11.1 MB) is 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 1.9 g of CO₂ per visit
1.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.91 g of CO₂e: 229.2 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
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (1 element).
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 84 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 5 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“” and “Our Offline Store”). One clear main headline is easier for people and search engines.
Meta description is long (287 characters)
Your meta description is 287 characters; Google truncates after about 160, so the end of your pitch is cut.
637 internal links, 19 external
The homepage links to 637 pages on hautopart.com and 19 external pages.
4 checks passed
Title: 43 characters
Your title is a healthy 43 characters: “Smart Car Upgrades & Accessories – Hansshow”.
Canonical URL set
The canonical URL is https://www.hansshow.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://www.hansshow.com/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your 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.
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.
2 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (4,226 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.hansshow.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without a meta description
https://www.hansshow.com/pages/black-friday, https://www.hansshow.com/collections/tesla-accessories, https://www.hansshow.com/collections/model-y-juniper-lighting-upgrade, https://www.hansshow.com/collections/tesla-model-y-juniper-sunshade, https://www.hansshow.com/collections/model-y-juniper-yoke-steering-wheel and https://www.hansshow.com/collections/model-y-juniper-gear-shift-control-stalk and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.hansshow.com/products/model-y-juniper-dashboard-display-f9-9-inches-touch-screen-instrument-cluster-display, whose canonical is https://www.hansshow.com/products/model-y-juniper-heads-up-display-dashboard-display-f9-9-inches-touch-screen-instrument-cluster. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.hansshow.com/pages/black-friday and https://www.hansshow.com/products/model-y-juniper-dashboard-display-f9-9-inches-touch-screen-instrument-cluster-display have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.hansshow.com/products/model-y-juniper-dashboard-display-f9-9-inches-touch-screen-instrument-cluster-display, https://www.hansshow.com/collections/model-y-juniper-illuminated-door-sill and https://www.hansshow.com/collections/model-y-juniper-rearview-mirror-dashcam took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 194 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
19 small tap targets
19 of 65 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
About 2,472 words of copy
The homepage carries about 2,472 words of visible text.
6 checks passed
16 calls to action
The homepage has 16 calls to action, for example “Shop by Category”, “Shop by Vehicle” and “Order Track”.
7 short forms
7 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 41 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 2 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.
31 other companies contacted
Loading the homepage contacts 31 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 hautopart.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on hautopart.com, including 14 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.