welt.de website review

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

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

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

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

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

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

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

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

4 third-party services load with your homepage (vividbucket.com, ringieraxelspringer.tech and asadcdn.com and others), adding 151 KiB and 95 ms of main-thread time.

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

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

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 layout shifts by 0.964 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Kein alternativer Text für dieses Bild vorhanden”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 185 ms to 202 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 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

ARIA attributes must conform to valid values: 8 elements on the page fail this check, rated critical by axe-core.

34 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

The homepage links to 443 pages on welt.de and 42 external pages.

Your robots.txt shuts out Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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.welt.de/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 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.

https://www.welt.de/meinewelt/newsletter has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.welt.de/newsticker, https://www.welt.de/apps, https://www.welt.de/podcasts, https://www.welt.de/meinewelt/newsletter, https://www.welt.de/spiele/article8000221/Testen-Sie-Ihr-Wissen-Kreuzwortraetsel-Taeglich-neue-Fragen.html and https://www.welt.de/spiele/article1336655/Sudoku-online-Spielen-Sie-kostenlos-Sudoku.html and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.welt.de/newsticker, https://www.welt.de/apps, https://www.welt.de/podcasts and https://www.welt.de/mediathek have 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 199 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “When fetching the accounts endpoint, a 401 HTTP response code was received.”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

Opening the homepage sets 6 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.