diepresse.com website review

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

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

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

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

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

6 third-party services load with your homepage (Cloudflare CDN, piano and Smart AdServer and others), adding 1.1 MB and 845 ms of main-thread time.

3 images could be 306 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

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

piano costs a phone 359 ms of main-thread work and 718 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.

Cloudflare CDN costs a phone 362 ms of main-thread work and 203 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.

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ilija Srdanovic, Anführer der Studentenliste, bejubelt mit …”.

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

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

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

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

1 image 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 127 ms to 118 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.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 169 requests on a phone: scripts 1.4 MB (85), images 954 KiB (35) and fonts 438 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (39 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 0.90 g of CO₂e: 108.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 53 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: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 27 characters: “Nachrichten – DiePresse.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 260 pages on diepresse.com and 15 external pages.

Your robots.txt shuts out ChatGPT (ChatGPT-User) and 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.

The HTML your server sends has 1,511 of the 3,838 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

robots.txt blocks GPTBot, ClaudeBot, 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.

/suche is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/suche, /epaper and /newsletter use the same meta description. A description written for each page earns more clicks.

/suche, /epaper and /newsletter have no <h1> headline, so visitors and search engines get no clear main topic.

/player and /panorama took over 3 s to send their HTML from our server.

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

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

1 link to other sites is dead, for example https://bsky.app/profile/diepressecom.bsky.social (404).

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://www.microsoft.com/de-de/edge.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

Your security.txt expired on 2026-04-23, so researchers may not trust its contact details.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

diepresse.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

diepresse.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

diepresse.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 3,838 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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