Website review, no card needed
ashworth-golf.com website review
Visit site (opens in a new tab)Reviewed 6 November 202628 issues · 79 checks
This review found 28 issues worth fixing on ashworth-golf.com, 4 of them high impact, across 79 checks. The most urgent: interactive controls must not be nested (1 element). 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
88B- #5,869 of 124,214 reviewed websitesbeats 93%
- #3,181 of 69,818 online storesbeats 93%
- #3,081 of 63,493 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 95 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 108 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 120 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 124 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 131 ms |
| Oct 31, 2026 | 131 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.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 196 KiBAbout 196 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
550 ms · 116 KiB25 files are served with short cache lifetimes, so returning visitors download them again (116 KiB).
Improve image delivery
560 KiB15 images could be 560 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
450 ms · 93 KiBAbout 93 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Legacy JavaScript
300 ms · 38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
300 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, mountain.com and Google CDN and others), adding 564 KiB and 226 ms of main-thread time.
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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 447 ms of it running JavaScript. That is comfortably low.
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.7 s
10.7 sYour largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The St. George's Hill Collection hero image”.
Time to Interactive: 10.8 s
10.8 sThe page becomes fully interactive after 10.8 s. Good is under 3.8 s.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 131 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 132 ms
132 msReal visitors wait 132 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 726 ms
726 msReal visitors wait 726 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: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.7 MB in 239 requests
2.7 MBYour homepage downloads 2.7 MB in 239 requests on a phone: images 952 KiB (37), other files 770 KiB (95) and scripts 669 KiB (88). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (39 KiB) 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 0.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.7 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
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 133 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 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“The St. George's Hill Collection” and “Honor the walk”). One clear main headline is easier for people and search engines.
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.
138 internal links, 5 external
The homepage links to 138 pages on ashworth-golf.com and 5 external pages.
7 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Ashworth is the original, authentic golf apparel brand. From polos and t-shirts to pants and accessories, our pieces ar…”.
Title: 39 characters
Your title is a healthy 39 characters: “Ashworth - Golf Apparel and Accessories”.
Canonical URL set
The canonical URL is https://www.ashworth-golf.com/.
Structured data in place
Structured data found: Organization, Product and WebSite.
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.ashworth-golf.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (451 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ashworth-golf.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.ashworth-golf.com/collections/tops, https://www.ashworth-golf.com/collections/bottoms, https://www.ashworth-golf.com/collections/layers, https://www.ashworth-golf.com/collections/accessories, https://www.ashworth-golf.com/collections/golf-polos and https://www.ashworth-golf.com/collections/tops-bestsellers and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
2 checks passed
Tap targets are thumb-sized
36 of 40 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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 235 words
The homepage has only about 235 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
10 calls to action
The homepage has 10 calls to action, for example “Contact us”, “Shop Now” and “A Classic The 2Bar Stripe Shop Now”.
5 short forms
5 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks and a star rating.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
42 other companies contacted
Loading the homepage contacts 42 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 ashworth-golf.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gorgias Live Chat Helpdesk · Mntn · Klaviyo Email Marketing Sms · Swish · herokuapp.com · ashworth-golf.com · stamped.io
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
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on ashworth-golf.com, including 12 speed issues, 2 SEO issues and 5 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.