Website review, no card needed
abendblatt.de website review
Visit site (opens in a new tab)Reviewed 18 October 202631 issues · 81 checks
This review found 31 issues worth fixing on abendblatt.de, 11 of them high impact, across 81 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.1 s |
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 146 ms |
| May 2, 2026 | 158 ms |
| May 9, 2026 | 165 ms |
| May 16, 2026 | 177 ms |
| May 23, 2026 | 180 ms |
| May 30, 2026 | 181 ms |
| Jun 6, 2026 | 176 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 167 ms |
| Jun 27, 2026 | 152 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 151 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 147 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 165 ms |
| Sep 19, 2026 | 174 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 183 ms |
| Oct 10, 2026 | 186 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.1 s
1.7 s
2.2 s
2.8 s
3.3 s
3.9 s
4.4 s
Speed
Improve image delivery
2.0 s · 1.7 MB14 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Render-blocking requests
1.0 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
5,781 HTML elements
The page has 5,781 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 67
67/100Your mobile performance score is 67 (desktop: 87). Pages that score under 90 lose visitors before the first paint.
4 third-party services on the page
4 third-party services load with your homepage (consentmanager.net, piano.io and funkedigital.de and others), adding 2.4 MB and 572 ms of main-thread time.
consentmanager.net adds 375 ms
375 msconsentmanager.net costs a phone 375 ms of main-thread work and 142 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.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
254 KiBAbout 254 KiB of JavaScript is downloaded but never used on this page.
funkemedien.de adds 0 ms
0 msfunkemedien.de costs a phone 0 ms of main-thread work and 2.0 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 240 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
206 KiB4 files are served with short cache lifetimes, so returning visitors download them again (206 KiB).
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.1 s
5.1 sYour 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 “Schulunterricht”.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 146 ms to 186 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 356 ms
356 msScripts block taps and scrolling for 356 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 141 ms
141 msReal visitors wait 141 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 386 ms
386 msReal visitors wait 386 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.7 MB in 80 requests
2.7 MBYour homepage downloads 2.7 MB in 80 requests on a phone: images 1.9 MB (21), scripts 535 KiB (44) and fonts 153 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (158 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 91.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 164 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
417 internal links, 63 external
The homepage links to 417 pages on abendblatt.de and 63 external pages.
5 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Nachrichten aus Hamburg und der Welt. News aus Politik, Wirtschaft, Sport und Kultur. Alles, was echte Hamburger wissen…”.
Title: 59 characters
Your title is a healthy 59 characters: “Nachrichten aus Hamburg und der Welt - Hamburger Abendblatt”.
Canonical URL set
The canonical URL is https://www.abendblatt.de/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.abendblatt.de/sitemaps/news.xml.
AI search readiness
robots.txt blocks 1 AI answer engine crawler
1 of 6Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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.
No llms.txt
There is no https://www.abendblatt.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.
Opted out of AI training for 5 crawlers
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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (4,775 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.abendblatt.de/service/kalender has no <title>, so Google invents the link text in results.
1 page without a meta description
https://www.abendblatt.de/service/kalender has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.abendblatt.de/service/gewinnspiele and https://www.abendblatt.de/service/kalender have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.abendblatt.de/service/kalender 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.
1 page slow to respond
https://www.abendblatt.de/service/kalender took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
41 of 51 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 2,967 words of copy
The homepage carries about 2,967 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Abendblatt-Shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: consentmanager
A consent management tool (consentmanager) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at abendblatt.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
Company
- Founded
- 1948
- Headquarters
- Hamburg
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on abendblatt.de, including 15 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.