Website review, no card needed
donaldrussell.com website review
Visit site (opens in a new tab)Reviewed 5 November 202628 issues · 85 checks
This review found 28 issues worth fixing on donaldrussell.com, 7 of them high impact, across 85 checks. The most urgent: 3,259 HTML elements. 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
87B- #8,156 of 117,595 reviewed websitesbeats 90%
- #4,752 of 66,923 online storesbeats 89%
- #4,611 of 61,018 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 861 ms |
| May 23, 2026 | 857 ms |
| May 30, 2026 | 900 ms |
| Jun 6, 2026 | 931 ms |
| Jun 13, 2026 | 987 ms |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 97 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 171 ms |
| Jul 25, 2026 | 183 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 189 ms |
| Aug 22, 2026 | 192 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 185 ms |
| Sep 19, 2026 | 181 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 181 ms |
| Oct 10, 2026 | 188 ms |
| Oct 17, 2026 | 194 ms |
| Oct 24, 2026 | 193 ms |
| Oct 31, 2026 | 191 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.7 s
3.1 s
Speed
3,259 HTML elements
The page has 3,259 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
600 ms · 1.3 MB30 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms17 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused JavaScript
600 ms · 114 KiBAbout 114 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.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 985 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 third-party services on the page
6 third-party services load with your homepage (cdn-cookieyes.com, nice-team.net and Shopify and others), adding 362 KiB and 370 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 56 KiB8 files are served with short cache lifetimes, so returning visitors download them again (56 KiB).
Minify JavaScript
150 ms · 47 KiB47 KiB could be saved by minifying JavaScript.
Legacy JavaScript
150 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
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
Largest Contentful Paint: 12.0 s
12.0 sYour largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 12.4 s
12.4 sThe page becomes fully interactive after 12.4 s. Good is under 3.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 87% slower for real visitors
+87%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 97 ms to 191 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 181 ms
181 msReal visitors wait 181 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 570 ms
570 msReal visitors wait 570 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 188 ms
188 msScripts block the page for only 188 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 243 requests
3.3 MBYour homepage downloads 3.3 MB in 243 requests on a phone: images 1.8 MB (44), other files 755 KiB (95) and scripts 513 KiB (63). Under 2 MB keeps phones on slow connections fast.
7 images below the first screen load straight away
7 images further down the page (605 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
210 KiB4 images are downloaded at several times the size a phone draws them, for example DRSalmonEnCroutePortraitRGB_220be11a-b593-4821-b86d-c8b759ca at 770 px wide, shown at 172 px. Resized copies would save about 210 KiB.
2 images in older formats
2 images (132 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.
About 0.9 g of CO₂ per visit
0.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 113.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h1 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 99 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 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “Buy Meat Online | Online Butchers | Donald Russell – Donald Russell Limited”.
3 H1 headlines
There are 3 <h1> headlines (“”, “” and “Popular Recipes”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
195 internal links, 11 external
The homepage links to 195 pages on donaldrussell.com and 11 external pages.
5 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Buy meat online with Donald Russell. We have 50 years' experience in supplying quality beef, chicken, lamb and seafood …”.
Canonical URL set
The canonical URL is https://donaldrussell.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://donaldrussell.com/sitemap.xml.
AI search readiness
4 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.
Text is in the HTML
Your server sends the page's text in the HTML (2,021 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://donaldrussell.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://donaldrussell.com/pages/christmas has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://donaldrussell.com/pages/christmas has 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 79 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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
155 of 159 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 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.
About 918 words of copy
The homepage carries about 918 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call us on 03330 066257” and “SHOP CHRISTMAS”.
25 calls to action
The homepage has 25 calls to action, for example “Start shopping”, “Shop All Christmas” and “Shop All Beef”.
36 short forms
36 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 donaldrussell.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
Klaviyo Email Marketing Sms · Bundler Bundles App · Microsoft Clarity · Yotpo Loyalty Rewards · Yotpo Product Reviews · Selleasy · nice-team.net
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
Company
- Employees
- 200
- Headquarters
- Inverurie
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 donaldrussell.com, including 12 speed issues, 3 SEO issues and 1 conversion gap. 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.