Website review, no card needed
purdey.com website review
Visit site (opens in a new tab)Reviewed 4 November 202637 issues · 75 checks
This review found 37 issues worth fixing on purdey.com, 9 of them high impact, across 75 checks. The most urgent: page weight: 14.5 MB in 258 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- #55,120 of 108,423 reviewed websitesbeats 44%
- #36,103 of 61,494 online storesbeats 36%
- #34,532 of 56,117 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 988 ms |
| May 23, 2026 | 971 ms |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 984 ms |
| Jun 20, 2026 | 981 ms |
| Jun 27, 2026 | 965 ms |
| Jul 4, 2026 | 900 ms |
| Jul 11, 2026 | 959 ms |
| Jul 18, 2026 | 984 ms |
| Jul 25, 2026 | 998 ms |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 990 ms |
| Aug 22, 2026 | 896 ms |
| Aug 29, 2026 | 884 ms |
| Sep 5, 2026 | 827 ms |
| Sep 12, 2026 | 760 ms |
| Sep 19, 2026 | 746 ms |
| Sep 26, 2026 | 731 ms |
| Oct 3, 2026 | 725 ms |
| Oct 10, 2026 | 701 ms |
| Oct 17, 2026 | 737 ms |
| Oct 24, 2026 | 703 ms |
| Oct 31, 2026 | 689 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 103 ms |
| May 23, 2026 | 100 ms |
| May 30, 2026 | 100 ms |
| Jun 6, 2026 | 102 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 115 ms |
| Aug 8, 2026 | 117 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 119 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 122 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 117 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
Speed
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: 8.4 s
A phone's processor spends 8.4 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Vimeo and Google Tag Manager and others), adding 11.0 MB and 2.4 s of main-thread time.
Vimeo adds 517 ms
517 msVimeo costs a phone 517 ms of main-thread work and 9.4 MB 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
350 ms · 1.1 MB17 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Reduce unused JavaScript
1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page.
Google CDN adds 641 ms
641 msGoogle CDN costs a phone 641 ms of main-thread work and 1.1 MB 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.
Render-blocking requests
700 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Google Tag Manager adds 419 ms
419 msGoogle Tag Manager costs a phone 419 ms of main-thread work and 130 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.
Facebook adds 363 ms
363 msFacebook costs a phone 363 ms of main-thread work and 229 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 321 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
315 KiB16 files are served with short cache lifetimes, so returning visitors download them again (315 KiB).
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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
Time to Interactive: 24.3 s
24.3 sThe page becomes fully interactive after 24.3 s. Good is under 3.8 s.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.238
0.238The layout shifts by 0.238 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 103 ms to 117 ms 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: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 531 ms
531 msReal visitors wait 531 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 14.5 MB in 258 requests
14.5 MBYour homepage downloads 14.5 MB in 258 requests on a phone: other files 9.3 MB (129), scripts 2.6 MB (60) and images 2.1 MB (27). Under 2 MB keeps phones on slow connections fast.
About 4.1 g of CO₂ per visit
4.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.10 g of CO₂e: 491.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Form elements do not have associated labels
Form elements do not have associated labels (1 element).
2 links without text
2 links have no text or label, so screen readers cannot say where they go.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (87 characters)
Your title is 87 characters, so Google will cut it off around 60: “James Purdey & Sons Ltd | Guns & Rifles | Clothing & Accessories – Purdey Guns & Rifles”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
75 internal links, 37 external
The homepage links to 75 pages on purdey.com and 37 external pages.
5 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Founded in 1814, James Purdey & Sons, or simply Purdey, are renowned for bespoke sporting shotguns and rifles, and luxu…”.
Canonical URL set
The canonical URL is https://www.purdey.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.purdey.com/sitemap.xml.
AI search readiness
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://www.purdey.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages without a meta description
https://www.purdey.com/products/the-sidelock-side-by-side, https://www.purdey.com/products/sidelock-over-and-under-1, https://www.purdey.com/products/damascus-gun, https://www.purdey.com/products/sidelock-hammer-ejector, https://www.purdey.com/products/trigger-plate and https://www.purdey.com/products/purdey-sporter and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://www.purdey.com/pages/our-bespoke-models, https://www.purdey.com/products/the-sidelock-side-by-side, https://www.purdey.com/products/sidelock-over-and-under-1, https://www.purdey.com/products/damascus-gun, https://www.purdey.com/products/sidelock-hammer-ejector and https://www.purdey.com/products/trigger-plate and 5 others 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 53 found) and read each the way a search engine does.
5 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.
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
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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 console errors
2 errors were logged to the browser console during Google's test (“requestStorageAccess: Permission denied.”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 10-field form
Your longest form asks for 10 fields (3 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 1,061 words of copy
The homepage carries about 1,061 words of visible text.
2 checks passed
15 calls to action
The homepage has 15 calls to action, for example “Book An Appointment”, “Contact The Team>” and “Book Online>”.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Microsoft Clarity.
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 purdey.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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 | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
Company
- Founded
- 1814
- Headquarters
- London
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 purdey.com, including 18 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.