Website review, no card needed

zoevacosmetics.co.uk logo

zoevacosmetics.co.uk website review

Visit site (opens in a new tab)Reviewed 10 November 202643 issues · 85 checks

This review found 43 issues worth fixing on zoevacosmetics.co.uk, 13 of them high impact, across 85 checks. The most urgent: page weight: 23.6 MB in 456 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

Real-visitor load time (LCP)75th percentile, phones
1.9 s1.5 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
352 ms150 msMay 23Nov 7312 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026173 ms
May 30, 2026178 ms
Jun 6, 2026179 ms
Jun 13, 2026177 ms
Jun 20, 2026179 ms
Jun 27, 2026179 ms
Jul 4, 2026187 ms
Jul 11, 2026195 ms
Jul 18, 2026195 ms
Jul 25, 2026195 ms
Aug 1, 2026195 ms
Aug 8, 2026203 ms
Aug 15, 2026208 ms
Aug 22, 2026211 ms
Aug 29, 2026211 ms
Sep 5, 2026205 ms
Sep 12, 2026203 ms
Sep 19, 2026213 ms
Sep 26, 2026236 ms
Oct 3, 2026281 ms
Oct 10, 2026322 ms
Oct 17, 2026328 ms
Oct 24, 2026329 ms
Oct 31, 2026328 ms
Nov 7, 2026312 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 zoevacosmetics.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zoevacosmetics.co.uk at 2.8 s2.8 s
  2. zoevacosmetics.co.uk at 5.6 s5.6 s
  3. zoevacosmetics.co.uk at 8.4 s8.4 s
  4. zoevacosmetics.co.uk at 11.3 s11.3 s
  5. zoevacosmetics.co.uk at 14.1 s14.1 s
  6. zoevacosmetics.co.uk at 16.9 s16.9 s
  7. zoevacosmetics.co.uk at 19.7 s19.7 s
  8. zoevacosmetics.co.uk at 22.5 s22.5 s

Speed

12 to fix58
  • 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.

  • Main-thread work: 9.3 s

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

  • Reduce unused JavaScript

    660 ms · 923 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 2.5 MB and 1.3 s of main-thread time.

  • Mobile performance score: 58

    58/100

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

  • Improve image delivery

    811 KiB

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

  • Google Tag Manager adds 354 ms

    354 ms

    Google Tag Manager costs a phone 354 ms of main-thread work and 670 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.

  • Use efficient cache lifetimes

    411 KiB

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

  • 2,730 HTML elements

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

  • Shopify adds 125 ms

    125 ms

    Shopify costs a phone 125 ms of main-thread work and 630 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 148 ms

    148 ms

    Klaviyo costs a phone 148 ms of main-thread work and 353 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 102 ms

    102 ms

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

  • Reduce unused CSS

    150 ms · 86 KiB

    About 86 KiB of CSS is downloaded but never applied on this page. 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 153 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    66 KiB

    Polyfills for old browsers add 66 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.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 66 ms

    66 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Time to Interactive: 27.3 s

    27.3 s

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

  • Largest Contentful Paint: 9.1 s

    9.1 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user INP: 286 ms

    286 ms

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

  • Tap response (INP) got 82% slower for real visitors

    +82%

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

  • Total Blocking Time: 310 ms

    310 ms

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

  • Cumulative Layout Shift: 0.125

    0.125

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 381 ms

    381 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

Images and page weight

4 to fix38
  • Page weight: 23.6 MB in 456 requests

    23.6 MB

    Your homepage downloads 23.6 MB in 456 requests on a phone: media 18.0 MB (5), scripts 2.4 MB (102) and other files 1.4 MB (278). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    HP26_CRYSTAL-LIPSTICK_MULTI_TILE_01.gif weighs 535 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (535 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.

  • 2 images below the first screen load straight away

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

  • About 6.7 g of CO₂ per visit

    6.70 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8490
  • 10 tap targets too small

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

  • ARIA tooltip nodes must have an accessible name (1 element)

    ARIA tooltip nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 6 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 22 links without text

    22 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 55 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 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

1 to fixGoogle 8598
  • 12 links crawlers can't follow

    12 links have no real href, so search engines can't follow them.

  • 190 internal links, 14 external

    The homepage links to 190 pages on zoevacosmetics.co.uk and 14 external pages.

8 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “Beauty, makeup & brushes by ZOEVA 💖 Discover new beauty trends! 💖 Brushes, eyeshadow, eyeliners & more! ➤ Shop online…”.

  • One H1 headline

    Your main headline reads: “ZOEVA Cosmetics UK”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “ZOEVA | Beauty, Makeup & Brushes | Shop now!”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (941 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 10 pages without a meta description

    https://zoevacosmetics.co.uk/products/fsb-xmas2026, https://zoevacosmetics.co.uk/collections/christmas-collection-2026, https://zoevacosmetics.co.uk/collections/christmas-eyes, https://zoevacosmetics.co.uk/collections/christmas-lips, https://zoevacosmetics.co.uk/collections/christmas-gift-sets and https://zoevacosmetics.co.uk/collections/eyeshadow and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://zoevacosmetics.co.uk/products/fsb-xmas2026, https://zoevacosmetics.co.uk/collections/christmas-collection-2026, https://zoevacosmetics.co.uk/collections/christmas-eyes, https://zoevacosmetics.co.uk/collections/christmas-lips, https://zoevacosmetics.co.uk/collections/christmas-gift-sets and https://zoevacosmetics.co.uk/collections/eyeliner and 8 others 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 81 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

2 to fixGoogle 9687
  • 17 small tap targets

    17 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://cdn.shopify.com/extensions/01a1b738-ca9b-774d-8972-688941f78dbc/cart-drawer-upsell…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 525 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop All”, “Register” and “Track My Order”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 26 cookies set on arrival

    26

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

  • 42 other companies contacted

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

Apps your storefront loads

Pandectes Gdpr · Yotpo Product Reviews · Gorgias Live Chat Helpdesk · Hulk Form Builder · Microsoft Clarity · Klaviyo Email Marketing Sms · Oxify Cart Drawer · Elevar Conversion Tracking · Rebuy Personalization Engine · Zoeva Discounts · Gdpr Cookie Consent · Polar Analytics · web.app · rebuyengine.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
Bootstrap
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 43 issues on zoevacosmetics.co.uk, including 21 speed issues, 1 SEO issue 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