curatorsf.com website review

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

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

8 images could be 269 KiB 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.

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

8 third-party services load with your homepage (alia-prod.com, cloudfront.net and Klaviyo and others), adding 1.4 MB and 708 ms of main-thread time.

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

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

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

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

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

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

cloudfront.net costs a phone 145 ms of main-thread work and 299 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.

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

15 KiB could be saved by minifying JavaScript.

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.

3 KiB could be saved by minifying CSS.

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

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

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

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

3 images 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' tap response (inp) went from 154 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.6 MB in 294 requests on a phone: scripts 1.9 MB (99), other files 972 KiB (167) and images 479 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example curator_logo_black_thin_1600x234_c554aca6-9300-4250-b1ef-351 at 1,600 px wide, shown at 220 px. Resized copies would save about 43 KiB.

1 image further down the page (51 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 1.02 g of CO₂e: 122.7 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.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h3), 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 meta description is 309 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 71 pages on curatorsf.com and 7 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.

The HTML your server sends has 329 of the 1,030 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

/collections/tops has no meta description, so Google writes the search snippet from whatever text it finds.

/tools/returns, /collections/dresses, /collections/bottoms and /collections/outerwear use the same meta description. A description written for each page earns more clicks.

/tools/returns has no <h1> headline, so visitors and search engines get no clear main topic.

/tools/returns, /collections/clothing, /collections/tops, /collections/dresses, /collections/bottoms and /collections/outerwear have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=52004918&Ver=2&mid=9a61d9a5-8aa3-4bc5-ab09-cae8da2ee57c&bo=1&sid=d969c910d8b211f1a4315b1058f82063&vid=d96a0b40d8b211f1b5c95dd3380c8019&vids=1&msclkid=N&pi=918639831&lg.

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

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

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://www.curatorsf.com/customer_authentication/redirect?locale=en&region_country=US.

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.

curatorsf.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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 1,030 words of visible text.

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

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 3 mores (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 32 cookies (measured from a US location before any click).

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