marieveronique.com website review

About 995 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

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

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

Shopify costs a phone 1.0 s of main-thread work and 498 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

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

2 KiB could be saved by minifying JavaScript.

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

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

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

Polyfills for old browsers add 84 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

2 KiB could be saved by minifying CSS.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 404 requests on a phone: scripts 2.5 MB (128), other files 1.4 MB (235) and images 381 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

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

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

Your title is only 15 characters: “Marie Veronique”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“Principles of”, “Skin Function” and “MEET MARIE”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.marieveronique.com/search?q={search_term_string}")”.

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

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

The homepage links to 156 pages on marieveronique.com and 5 external pages.

https://www.marieveronique.com/collections/product-type has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.marieveronique.com/collections/all, https://www.marieveronique.com/collections/product-type, https://www.marieveronique.com/collections/serums, https://www.marieveronique.com/collections/skin-conditions, https://www.marieveronique.com/collections/stable-balanced-skin and https://www.marieveronique.com/collections/age-delay have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.marieveronique.com/collections/product-type and https://www.marieveronique.com/collections/skin-conditions have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97036358&tm=gtm002&Ver=2&mid=2455af07-44ed-47c3-aeaf-81b2c8f9770c&bo=1&sid=add43fd0d9c211f19005bf1f3efbc1d0&vid=add49b40d9c211f19643b32ac3db2fea&vids=1&msclkid=N&gtm_t.

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.marieveronique.com/cdn/shop/t/195/assets/custom-styles.css?v=19416' because it…”.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 411 words of visible text.

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.

Opening the homepage sets 24 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.