sistersandco.com website review

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

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

18 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

8 third-party services load with your homepage (Klaviyo, Cloudflare CDN and Google Tag Manager and others), adding 1.8 MB and 1.2 s of main-thread time.

12 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

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

marsello.app costs a phone 134 ms of main-thread work and 708 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 158 KiB of CSS is downloaded but never applied on this page.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

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

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

9 KiB could be saved by minifying CSS.

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 22.2 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 5.9 MB in 370 requests on a phone: images 2.4 MB (58), scripts 2.1 MB (114) and other files 864 KiB (145). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example imgi_21_alemais-sustainable-dress-mini-kenny-mini-dress-1253 at 1,067 px wide, shown at 322 px. Resized copies would save about 500 KiB.

9 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

Rebe_NYC_L01_35MM_8950_600x600.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (121 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

12 buttons have no accessible name, so screen readers announce just “button”.

1 image has no alt text, which hurts accessibility and image search.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

24 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. (1 element).

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 466 pages on sistersandco.com and 0 external pages.

https://www.sistersandco.com/en-us/collections/all, https://www.sistersandco.com/en-us/policies/shipping-policy, https://www.sistersandco.com/policies/terms-of-service, https://www.sistersandco.com/en-us/collections/anine-bing-sale-3 and https://www.sistersandco.com/collections/womens-new-arrivals have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.sistersandco.com/policies/terms-of-service, whose canonical is https://www.sistersandco.com/en-us/policies/terms-of-service. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.sistersandco.com/en-us/collections/all, https://www.sistersandco.com/en-us/policies/shipping-policy, https://www.sistersandco.com/policies/terms-of-service, https://www.sistersandco.com/pages/buying-online, https://www.sistersandco.com/en-us/collections/anine-bing and https://www.sistersandco.com/en-us/collections/anine-bing-sale-3 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sistersandco.com/en-us/collections/coats took over 3 s to send its HTML from our server.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Unexpected token ':'”.

Chrome logged issues while loading the page (“Cookie”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 436 words of visible text.

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