charlottesimone.com website review

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

10 images could be 5.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

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

Klaviyo costs a phone 119 ms of main-thread work and 381 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 third-party services load with your homepage (Klaviyo, Klarna and Shopify and others), adding 847 KiB and 265 ms of main-thread time.

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

2 KiB could be saved by minifying JavaScript.

2 long tasks block the main thread while loading, the longest for 92 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).

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

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

Your largest element takes 14.1 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 14.3 s. Good is under 3.8 s.

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

The first text or image appears after 4.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-11-07, real Chrome visitors' tap response (inp) went from 108 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.7 MB in 254 requests on a phone: images 5.7 MB (16), scripts 963 KiB (90) and other files 790 KiB (100). Under 2 MB keeps phones on slow connections fast.

1 image (183 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.20 g of CO₂e: 263.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 34 pages on charlottesimone.com and 10 external pages.

https://charlottesimone.com/collections/all and https://charlottesimone.com/blogs/press have no meta description, so Google writes the search snippet from whatever text it finds.

https://charlottesimone.com/collections/all and https://charlottesimone.com/pages/about have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://charlottesimone.com/cdn/shop/t/108/assets/ins-img_300x.jpg?v=18809.

4 errors were logged to the browser console while the page loaded, for example “instafeedApp is not defined”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

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

The page uses urgency cues (a countdown or limited-time wording).

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 18 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.