Website review, no card needed

evolvebeauty.co.uk logo

evolvebeauty.co.uk website review

Visit site (opens in a new tab)Reviewed 20 November 202630 issues · 83 checks

This review found 30 issues worth fixing on evolvebeauty.co.uk, 7 of them high impact, across 83 checks. The most urgent: main-thread work: 7.9 s. 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.1 sMay 30Nov 141.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.6 s
Jul 25, 20261.6 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.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.3 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Nov 14, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
276 ms166 msMay 30Nov 14179 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026210 ms
Jun 6, 2026206 ms
Jun 13, 2026207 ms
Jun 20, 2026209 ms
Jun 27, 2026219 ms
Jul 4, 2026226 ms
Jul 11, 2026235 ms
Jul 18, 2026245 ms
Jul 25, 2026254 ms
Aug 1, 2026260 ms
Aug 8, 2026263 ms
Aug 15, 2026263 ms
Aug 22, 2026261 ms
Aug 29, 2026248 ms
Sep 5, 2026237 ms
Sep 12, 2026228 ms
Sep 19, 2026224 ms
Sep 26, 2026229 ms
Oct 3, 2026228 ms
Oct 10, 2026231 ms
Oct 17, 2026225 ms
Oct 24, 2026187 ms
Oct 31, 2026186 ms
Nov 7, 2026179 ms
Nov 14, 2026179 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 evolvebeauty.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. evolvebeauty.co.uk at 1.0 s1.0 s
  2. evolvebeauty.co.uk at 2.1 s2.1 s
  3. evolvebeauty.co.uk at 3.1 s3.1 s
  4. evolvebeauty.co.uk at 4.2 s4.2 s
  5. evolvebeauty.co.uk at 5.2 s5.2 s
  6. evolvebeauty.co.uk at 6.2 s6.2 s
  7. evolvebeauty.co.uk at 7.3 s7.3 s
  8. evolvebeauty.co.uk at 8.3 s8.3 s

Speed

11 to fix57
  • Main-thread work: 7.9 s

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

  • 6,213 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Shopify and heatmap.com and others), adding 3.0 MB and 1.6 s of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 1.1 MB

    24 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Reduce unused JavaScript

    150 ms · 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 150 ms faster on a phone.

  • Mobile performance score: 57

    57/100

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

  • Klaviyo adds 291 ms

    291 ms

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

  • Shopify adds 241 ms

    241 ms

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

  • rebuyengine.com adds 207 ms

    207 ms

    rebuyengine.com costs a phone 207 ms of main-thread work and 752 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.

  • octaneai.com adds 199 ms

    199 ms

    octaneai.com costs a phone 199 ms of main-thread work and 327 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.

  • Yotpo adds 184 ms

    184 ms

    Yotpo costs a phone 184 ms of main-thread work and 337 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

    150 ms · 158 KiB

    8 images could be 158 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 14 long tasks on the main thread

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

  • Render-blocking requests

    100 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.

  • Reduce unused CSS

    70 KiB

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

  • Legacy JavaScript

    67 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 34.6 s

    34.6 s

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

  • Largest Contentful Paint: 6.3 s

    6.3 s

    Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 7.5 s

    7.5 s

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

  • Total Blocking Time: 419 ms

    419 ms

    Scripts block taps and scrolling for 419 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 4 images without width and height

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

9 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.2 s

    1.2 s

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

  • Real-user INP: 188 ms

    188 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 328 ms

    328 ms

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

  • Tap response (INP) got 14% faster for real visitors

    -14%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 210 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    -23%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 7.0 MB in 710 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 710 requests on a phone: scripts 3.3 MB (248), other files 2.0 MB (342) and images 772 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    1.97 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9695
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 17 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • One H1 headline

    Your <h1> is empty.

  • 180 internal links, 13 external

    The homepage links to 180 pages on evolvebeauty.co.uk and 13 external pages.

6 checks passed
  • Meta description: 109 characters

    Your meta description is 109 characters: “Evolve Organic Beauty makes artisan natural and organic skincare for sensitive skin. Free delivery available.”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Evolve Organic Beauty | Award Winning Artisan Skincare‎”.

  • Canonical URL set

    The canonical URL is https://www.evolvebeauty.com/en-us.

  • 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.evolvebeauty.com/sitemap.xml.

AI search readiness

100
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.evolvebeauty.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.evolvebeauty.com/en-us/pages/join-our-mailing-list 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 66 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 7789
  • 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.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “MinMaxify is deactivated for this website. Please don't forget to remove minmaxify-head.liquid still being referenced b…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 23 words

    The homepage has only about 23 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

4 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “Subscribe & Save”, “Book a Skincare Consultation” and “Contact Us”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks, a star rating and 1 trust badge.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 20 cookies set on arrival

    20

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

  • 39 other companies contacted

    Loading the homepage contacts 39 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 evolvebeauty.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 18 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Blockify Fraud Filter · Minmaxify Order Limits · Yotpo Loyalty Rewards · Ground · Yotpo Product Reviews · Klaviyo Email Marketing Sms · Region Restrictions · Stape Remix · Gdpr Backpack · Orbe Geolocation · cloudfront.net · gorgias.chat · rebuyengine.com · superfiliate-cdn.com · 9gtb.com · octaneai.com · kxcdn.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
Hosting
Shopify

Company

Headquarters
Saint Albans

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on evolvebeauty.co.uk, including 17 speed issues, 3 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

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