Website review, no card needed
bathrugbyshop.com website review
Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 90 checks
This review found 43 issues worth fixing on bathrugbyshop.com, 15 of them high impact, across 90 checks. The most urgent: page weight: 15.0 MB in 519 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
78C- #60,432 of 119,805 reviewed websitesbeats 44%
- #39,642 of 67,930 online storesbeats 36%
- #37,894 of 61,917 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 977 ms |
| Jun 13, 2026 | 963 ms |
| Jun 20, 2026 | 943 ms |
| Jun 27, 2026 | 956 ms |
| Jul 4, 2026 | 985 ms |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 997 ms |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 120 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 124 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 123 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 125 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 124 ms |
| Sep 26, 2026 | 124 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 122 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
1.1 s
2.2 s
3.3 s
4.5 s
5.6 s
6.7 s
7.8 s
8.9 s
Speed
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,543 HTML elements
The page has 4,543 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (getpurpledot.com, Google Tag Manager and Shopify and others), adding 1.7 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
750 ms · 567 KiBAbout 567 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
900 ms · 314 KiB15 files are served with short cache lifetimes, so returning visitors download them again (314 KiB).
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
getpurpledot.com adds 610 ms
610 msgetpurpledot.com costs a phone 610 ms of main-thread work and 159 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
455 KiB11 images could be 455 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 315 ms
315 msGoogle Tag Manager costs a phone 315 ms of main-thread work and 506 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 245 ms
245 msShopify costs a phone 245 ms of main-thread work and 518 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.
Klaviyo adds 159 ms
159 msKlaviyo costs a phone 159 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.
Reduce unused CSS
180 ms · 24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.
Render-blocking requests
200 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 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: 35 ms
35 msYour server sent the HTML in 35 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.9 s
14.9 sYour largest element takes 14.9 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.1 s
24.1 sThe page becomes fully interactive after 24.1 s. Good is under 3.8 s.
Speed Index: 13.0 s
13.0 sVisually, the page fills in at 13.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 242 ms
242 msScripts block taps and scrolling for 242 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 120 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 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: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 347 ms
347 msReal visitors wait 347 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 15.0 MB in 519 requests
15.0 MBYour homepage downloads 15.0 MB in 519 requests on a phone: images 12.0 MB (231), scripts 1.7 MB (111) and other files 946 KiB (149). Under 2 MB keeps phones on slow connections fast.
24 images in older formats
24 images (1.5 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
Bath-Rugby-000-Black-Friday_Pre-BF_Up-to-30-off-Training-Mob 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).
1 image far larger than shown
51 KiB1 image is downloaded at several times the size a phone draws it, for example 60fad036-cc46-422e-b1fd-754550bd9a78.png at 1,500 px wide, shown at 325 px. Resized copies would save about 51 KiB.
4 images below the first screen load straight away
4 images further down the page (234 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.3 g of CO₂ per visit
4.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.25 g of CO₂e: 510.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (47 elements)
Certain ARIA roles must be contained by particular parents: 47 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (33 elements)
Certain ARIA roles must contain particular children: 33 elements on the page fail this check, rated critical by axe-core.
15 buttons without a name
15 buttons have no accessible name, so screen readers announce just “button”.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Orphan list items
Some list items are not inside a list.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious 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.
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.
51 form fields without a label
51 form fields have no label, so screen readers announce an empty box and autofill guesses.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (1 element).
2 checks passed
Every image has alt text
All 555 images in the HTML carry an alt attribute.
57 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 67 WCAG 2.2 A/AA and best-practice rules on the phone render: 57 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (10 characters)
Your title is only 10 characters: “Bath Rugby”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
217 internal links, 0 external
The homepage links to 217 pages on bathrugbyshop.com and 0 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://bathrugbyshop.com/.
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://bathrugbyshop.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 (1,263 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bathrugbyshop.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://bathrugbyshop.com/collections/black-friday, https://bathrugbyshop.com/collections/26-27-third-kit, https://bathrugbyshop.com/collections/26-27-training-range, https://bathrugbyshop.com/collections/50-off-pro-kits, https://bathrugbyshop.com/collections/outlet and https://bathrugbyshop.com/collections/hot-deals and 9 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 83 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 “Error: <path> attribute d: Expected number, "… 12.1483 16.7422C12.1483 16.3868…".”.
2 checks passed
Tap targets are thumb-sized
175 of 186 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
A 11-field form
Your longest form asks for 11 fields (0 required). Every extra field lowers completion.
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.
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 842 words of copy
The homepage carries about 842 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL” and “SHOP BY”.
10 calls to action
The homepage has 10 calls to action, for example “SHOP ALL”, “Shop All” and “Shop By”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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 (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.
33 other companies contacted
Loading the homepage contacts 33 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 bathrugbyshop.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Klaviyo Email Marketing Sms · Triplewhale · Gdpr Backpack · gorgias.chat · 9gtb.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
- 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 43 issues on bathrugbyshop.com, including 16 speed issues, 5 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.