lexus.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 3.5 s

  3.5 s

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

• Real-user INP: 266 ms

  266 ms

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

• Largest content (LCP) got 32% slower for real visitors

  +32%

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

• Real-user FCP: 3.0 s

  3.0 s

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

• Tap response (INP) got 14% slower for real visitors

  +14%

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

• Page weight: 3.3 MB

  3.3 MB

  Your homepage downloads 3.3 MB on a phone, 1.1 MB of it images (34%). Under 2 MB keeps phones on slow connections fast.

• 5 images below the first screen load straight away

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

  Elements (5)

• About 0.9 g of CO₂ per visit

  0.94 g

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

• 6 buttons without a name

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

  Elements (3)

• Images must have alternative text (1 element)

  Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 2 tap targets too small

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

  Elements (2)

• Links must have discernible text (1 element)

  Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• All page content should be contained by landmarks (31 elements)

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

  Elements (3)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 1 form field without a label

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

• No H1 headline

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

• Title is short (26 characters)

  Your title is only 26 characters: “Lexus | Experience Amazing”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

• No X (Twitter) card tag

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

• Most text only appears after JavaScript runs

  0%

  A phone browser shows 651 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

• No Organization structured data

  There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

• No calls to action

  We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• No analytics detected

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

• No direct contact details

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

• No form on the homepage

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

• No risk reducer

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

• About 651 words of copy

  The homepage carries about 651 words of visible text.

• 3 cookies set on arrival

  3

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

• No consent tool detected

  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.

• 4 other companies contacted

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