breitling.com website review

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

Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

20 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

8 third-party services load with your homepage (Google Tag Manager, Optanon and Noibu and others), adding 1.5 MB and 1.1 s of main-thread time.

11 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google Tag Manager costs a phone 949 ms of main-thread work and 1,017 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.

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

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

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

26 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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 could be saved by minifying CSS.

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.

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

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

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your homepage downloads 4.9 MB in 203 requests on a phone: scripts 2.6 MB (66), images 1.8 MB (43) and other files 212 KiB (86). Under 2 MB keeps phones on slow connections fast.

hp-slider-top-time-story-mobile.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).

1 image is downloaded at several times the size a phone draws it, for example Football_Car_-_HP_Local_Banner_-_1165x915.jpg at 1,165 px wide, shown at 358 px. Resized copies would save about 25 KiB.

1 image (49 KiB) is 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.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (24 elements).

There are 3 <h1> headlines (“Navitimer B09: signed with the Twin Jet”, “Navitimer B01” and “Top Time”). One clear main headline is easier for people and search engines.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 279 pages on breitling.com and 19 external pages.

/us-en and / all use the title “Swiss Luxury Watches of Style, Purpose & Action | Breitling”. Search engines can't tell which page to show for a search, so each competes with the others.

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

/us-en/terms-and-conditions, /us-en/watches, /us-en/collections, /us-en/collections/superocean-heritage, /us-en/collections/avenger and /us-en/collections/classic-avi and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=26014521&tm=gtm002&Ver=2&mid=326b45a6-9987-4490-b03e-54e98f4cebee&bo=3&sid=980a42b0d58111f1b860333170b5b7e1&vid=980a51d0d58111f1b564cbe708cc790e&vids=0&msclkid=N&pi=91.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

2 images are served at too low a resolution for sharp phone screens.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

Opening https://breitling.com goes through 2 redirects before the homepage loads.

1 link go through two or more redirects, for example https://instagram.com/breitling.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

Social proof on the homepage: 25 trust badges. 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.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 643 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, Meta Pixel and Microsoft Ads 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 31 cookies (measured from a US location before any click).

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