Website review, no card needed

nzz.ch logo

nzz.ch website review

Visit site (opens in a new tab)Reviewed 3 November 202630 issues · 83 checks

This review found 30 issues worth fixing on nzz.ch, 15 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.4 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
140 ms101 msMay 16Oct 31105 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026108 ms
May 30, 2026107 ms
Jun 6, 2026108 ms
Jun 13, 2026111 ms
Jun 20, 2026122 ms
Jun 27, 2026129 ms
Jul 4, 2026131 ms
Jul 11, 2026135 ms
Jul 18, 2026130 ms
Jul 25, 2026125 ms
Aug 1, 2026124 ms
Aug 8, 2026122 ms
Aug 15, 2026121 ms
Aug 22, 2026119 ms
Aug 29, 2026118 ms
Sep 5, 2026119 ms
Sep 12, 2026117 ms
Sep 19, 2026119 ms
Sep 26, 2026117 ms
Oct 3, 2026114 ms
Oct 10, 2026114 ms
Oct 17, 2026110 ms
Oct 24, 2026106 ms
Oct 31, 2026105 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

Full-page screenshot of nzz.ch (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nzz.ch at 0.4 s0.4 s
  2. nzz.ch at 0.9 s0.9 s
  3. nzz.ch at 1.3 s1.3 s
  4. nzz.ch at 1.7 s1.7 s
  5. nzz.ch at 2.2 s2.2 s
  6. nzz.ch at 2.6 s2.6 s
  7. nzz.ch at 3.0 s3.0 s
  8. nzz.ch at 3.5 s3.5 s

Speed

11 to fix36
  • Use efficient cache lifetimes

    4.3 s · 10.6 MB

    47 files are served with short cache lifetimes, so returning visitors download them again (10.6 MB).

  • Reduce unused JavaScript

    3.2 s · 895 KiB

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 5.1 s

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

  • 4,119 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (static-nzz.ch, consentmanager.net and adnz.co and others), adding 13.3 MB and 1.8 s of main-thread time.

  • LongTail Ad Solutions adds 73 ms

    73 ms

    LongTail Ad Solutions costs a phone 73 ms of main-thread work and 11.3 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.

  • static-nzz.ch adds 967 ms

    967 ms

    static-nzz.ch costs a phone 967 ms of main-thread work and 971 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.

  • 17 long tasks on the main thread

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

  • consentmanager.net adds 263 ms

    263 ms

    consentmanager.net costs a phone 263 ms of main-thread work and 189 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.

  • adnz.co adds 138 ms

    138 ms

    adnz.co costs a phone 138 ms of main-thread work and 309 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.

  • Reduce unused CSS

    180 ms · 44 KiB

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

  • Legacy JavaScript

    150 ms · 31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    150 ms

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

  • Improve image delivery

    90 KiB

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

  • 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 109 ms

    109 ms

    Your server sent the HTML in 109 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 0.31

    0.31

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

  • Largest Contentful Paint: 16.8 s

    16.8 s

    Your largest element takes 16.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Die Einsatzkräfte erleben erneut ein Debakel. Die grüne Sic…”.

  • Time to Interactive: 23.3 s

    23.3 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

5 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 120 ms

    120 ms

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

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 355 ms

    355 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 14.4 MB in 165 requests

    14.4 MB

    Your homepage downloads 14.4 MB in 165 requests on a phone: media 10.6 MB (12), scripts 2.1 MB (66) and images 823 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • About 4.1 g of CO₂ per visit

    4.09 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9997
  • All page content should be contained by landmarks (345 elements)

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings should not be empty (4 elements)

    Headings should not be empty: 4 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. (49 elements).

2 checks passed
  • Every image has alt text

    All 69 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

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

  • 196 internal links, 99 external

    The homepage links to 196 pages on nzz.ch and 99 external pages.

7 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “NZZ Nachrichten, Hintergründe, Meinungen aus der Schweiz, International, Sport, Digital, Wirtschaft, Auto & mehr. Fundi…”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “NZZ – Neue Zürcher Zeitung | Aktuelle News, Hintergründe & mehr”.

  • Canonical URL set

    The canonical URL is https://www.nzz.ch/.

  • Structured data in place

    Structured data found: NewsMediaOrganization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.nzz.ch/sitemap.xml.

AI search readiness

1 to fix65
  • robots.txt blocks 4 AI answer engine crawlers

    4 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), 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.

  • No llms.txt

    There is no https://www.nzz.ch/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.

2 checks passed
  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,839 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.nzz.ch/briefing, whose canonical is https://www.nzz.ch/briefing/briefing-am-montagabend-ld.10052135. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 4 JavaScript errors while loading

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

  • 1 low-resolution image

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

2 checks passed
  • Tap targets are thumb-sized

    52 of 57 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 3,142 words of copy

    The homepage carries about 3,142 words of visible text.

1 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop”.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Criteo, Google Ads and The Trade Desk (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

  • 16 cookies set on arrival

    16

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

  • 38 other companies contacted

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

1 checks passed
  • Consent tool: consentmanager

    A consent management tool (consentmanager) loads with the page.

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 nzz.ch, 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
Hosting
Cloudflare

Company

Founded
1780
Headquarters
Zurich

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on nzz.ch, including 18 speed issues, 1 SEO issue and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25