judithmarch.com website review

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

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

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

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

8 third-party services load with your homepage (recart.com, POWr and Clarity and others), adding 1.1 MB and 719 ms of main-thread time.

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

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

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

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

azurefd.net costs a phone 58 ms of main-thread work and 321 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.

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

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

About 42 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

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

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

The first text or image appears after 1.8 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-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.7 MB in 262 requests on a phone: images 1.3 MB (27), scripts 1.2 MB (120) and other files 888 KiB (100). Under 2 MB keeps phones on slow connections fast.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Your title is 67 characters, so Google will cut it off around 60: “Judith March - Southern charm meets bohemian vibe of the West Coast”.

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

Your meta description is only 56 characters: “Southern charm meets the bohemian vibe of the West Coast”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“” and “Find Your Best Fit”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 206 pages on judithmarch.com and 13 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://www.judithmarch.com/collections/new-arrivals, https://www.judithmarch.com/collections/halloween-2026, https://www.judithmarch.com/collections/halloween-hats, https://www.judithmarch.com/collections/halloween-pullovers, https://www.judithmarch.com/collections/halloween-mini-kids and https://www.judithmarch.com/collections/halloween-tees-tanks and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.judithmarch.com/collections/thanksgiving-2026 and https://www.judithmarch.com/collections/christmas-2026 took over 3 s to send their HTML from our server.

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

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

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

Your longest form asks for 9 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.

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

The homepage carries about 284 words of visible text.

Before a visitor clicks anything, the page loads Klaviyo, Microsoft Clarity and Pinterest Tag (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 17 cookies, 1 of them by other companies (measured from a US location before any click).

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