brilly.co website review

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and 9gtb.com and others), adding 1.7 MB and 292 ms of main-thread time.

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

Shopify costs a phone 72 ms of main-thread work and 1.2 MB 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.

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

40 KiB could be saved by minifying JavaScript.

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

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

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

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

6 KiB JavaScript is shipped twice across bundles.

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.

4 KiB could be saved by minifying CSS.

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

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

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

10 images have no width and height attributes, so the layout jumps as each one loads.

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 6.1 MB in 299 requests on a phone: media 3.1 MB (2), images 1.1 MB (51) and other files 877 KiB (136). Under 2 MB keeps phones on slow connections fast.

Hero-Mobile-Base_Layer.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).

4 images further down the page (156 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

15 tap targets are too small or too close together to hit reliably with a finger.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

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

There are 4 <h1> headlines (“”, “You deserve a bra that keeps up with you.” and “Brilly Essential Bra”). One clear main headline is easier for people and search engines.

Structured data found (Organization, ProductGroup and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

The homepage links to 28 pages on brilly.co and 0 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://brilly.co/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://brilly.co/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://brilly.co/pages/ads, https://brilly.co/customer_authentication/redirect, https://brilly.co/pages/how-to-wear, https://brilly.co/collections/all, https://brilly.co/pages/science and https://brilly.co/policies/privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://brilly.co/customer_authentication/redirect, https://brilly.co/pages/how-to-wear, https://brilly.co/pages/wholesale-and-partnerships and https://brilly.co/pages/accessibility-statement have no <h1> headline, so visitors and search engines get no clear main topic.

https://brilly.co/products/bra took over 3 s to send its HTML from our server.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

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

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://brilly.co/cdn/shop/t/3/assets/swiper-bundle.min.css?v=6007' because its MIME type …”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,149 words of visible text.

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