nudebarre.com website review

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

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

17 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 170 ms faster on a phone.

8 third-party services load with your homepage (rlets.com, Google Tag Manager and Facebook and others), adding 2.0 MB and 890 ms of main-thread time.

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

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

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

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

rlets.com costs a phone 277 ms of main-thread work and 50 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.

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

Shopify costs a phone 63 ms of main-thread work and 764 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.

Polyfills for old browsers add 89 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.

2 KiB could be saved by minifying JavaScript.

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.

For real visitors the layout shifts by 0.69 (75th percentile). Good is under 0.1.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 170 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.8 MB in 292 requests on a phone: images 2.7 MB (37), scripts 2.6 MB (116) and other files 700 KiB (112). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.

2 images (1.1 MB) are 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.

Swatchbook_w_12shades_shorter_d21287d0-d386-447a-8547-2657f9 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 1.94 g of CO₂e: 232.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 391 pages on nudebarre.com and 14 external pages.

Your Organization JSON-LD is missing logo, 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://nudebarre.com/collections/markdowns, https://nudebarre.com/collections/best-sellers-1, https://nudebarre.com/pages/wedding-edit and https://nudebarre.com/pages/time-of-shade have no meta description, so Google writes the search snippet from whatever text it finds.

https://nudebarre.com/collections/markdowns, https://nudebarre.com/collections/best-sellers-1, https://nudebarre.com/collections, https://nudebarre.com/pages/wedding-edit, https://nudebarre.com/pages/time-of-shade and https://nudebarre.com/collections/morning-shades and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=0ffcb796-bc3f-45bc-8063-32aad7e38fe5&referrer=&landingpage=https%3A%2F%2Fnudebarre.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017_.

10 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Large scripts ship without source maps.

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

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 carries about 393 words of visible text.

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