lexus.co.uk website review

54 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).

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

About 558 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

About 287 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

Polyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 700 ms faster on a phone.

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

4 third-party services load with your homepage (Optanon, toyota-europe.com and hlx.page and others), adding 4.8 MB and 150 ms of main-thread time.

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

toyota.eu costs a phone 0 ms of main-thread work and 4.4 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.

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

Optanon costs a phone 148 ms of main-thread work and 363 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.

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.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 7.0 MB in 126 requests on a phone: images 4.6 MB (25), scripts 1.1 MB (52) and stylesheets 584 KiB (18). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example 2025-lexus-dx-homepage-omotensashi-1920x1080-310328 at 1,920 px wide, shown at 344 px. Resized copies would save about 782 KiB.

6 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (175 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.98 g of CO₂e: 237.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must be contained by particular parents: 11 elements on the page fail this check, rated critical by axe-core.

4 buttons have no accessible name, so screen readers announce just “button”.

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“NX​” and “LBX”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 151 pages on lexus.co.uk and 12 external pages.

https://www.lexus.co.uk/new-cars/es and https://www.lexus.co.uk/new-cars/all-new-es all use the title “Lexus ES | Feel Your Best | Lexus UK”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.lexus.co.uk/new-cars/es and https://www.lexus.co.uk/new-cars/all-new-es use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.lexus.co.uk/new-cars/nx, whose canonical is https://www.lexus.co.uk/new-cars/nx/overview. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.lexus.co.uk/pre-owned and https://www.lexus.co.uk/pre-owned/buy-a-used-car have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “TEST”.

Large scripts ship without source maps.

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 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 351 words of visible text.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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