Website review, no card needed

drink-mana.co.uk logo

drink-mana.co.uk website review

Visit site (opens in a new tab)Reviewed 11 November 202631 issues · 73 checks

This review found 31 issues worth fixing on drink-mana.co.uk, 9 of them high impact, across 73 checks. The most urgent: render-blocking requests. 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

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

How it loaded on a phone

  1. drink-mana.co.uk at 0.4 s0.4 s
  2. drink-mana.co.uk at 0.9 s0.9 s
  3. drink-mana.co.uk at 1.3 s1.3 s
  4. drink-mana.co.uk at 1.7 s1.7 s
  5. drink-mana.co.uk at 2.1 s2.1 s
  6. drink-mana.co.uk at 2.6 s2.6 s
  7. drink-mana.co.uk at 3.0 s3.0 s
  8. drink-mana.co.uk at 3.4 s3.4 s

Speed

10 to fix65
  • Render-blocking requests

    1.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (POWr, drink-mana.com and weglot.com and others), adding 3.5 MB and 1.2 s of main-thread time.

  • Mobile performance score: 65

    65/100

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

  • Reduce unused JavaScript

    150 ms · 459 KiB

    About 459 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • POWr adds 479 ms

    479 ms

    POWr costs a phone 479 ms of main-thread work and 13 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.

  • drink-mana.com adds 336 ms

    336 ms

    drink-mana.com costs a phone 336 ms of main-thread work and 490 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.

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Shopify adds 98 ms

    98 ms

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

  • 2,125 HTML elements

    The page has 2,125 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Klaviyo adds 94 ms

    94 ms

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

  • Improve image delivery

    158 KiB

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

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    130 KiB

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    32 KiB

    About 32 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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: 80 ms

    80 ms

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

Core Web Vitals

4 to fix65
  • Largest Contentful Paint: 15.1 s

    15.1 s

    Your largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Fast complete nutrition with creatine Built for hard traini…”.

  • Time to Interactive: 23.4 s

    23.4 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • 19 images without width and height

    19 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 133 ms

    133 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 5.9 MB in 436 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 436 requests on a phone: images 2.2 MB (70), scripts 1.7 MB (102) and other files 1.3 MB (244). Under 2 MB keeps phones on slow connections fast.

  • 8 images below the first screen load straight away

    8 images further down the page (442 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    112 KiB

    1 image is downloaded at several times the size a phone draws it, for example blog_2_de3216b7-a738-4216-8105-0435fcc35749.png at 1,930 px wide, shown at 331 px. Resized copies would save about 112 KiB.

  • 2 images in older formats

    2 images (214 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 1.7 g of CO₂ per visit

    1.68 g

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

Accessibility

7 to fixGoogle 8390
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • 21 text elements with low contrast

    21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • 68 images without alt text

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

  • All page content should be contained by landmarks (24 elements)

    All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.

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

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h3 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

5 to fixGoogle 7784
  • Canonical points to another host

    Your canonical URL points to drink-mana.com, not drink-mana.co.uk, so Google may credit that host instead.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 28 H1 headlines

    There are 28 <h1> headlines (“Fast complete nutrition with creatine”, “Built for hard training and long workdays. Pick t…” and “Powdered Meals”). One clear main headline is easier for people and search engines.

  • 7 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 87 internal links, 44 external

    The homepage links to 87 pages on drink-mana.co.uk and 44 external pages.

5 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Nutritionally complete food, now better than ever thanks to our latest recipe. Just mix with water and, in under a minu…”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Mana™ | Food for a Better Life”.

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://drink-mana.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

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

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    44 of 48 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 855 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy for €70 and you have free shipping±” and “Buy Now”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Buy Now”, “Learn More” and “Learn more”.

  • 11 short forms

    11 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 19 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 15 cookies set on arrival

    15

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

  • 31 other companies contacted

    Loading the homepage contacts 31 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 drink-mana.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 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Judge Me Reviews · Pagefly Ai Page Builder · Weglot Translate Your Store · Gdpr Cookie Consent · Stape Remix · Growave Loyalty Wishlist · Simple Social Login · cloudfront.net · powr.io · klaviyo.com · rechargecdn.com · gorgias.chat · ablestar.app · 9gtb.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

CMS
adastra
Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on drink-mana.co.uk, including 14 speed issues and 5 SEO issues. 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