louisecarter-official.com website review

43 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.1 s faster on a phone.

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

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

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

About 1.3 MB of JavaScript is downloaded but never used on this page.

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

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

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

alia-prod.com costs a phone 381 ms of main-thread work and 491 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 costs a phone 191 ms of main-thread work and 502 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,068 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 75 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.

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

61 KiB could be saved by minifying JavaScript.

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

6 KiB could be saved by minifying CSS.

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.

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

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

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

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

Your homepage downloads 9.3 MB in 566 requests on a phone: scripts 3.4 MB (159), images 3.3 MB (48) and other files 2.1 MB (333). Under 2 MB keeps phones on slow connections fast.

14 images are downloaded at several times the size a phone draws them, for example lc-home-hero-mobile-bundle.jpg at 1,350 px wide, shown at 390 px. Resized copies would save about 784 KiB.

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

9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 21 characters: “Louise Carter Jewelry”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Louise Carter” and “Louise Carter”). One clear main headline is easier for people and search engines.

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

The homepage links to 82 pages on louisecarter-official.com and 2 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://louisecarter-official.com/collections/7-for-85-waterproof-bundle is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://louisecarter-official.com/collections/7-for-85-waterproof-bundle has no meta description, so Google writes the search snippet from whatever text it finds.

https://louisecarter-official.com/collections/hand-chains, https://louisecarter-official.com/collections/anklets and https://louisecarter-official.com/collections/all-products use the same meta description. A description written for each page earns more clicks.

https://louisecarter-official.com/collections/7-for-85-waterproof-bundle has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

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

6 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 ()”.

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

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 5 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 42 cookies, 1 of them by other companies (measured from a US location before any click).

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