cherryla.com website review

About 133 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

About 166 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 880 ms faster on a phone.

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

8 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 742 KiB and 567 ms of main-thread time.

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

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

Klaviyo costs a phone 170 ms of main-thread work and 312 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.

9 KiB could be saved by minifying CSS.

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

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

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.

Your largest element takes 19.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TWOSTAR-CREATIVE_SHOTS_757762Green_752010c1-2abe-4358-b601-…”.

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

Visually, the page fills in at 7.3 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 80 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 26.6 MB in 256 requests on a phone: media 20.3 MB (2), images 4.1 MB (39) and scripts 947 KiB (84). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example ANAWALT_opt_4_4f51cd82-bb89-4756-a626-18451cc30e73.png at 1,782 px wide, shown at 320 px. Resized copies would save about 1.6 MB.

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your <h1> is empty.

The homepage links to 103 pages on cherryla.com and 2 external pages.

/collections/shop-all, /collections/new-arrivals, /collections/core-classics, /collections/all-tops, /collections/tees-long-sleeves and /collections/crewnecks and 9 others use the same meta description. A description written for each page earns more clicks.

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

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://cherryla.com/account.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

cherryla.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

cherryla.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

DMARC is set to p=none, so mail pretending to be cherryla.com is still delivered. Add a report address, check the reports, then move to quarantine.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 include:servers.mcsv.net ?all”.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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