santarosabrand.com website review

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

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

About 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 430 ms faster on a phone.

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

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

6 third-party services load with your homepage (Accessibe Accessibility Overlay, Klaviyo and Clarity and others), adding 656 KiB and 406 ms of main-thread time.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mobile-Single-v1.png”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.6 MB in 155 requests on a phone: images 954 KiB (15), scripts 825 KiB (63) and other files 622 KiB (68). Under 2 MB keeps phones on slow connections fast.

SRB-white_1_81ee2ecf-6885-4ab0-a4b3-519156af6a28.png 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).

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 16 characters: “Santa Rosa Brand”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 28 pages on santarosabrand.com and 4 external pages.

https://www.santarosabrand.com/collections/frontpage, https://www.santarosabrand.com/collections/all, https://www.santarosabrand.com/pages/contact, https://www.santarosabrand.com/pages/faq, https://www.santarosabrand.com/policies/terms-of-service and https://www.santarosabrand.com/policies/privacy-policy and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.santarosabrand.com/collections/frontpage, https://www.santarosabrand.com/collections/shop-mens and https://www.santarosabrand.com/collections/all 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 12 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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