Website review, no card needed
arnoldclarkautoparts.com website review
Visit site (opens in a new tab)Reviewed 8 November 202637 issues · 82 checks
This review found 37 issues worth fixing on arnoldclarkautoparts.com, 12 of them high impact, across 82 checks. The most urgent: fails Core Web Vitals for real visitors. 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
74C- #88,060 of 126,287 reviewed websitesbeats 26%
- #54,937 of 70,419 online storesbeats 18%
- #51,550 of 63,932 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 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.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 369 ms |
| May 23, 2026 | 374 ms |
| May 30, 2026 | 309 ms |
| Jun 6, 2026 | 228 ms |
| Jun 13, 2026 | 163 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 126 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 131 ms |
| Aug 8, 2026 | 135 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 135 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 133 ms |
| Oct 17, 2026 | 130 ms |
| Oct 24, 2026 | 131 ms |
| Oct 31, 2026 | 133 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.9 s
1.8 s
2.6 s
3.5 s
4.4 s
5.3 s
6.2 s
7.0 s
Speed
4,899 HTML elements
The page has 4,899 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused JavaScript
150 ms · 744 KiBAbout 744 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
250 ms · 594 KiB20 files are served with short cache lifetimes, so returning visitors download them again (594 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Trust Pilot and others), adding 1.8 MB and 635 ms of main-thread time.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 206 ms
206 msGoogle Tag Manager costs a phone 206 ms of main-thread work and 313 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.
Shopify adds 97 ms
97 msShopify costs a phone 97 ms of main-thread work and 691 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.
partly.com adds 80 ms
80 mspartly.com costs a phone 80 ms of main-thread work and 362 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.
Improve image delivery
232 KiB9 images could be 232 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
150 ms · 12 KiB12 KiB could be saved by minifying JavaScript.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 154 ms. During a long task the page ignores taps.
Reduce unused CSS
77 KiBAbout 77 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Duplicated JavaScript
17 KiB17 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
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
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.28
0.28For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.
Time to Interactive: 16.2 s
16.2 sThe page becomes fully interactive after 16.2 s. Good is under 3.8 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Stay winter-ready with our Winter Essentials range — keep y…”. Most of its time is element render delay (2.5 s).
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 244 ms
244 msScripts block taps and scrolling for 244 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 171 ms
171 msReal visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 387 ms
387 msReal visitors wait 387 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 64% faster for real visitors
-64%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 369 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 304 requests
3.8 MBYour homepage downloads 3.8 MB in 304 requests on a phone: scripts 1.4 MB (72), other files 1.2 MB (178) and fonts 469 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 130.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Documents must have <title> element to aid in navigation (1 element)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
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.
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 checks passed
6 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 10 WCAG 2.2 A/AA and best-practice rules on the phone render: 6 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Arnold Clark Autoparts” and “Winter Essentials at Autoparts”). One clear main headline is easier for people and search engines.
Meta description is long (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
410 internal links, 19 external
The homepage links to 410 pages on arnoldclarkautoparts.com and 19 external pages.
6 checks passed
Title: 51 characters
Your title is a healthy 51 characters: “Car Parts & Accessories From Arnold Clark Autoparts”.
Canonical URL set
The canonical URL is https://www.arnoldclarkautoparts.com/.
Structured data in place
Structured data found: BreadcrumbList.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.arnoldclarkautoparts.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.
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.
llms.txt published
The site publishes https://www.arnoldclarkautoparts.com/llms.txt (195 KiB, 621 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without an H1
https://www.arnoldclarkautoparts.com/collections/ev-charging-cables and https://www.arnoldclarkautoparts.com/collections/exhausts 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 180 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 2 pages that loaded have a meta description.
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 2 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'placeholder')”.
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 12 words
The homepage has only about 12 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
11 calls to action
The homepage has 11 calls to action, for example “Shop our products”, “Shop now” and “Shop all”.
27 short forms
27 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 3 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
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 arnoldclarkautoparts.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Partly Pim Smarter Auto Parts · Blocky Fraud Blocker · Meteor Mega Menu · Lipscore Reviews · Crazy Egg · Hulk Form Builder · Cartbite · Bacon Menu · nofraud.com · archivepro.io · trustpilot.com
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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- 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 arnoldclarkautoparts.com, including 18 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.