litens.com website review

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

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

Your mobile performance score is 56 (desktop: 85). Pages that score under 90 lose visitors before the first paint.

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

6 third-party services load with your homepage (tagembed.com, Google Tag Manager and Google Analytics and others), adding 469 KiB and 332 ms of main-thread time.

12 KiB could be saved by minifying JavaScript.

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

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

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

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

17 KiB could be saved by minifying CSS.

Desktop scores 85 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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 first text or image appears after 10.4 s on a phone. Good is under 1.8 s.

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

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

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

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

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

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

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

Your homepage downloads 27.6 MB in 128 requests on a phone: media 25.3 MB (7), fonts 1.4 MB (8) and scripts 568 KiB (61). Under 2 MB keeps phones on slow connections fast.

vidoe-poster2-mobile.webp 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 7.82 g of CO₂e: 938.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

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

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

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

Your title is only 23 characters: “Litens Automotive Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 82 pages on litens.com and 8 external pages.

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.

There is no https://www.litens.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

/, https://www.litens.com/fr/page-daccueil, https://www.litens.com/pt/home-page-portugues, https://www.litens.com/ro/home-page-romana, https://www.litens.com/de/home-page-deutsch and https://www.litens.com/zh/home-page-chinese and 2 others all use the title “Litens Automotive Group”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.litens.com/who-we-are, https://www.litens.com/who-we-are/diversity-inclusion, https://www.litens.com/who-we-are/worldwide, https://www.litens.com/who-we-are/sustainability, https://www.litens.com/policies and https://www.litens.com/who-we-are/quality-awards have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.litens.com/fr/page-daccueil, https://www.litens.com/ja/home-page-japanese and https://www.litens.com/ko/home-page-3 use the same meta description. A description written for each page earns more clicks.

https://www.litens.com/who-we-are/worldwide has no <h1> headline, so visitors and search engines get no clear main topic.

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

5 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 image is served at too low a resolution for sharp phone screens.

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

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

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