lidl.com website review

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

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

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

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

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

25 images could be 13.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

2 third-party services load with your homepage (Optanon and leaflets.schwarz), adding 240 KiB and 95 ms of main-thread time.

1 long task block the main thread while loading, the longest for 55 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).

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

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

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

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

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

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

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

The layout shifts by 0.155 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 23.7 MB in 144 requests on a phone: images 22.0 MB (55), scripts 730 KiB (43) and fonts 464 KiB (6). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example AW41_MarketingStageTeasers_LidlPlusDeals-Mobile-2488880.jpg at 10,000 px wide, shown at 853 px. Resized copies would save about 8.0 MB.

3 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.

16 images (8.6 MB) are 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.

AW41_MarketingStageTeasers_LidlPlusDeals-Mobile-2488880.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 further down the page (29 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 6.71 g of CO₂e: 805.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your meta description is only 39 characters: “Lidl US | Grocery Store | More to Value”. 70 to 160 characters is enough to sell the click.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 162 pages on lidl.com and 12 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

/mla has no <title>, so Google invents the link text in results.

/c/offers-leaflets/s10092873, /mla, /c/lidl-plus/s10093874, /c/food-wine/s10068374, /c/kitchen-household/s10068166 and /c/diy-garden/s10068222 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/mla, /c/lidl-plus/s10093874, /c/taste-of-the-world/s10093879, /c/store-finder/s10089075, /c/leave-your-review/s10095204 and /c/about-us/s10089074 have no <h1> headline, so visitors and search engines get no clear main topic.

/mla has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

Large scripts ship without source maps.

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.

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

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

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