orlebarbrown.com website review

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

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

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

8 third-party services load with your homepage (hcaptcha.com, ContentSquare and Shopify and others), adding 4.1 MB and 1.8 s of main-thread time.

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

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

hcaptcha.com costs a phone 806 ms of main-thread work and 1.0 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.

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

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

ContentSquare costs a phone 257 ms of main-thread work and 169 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.

PayPal costs a phone 220 ms of main-thread work and 392 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.

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

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

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

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

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

20 KiB could be saved by minifying JavaScript.

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

3 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop New Season Cruise'26 Collection”.

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 960 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 20.1 MB in 683 requests on a phone: media 13.6 MB (3), scripts 3.1 MB (315) and other files 1.2 MB (236). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (153 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Images must have alternative text: 11 elements on the page fail this check, rated critical by axe-core.

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

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

ARIA progressbar nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

11 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. (5 elements).

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

Your <h1> is empty.

The homepage links to 322 pages on orlebarbrown.com and 7 external pages.

https://orlebarbrown.com/en-us/collections/mens-resortwear-sartoro-striped-print, https://orlebarbrown.com/en-us/collections/mens-resortwear-forma-sora-print and https://orlebarbrown.com/en-us/collections/mens-resortwear-lunch-by-the-water are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://orlebarbrown.com/en-us/collections/new-season-swim-shorts, https://orlebarbrown.com/en-us/collections/new-season-polos, https://orlebarbrown.com/en-us/collections/new-season-shirts, https://orlebarbrown.com/en-us/collections/new-season-day-shorts-trousers and https://orlebarbrown.com/en-us/collections/new-merino-outerwear all use the title “New Season Cruise '26 | Men's Cruise Collection – ORLEBAR BROWN”. Search engines can't tell which page to show for a search, so each competes with the others.

https://orlebarbrown.com/en-us/collections/all, https://orlebarbrown.com/en-us/pages/the-ob-guarantee and https://orlebarbrown.com/en-us/collections/mens-resortwear-lunch-by-the-water have no meta description, so Google writes the search snippet from whatever text it finds.

https://orlebarbrown.com/en-us/collections/new-season-swim-shorts, https://orlebarbrown.com/en-us/collections/new-season-polos, https://orlebarbrown.com/en-us/collections/new-season-shirts, https://orlebarbrown.com/en-us/collections/new-season-day-shorts-trousers and https://orlebarbrown.com/en-us/collections/new-merino-outerwear use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://orlebarbrown.com/pages/accessibility-statement, whose canonical is https://orlebarbrown.com/en-us/pages/accessibility-statement. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://orlebarbrown.com/pages/accessibility-statement, https://orlebarbrown.com/en-us/collections/all, https://orlebarbrown.com/en-us/collections/mens-resortwear-merino-outerwear, https://orlebarbrown.com/en-us/pages/delivery-and-returns, https://orlebarbrown.com/en-us/pages/the-ob-guarantee and https://orlebarbrown.com/en-us/collections/new-season-swim-shorts and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://orlebarbrown.com/en-us#.

28 of 79 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 (“The Protected Audience API is deprecated and will be removed in a future release.”).

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 484 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 33 cookies (measured from a US location before any click).

Loading the homepage contacts 57 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.