Website review, no card needed
cotswoldoutdoor.com website review
Visit site (opens in a new tab)Reviewed 26 October 202645 issues · 85 checks
This review found 45 issues worth fixing on cotswoldoutdoor.com, 19 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 803 ms |
| May 16, 2026 | 788 ms |
| May 23, 2026 | 773 ms |
| May 30, 2026 | 769 ms |
| Jun 6, 2026 | 767 ms |
| Jun 13, 2026 | 770 ms |
| Jun 20, 2026 | 774 ms |
| Jun 27, 2026 | 774 ms |
| Jul 4, 2026 | 776 ms |
| Jul 11, 2026 | 781 ms |
| Jul 18, 2026 | 781 ms |
| Jul 25, 2026 | 770 ms |
| Aug 1, 2026 | 763 ms |
| Aug 8, 2026 | 756 ms |
| Aug 15, 2026 | 766 ms |
| Aug 22, 2026 | 791 ms |
| Aug 29, 2026 | 868 ms |
| Sep 5, 2026 | 942 ms |
| Sep 12, 2026 | 988 ms |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 990 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 183 ms |
| May 16, 2026 | 179 ms |
| May 23, 2026 | 178 ms |
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 179 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 181 ms |
| Jul 11, 2026 | 184 ms |
| Jul 18, 2026 | 183 ms |
| Jul 25, 2026 | 181 ms |
| Aug 1, 2026 | 181 ms |
| Aug 8, 2026 | 181 ms |
| Aug 15, 2026 | 184 ms |
| Aug 22, 2026 | 186 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 186 ms |
| Sep 19, 2026 | 186 ms |
| Sep 26, 2026 | 186 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 183 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.3 s
Speed
Reduce unused JavaScript
3.0 s · 802 KiBAbout 802 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 455 KiB61 files are served with short cache lifetimes, so returning visitors download them again (455 KiB).
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,482 HTML elements
The page has 3,482 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
500 ms · 807 KiB12 images could be 807 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Reduce unused CSS
730 ms · 128 KiBAbout 128 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 730 ms faster on a phone.
Render-blocking requests
800 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Adobe Tag Manager and adn.cloud and others), adding 1.6 MB and 494 ms of main-thread time.
Feefo.com adds 57 ms
57 msFeefo.com costs a phone 57 ms of main-thread work and 329 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.
zitcha.app adds 0 ms
0 mszitcha.app costs a phone 0 ms of main-thread work and 681 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 95 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
15 KiBPolyfills for old browsers add 15 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: 230 ms
230 msYour server sent the HTML in 230 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.
Largest Contentful Paint: 12.8 s
12.8 sYour largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Shop up to 20% off all footwear on Cotswold Outdoor”.
Time to Interactive: 21.3 s
21.3 sThe page becomes fully interactive after 21.3 s. Good is under 3.8 s.
First Contentful Paint: 4.9 s
4.9 sThe first text or image appears after 4.9 s on a phone. Good is under 1.8 s.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.8 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.183
0.183The layout shifts by 0.183 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 183 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 358 ms
358 msReal visitors wait 358 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 97 ms
97 msScripts block the page for only 97 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.8 MB in 152 requests
3.8 MBYour homepage downloads 3.8 MB in 152 requests on a phone: images 1.7 MB (49), scripts 1.5 MB (60) and fonts 321 KiB (7). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (893 KiB) 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.
8 images below the first screen load straight away
8 images further down the page (812 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
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.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 buttons without a name
10 buttons have no accessible name, so screen readers announce just “button”.
[role="img"] and [role="image"] elements must have alternative text (69 elements)
[role="img"] and [role="image"] elements must have alternative text: 69 elements on the page fail this check, rated serious by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (2 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
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.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (48 elements)
All page content should be contained by landmarks: 48 elements on the page fail 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
40 form fields without a label
40 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
27 links crawlers can't follow
27 links have no real href, so search engines can't follow them.
Structured data has 3 problems
Structured data found (Organization and WebSite) but with 3 problems, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
316 internal links, 6 external
The homepage links to 316 pages on cotswoldoutdoor.com and 6 external pages.
5 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “Find the best range of Outdoor Clothing and Footwear, Climbing, Camping Equipment and more. Price Match Promise guarant…”.
Title: 47 characters
Your title is a healthy 47 characters: “Outdoor Clothing & Equipment | Cotswold Outdoor”.
Canonical URL set
The canonical URL is https://www.cotswoldoutdoor.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://www.cotswoldoutdoor.com/sitemap/index.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.cotswoldoutdoor.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,073 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.cotswoldoutdoor.com/c/campaigns/offers/outdoor-footwear-offers.html is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 175 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 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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_CONNECTION_CLOSED”.
2 checks passed
Tap targets are thumb-sized
64 of 64 tappable elements near the top are at least 24 px.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 69-field form
Your longest form asks for 69 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 471 words of copy
The homepage carries about 471 words of visible text.
2 checks passed
20 calls to action
The homepage has 20 calls to action, for example “Shop All Jackets”, “Shop All Footwear” and “Shop All Trousers & Shorts”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
10 other companies contacted
Loading the homepage contacts 10 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 cotswoldoutdoor.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- CloudFront
Company
- Founded
- 1974
- Headquarters
- Malmesbury
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on cotswoldoutdoor.com, including 19 speed issues, 4 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.