sunnamusk.com website review

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

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

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

ZenDesk costs a phone 371 ms of main-thread work and 431 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 288 ms of main-thread work and 797 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.

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

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

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

Klaviyo costs a phone 151 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.

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

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

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

19 KiB JavaScript is shipped twice across bundles.

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.

3 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 203 ms to 238 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.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.4 MB in 421 requests on a phone: scripts 3.0 MB (172), images 2.9 MB (69) and other files 992 KiB (146). Under 2 MB keeps phones on slow connections fast.

Gift_Sets_Offers_Online_NovP_Media_1080x1920_copy_3.jpg 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).

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

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

2 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 on the page fails this check, rated serious by axe-core.

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

15 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 (h3 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 312 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/sunnamusk-logo.svg")”.

The homepage links to 181 pages on sunnamusk.com and 20 external pages.

/collections/exclusive-collection has no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all, /collections and /collections/room-spray use the same meta description. A description written for each page earns more clicks.

/pages/sunnamusksociety, /collections and /collections/persona-collection have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR”.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: “7,000+ REVIEWS”. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 15 fields (0 required). Every extra field lowers completion.

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 458 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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 27 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 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.