judithandcharles.com website review

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

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

4 images could be 255 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

8 third-party services load with your homepage (ContentSquare, Shopify and emotivecdn.io and others), adding 1.4 MB and 844 ms of main-thread time.

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

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

67 KiB could be saved by minifying JavaScript.

ContentSquare costs a phone 354 ms of main-thread work and 185 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.

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

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

Shopify costs a phone 166 ms of main-thread work and 350 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.

emotivecdn.io costs a phone 114 ms of main-thread work and 384 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.

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

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

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.

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

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

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

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

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

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' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 301 requests on a phone: scripts 1.6 MB (97), other files 1.0 MB (147) and images 572 KiB (15). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (45 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

2 elements hidden from screen readers can still receive keyboard focus.

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

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

Headings skip levels (h2 → h5), 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 16 characters: “Judith & Charles”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 73 pages on judithandcharles.com and 3 external pages.

https://www.judithandcharles.com/en-us/pages/easy-care-techno and https://www.judithandcharles.com/en-us/collections/easy-care all use the title “The Easy Care Edit – Judith & Charles”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.judithandcharles.com/en-us/pages/easy-care-techno has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.judithandcharles.com/en-us/pages/easy-care-techno has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

The homepage has only about 144 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, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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