annazuckerman.com website review

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

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 658 KiB and 358 ms of main-thread time.

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

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

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

34 KiB JavaScript is shipped twice across bundles.

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

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.

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

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

The layout shifts by 0.437 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 280 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 145 ms to 174 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 7.2 MB in 312 requests on a phone: media 3.2 MB (2), images 2.1 MB (80) and scripts 812 KiB (80). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example shopify_pic.jpg at 1,920 px wide, shown at 360 px. Resized copies would save about 105 KiB.

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

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: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Your <h1> is empty.

The homepage links to 682 pages on annazuckerman.com and 22 external pages.

https://annazuckerman.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://annazuckerman.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://annazuckerman.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://annazuckerman.com/collections/thalia-x-anna-zuckerman and https://annazuckerman.com/collections/just-like-diamonds use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://annazuckerman.com/products/bethenny-frankel-x-anna-zuckerman-just-like-diamonds-4-carat-studs, whose canonical is https://annazuckerman.com/products/bethenny-frankel-x-anna-zuckerman-just-like-diamonds-studs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://annazuckerman.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 3,365 words of visible text.

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