Website review, no card needed
tonyferguson.com website review
Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 82 checks
This review found 35 issues worth fixing on tonyferguson.com, 13 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
76C- #75,199 of 123,862 reviewed websitesbeats 35%
- #48,194 of 69,698 online storesbeats 26%
- #45,657 of 63,406 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 2.9 s |
| Nov 7, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 137 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 131 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 136 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 136 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 148 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 153 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 143 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 140 ms |
| Oct 24, 2026 | 139 ms |
| Oct 31, 2026 | 138 ms |
| Nov 7, 2026 | 134 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.4 s
4.5 s
5.6 s
6.7 s
7.8 s
9.0 s
Speed
Use efficient cache lifetimes
1.9 s · 691 KiB25 files are served with short cache lifetimes, so returning visitors download them again (691 KiB).
Reduce unused JavaScript
1.1 s · 620 KiBAbout 620 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Facebook and Google Tag Manager and others), adding 1.9 MB and 603 ms of main-thread time.
Improve image delivery
300 ms · 350 KiB14 images could be 350 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Klaviyo adds 153 ms
153 msKlaviyo costs a phone 153 ms of main-thread work and 408 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.
1,743 HTML elements
The page has 1,743 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 66 ms
66 msShopify costs a phone 66 ms of main-thread work and 632 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 139 ms. During a long task the page ignores taps.
Legacy JavaScript
95 KiBPolyfills for old browsers add 95 KiB JavaScript that modern phones do not need.
Reduce unused CSS
16 KiBAbout 16 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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 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.
Largest Contentful Paint: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.7 s
20.7 sThe page becomes fully interactive after 20.7 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Cumulative Layout Shift: 0.228
0.228The layout shifts by 0.228 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image 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-11-07, real Chrome visitors' tap response (inp) went from 137 ms to 134 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
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.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 766 ms
766 msReal visitors wait 766 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 112 ms
112 msScripts block the page for only 112 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.4 MB in 356 requests
4.4 MBYour homepage downloads 4.4 MB in 356 requests on a phone: scripts 1.8 MB (137), images 906 KiB (32) and other files 890 KiB (113). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Untitled_design_29.png 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 below the first screen load straight away
1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.25 g of CO₂e: 150.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
32 text elements with low contrast
32 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
[role="img"] and [role="image"] elements must have alternative text (3 elements)
[role="img"] and [role="image"] elements must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 33 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (90 characters)
Your title is 90 characters, so Google will cut it off around 60: “Best Meal Replacement Shakes in Australia | Weight Loss Shakes – Tony Ferguson Weight Loss”.
Meta description is long (246 characters)
Your meta description is 246 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
89 internal links, 10 external
The homepage links to 89 pages on tonyferguson.com and 10 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://tonyferguson.com/.
Structured data in place
Structured data found: Organization, Product 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://tonyferguson.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 (819 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://tonyferguson.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
https://tonyferguson.com/collections/all, https://tonyferguson.com/collections/shakes, https://tonyferguson.com/collections/single-sachets, https://tonyferguson.com/collections/protein-bars, https://tonyferguson.com/collections/bundles and https://tonyferguson.com/blogs/healthy-recipes and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://tonyferguson.com/pages/weight-loss-program, https://tonyferguson.com/pages/meal-plan, https://tonyferguson.com/pages/about-us, https://tonyferguson.com/pages/faqs and https://tonyferguson.com/pages/contact-us 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 35 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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=20131278&tm=gtm002&Ver=2&mid=f73cdc92-71cf-4297-bdfb-580770864103&bo=1&sid=62a09340dda311f1b495353563931787&vid=62a0beb0dda311f1b8ec91044e25f872&vids=1&msclkid=N&pi=91.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.
2 checks passed
Tap targets are thumb-sized
52 of 55 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 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 711 words of copy
The homepage carries about 711 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
11 calls to action
The homepage has 11 calls to action, for example “Shop”, “Contact Us” and “Buy 4 or more, save 30%”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 21 testimonial or review blocks, a star rating, 2 trust badges and “1,000+ reviews”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 2 of them by other companies (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.
41 other companies contacted
Loading the homepage contacts 41 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 tonyferguson.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Fbp Fast Bundle · Triplewhale · Reviews Co Uk Product And Merchant Review Collection · rechargecdn.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
Company
- Headquarters
- Queanbeyan
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on tonyferguson.com, including 18 speed issues, 4 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.