Website review, no card needed

beast.co.uk logo

beast.co.uk website review

Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 94 checks

This review found 35 issues worth fixing on beast.co.uk, 13 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.3 sMay 23Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
152 ms126 msMay 23Nov 7146 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026144 ms
May 30, 2026147 ms
Jun 6, 2026145 ms
Jun 13, 2026138 ms
Jun 20, 2026136 ms
Jun 27, 2026130 ms
Jul 4, 2026129 ms
Jul 11, 2026131 ms
Jul 18, 2026137 ms
Jul 25, 2026137 ms
Aug 1, 2026137 ms
Aug 8, 2026134 ms
Aug 15, 2026130 ms
Aug 22, 2026133 ms
Aug 29, 2026135 ms
Sep 5, 2026137 ms
Sep 12, 2026137 ms
Sep 19, 2026137 ms
Sep 26, 2026142 ms
Oct 3, 2026137 ms
Oct 10, 2026140 ms
Oct 17, 2026147 ms
Oct 24, 2026145 ms
Oct 31, 2026149 ms
Nov 7, 2026146 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

Full-page screenshot of beast.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beast.co.uk at 3.7 s3.7 s
  2. beast.co.uk at 7.3 s7.3 s
  3. beast.co.uk at 11.0 s11.0 s
  4. beast.co.uk at 14.7 s14.7 s
  5. beast.co.uk at 18.4 s18.4 s
  6. beast.co.uk at 22.0 s22.0 s
  7. beast.co.uk at 25.7 s25.7 s
  8. beast.co.uk at 29.4 s29.4 s

Speed

13 to fix54
  • Reduce unused JavaScript

    5.3 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.

  • Use efficient cache lifetimes

    2.0 s · 392 KiB

    23 files are served with short cache lifetimes, so returning visitors download them again (392 KiB).

  • Render-blocking requests

    1.2 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Main-thread work: 6.4 s

    A phone's processor spends 6.4 s on main-thread work while loading, 2.8 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 (Clarity, Shopify and pop-convert.com and others), adding 3.1 MB and 1.3 s of main-thread time.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    680 KiB

    3 images could be 680 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Shopify adds 294 ms

    294 ms

    Shopify costs a phone 294 ms of main-thread work and 1.3 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.

  • Reduce unused CSS

    300 ms · 113 KiB

    About 113 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Clarity adds 306 ms

    306 ms

    Clarity costs a phone 306 ms of main-thread work and 31 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 227 ms

    227 ms

    Klaviyo costs a phone 227 ms of main-thread work and 644 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.

  • LoyaltyLion adds 63 ms

    63 ms

    LoyaltyLion costs a phone 63 ms of main-thread work and 358 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.

  • azurefd.net adds 48 ms

    48 ms

    azurefd.net costs a phone 48 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.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • 8 long tasks on the main thread

    8 long tasks block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    70 KiB

    Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    12 KiB

    12 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 75 ms

    75 ms

    Your server sent the HTML in 75 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 72.6 s

    72.6 s

    Your largest element takes 72.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “X 10% OFF YOUR FIRST ORDER! Join the BEAST mailing list for…”.

  • Time to Interactive: 72.8 s

    72.8 s

    The page becomes fully interactive after 72.8 s. Good is under 3.8 s.

  • Speed Index: 15.2 s

    15.2 s

    Visually, the page fills in at 15.2 s (Speed Index). Good is under 3.4 s.

  • Cumulative Layout Shift: 0.189

    0.189

    The layout shifts by 0.189 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

  • 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 144 ms to 146 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: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 171 ms

    171 ms

    Real visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 502 ms

    502 ms

    Real visitors wait 502 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 16% faster for real visitors

    -16%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 73 ms

    73 ms

    Scripts block the page for only 73 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix36
  • Page weight: 14.3 MB in 673 requests

    14.3 MB

    Your homepage downloads 14.3 MB in 673 requests on a phone: media 7.3 MB (2), scripts 2.9 MB (298) and images 1.8 MB (22). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    beast_foods_mobile_banner.png weighs 722 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    apparel_social_proof_badges_877d9d53-e4e9-4ded-9ceb-db216540 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

    475 KiB

    1 image is downloaded at several times the size a phone draws it, for example beast_foods_mobile_banner.png at 2,000 px wide, shown at 390 px. Resized copies would save about 475 KiB.

  • 1 image in older formats

    1 image (50 KiB) is 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 4.1 g of CO₂ per visit

    4.05 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.05 g of CO₂e: 486.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fixGoogle 9190
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 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.

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 8598
  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 133 internal links, 8 external

    The homepage links to 133 pages on beast.co.uk and 8 external pages.

8 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Shop Eddie Hall's BEAST™ range of premium supplements, clothing and official merchandise today. Our products are crafte…”.

  • One H1 headline

    Your main headline reads: “Beast — Fuel Your Inner Beast”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “BEAST™ Supplements & Apparel | Eddie Hall”.

  • Canonical URL set

    The canonical URL is https://beast.co.uk/.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://beast.co.uk/sitemap.xml.

AI search readiness

100
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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (4,276 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://beast.co.uk/llms.txt (15 KiB, 59 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 2 pages slow to respond

    https://beast.co.uk/collections/mens and https://beast.co.uk/collections/womens took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    10 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9278
  • 3 broken images

    3 images failed to load on a phone, for example https://beast.co.uk/.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    30 of 32 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 390 words of copy

    The homepage carries about 390 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register” and “Learn More”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Register”, “Learn More” and “SHOP BEAST FOODS”.

  • 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: 1 customer or partner logo and 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 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.

  • 56 other companies contacted

    Loading the homepage contacts 56 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 beast.co.uk, 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 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Lipscore Reviews · Uppromote Affiliate · Microsoft Clarity · Klaviyo Email Marketing Sms · Loyalty Rewards And Referrals · Affliate By Secomapp · Pop Convert · Forms · Cornercart · Restockrocket · Discount Kit · trustpilot.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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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 beast.co.uk, including 18 speed issues, 1 SEO issue and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25