brisara.com website review

Shopify costs a phone 1.2 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

5 third-party services load with your homepage (Shopify, shop.app and nfcube.com and others), adding 1.1 MB and 1.3 s of main-thread time.

9 images could be 420 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

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

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

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

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

About 23 KiB of CSS is downloaded but never applied on this page.

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

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.

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Americana”.

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

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

Visually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 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 3.1 MB in 344 requests on a phone: scripts 1,014 KiB (137), other files 906 KiB (159) and images 896 KiB (11). Under 2 MB keeps phones on slow connections fast.

IMG_9475.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).

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 7 characters: “Brisara”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 50 pages on brisara.com and 3 external pages.

https://brisara.com/collections/dresses-copy, https://brisara.com/collections/tropical-chinoiserie, https://brisara.com/collections/blue-white-amour, https://brisara.com/collections/dresses-1, https://brisara.com/collections/tops-1 and https://brisara.com/collections/caftans-1 and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://brisara.com/products/sara-dress-leopard-party-navy and https://brisara.com/products/sara-dress-leopard-party-1 use the same meta description. A description written for each page earns more clicks.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) ReferenceError: item is not defined”.

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

The homepage has only about 137 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.

Opening the homepage sets 6 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.