marchesa.com website review

24 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Clarity, Klaviyo and Forter and others), adding 3.2 MB and 417 ms of main-thread time.

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

cloudfront.net costs a phone 1 ms of main-thread work and 1.8 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.

Klaviyo costs a phone 138 ms of main-thread work and 310 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 costs a phone 15 ms of main-thread work and 653 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.

About 158 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

10 KiB could be saved by minifying JavaScript.

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 9.2 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 17.4 s. Good is under 3.8 s.

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

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

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

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

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

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

Your homepage downloads 7.1 MB in 492 requests on a phone: images 4.6 MB (115), other files 1.3 MB (265) and scripts 833 KiB (74). Under 2 MB keeps phones on slow connections fast.

rosasubhero.png 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).

2 images are downloaded at several times the size a phone draws them, for example ac.svg at 16,250 px wide, shown at 22 px. Resized copies would save about 196 KiB.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The homepage links to 115 pages on marchesa.com and 6 external pages.

https://www.marchesa.com/policies/shipping-policy, https://www.marchesa.com/collections/marchesa-notte-1, https://www.marchesa.com/collections/marchesa-rosa-1, https://www.marchesa.com/collections/jewelry, https://www.marchesa.com/collections/fashion-jewelry and https://www.marchesa.com/collections/marchesa-fine-jewelry and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.marchesa.com/collections/marchesa-notte-1, https://www.marchesa.com/collections/marchesa-rosa-1, https://www.marchesa.com/collections/fashion-jewelry, https://www.marchesa.com/collections/marchesa-fine-jewelry, https://www.marchesa.com/collections/shop-all and https://www.marchesa.com/pages/marchesa-couture have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.marchesa.com/collections/shop-all has 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.

https://www.marchesa.com/collections/marchesa-notte-1 and https://www.marchesa.com/collections/marchesa-rosa-1 took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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

The homepage carries about 563 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 16 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.