Programmable

Website review, no card needed

psychothriller.de logo

psychothriller.de website review

Visit site (opens in a new tab)Reviewed 13 November 202632 issues · 82 checks

This review found 32 issues worth fixing on psychothriller.de, 9 of them high impact, across 82 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

Site score

82B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.9 s1.6 sAug 1Nov 71.9 s
Show as table
DateReal-visitor load time (LCP)
Aug 1, 20261.6 s
Aug 15, 20261.8 s
Oct 31, 20261.9 s
Nov 7, 20261.9 s

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

ivarleonmenger.de (opens in a new tab)
Full-page screenshot of psychothriller.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. psychothriller.de at 1.4 s1.4 s
  2. psychothriller.de at 2.7 s2.7 s
  3. psychothriller.de at 4.1 s4.1 s
  4. psychothriller.de at 5.4 s5.4 s
  5. psychothriller.de at 6.8 s6.8 s
  6. psychothriller.de at 8.1 s8.1 s
  7. psychothriller.de at 9.5 s9.5 s
  8. psychothriller.de at 10.8 s10.8 s

Speed

7 to fix57

  • Use efficient cache lifetimes

    4.3 s · 1.9 MB

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

  • Render-blocking requests

    3.3 s

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

  • Improve image delivery

    1.9 s · 441 KiB

    9 images could be 441 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Reduce unused CSS

    1.2 s · 220 KiB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 236 KiB

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

  • Google Tag Manager adds 125 ms

    125 ms

    Google Tag Manager costs a phone 125 ms of main-thread work and 308 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.

  • Font display

    250 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, jit.si and Google Analytics), adding 342 KiB and 137 ms of main-thread time.

  • Minify CSS

    150 ms · 11 KiB

    11 KiB could be saved by minifying CSS.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 84 ms. During a long task the page ignores taps.

  • Minify JavaScript

    23 KiB

    23 KiB could be saved by minifying JavaScript.

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

2 checks passed

  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 281 ms of it running JavaScript. That is comfortably low.

  • Server response: 122 ms

    122 ms

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

Core Web Vitals

9 to fix100

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

  • Speed Index: 15.8 s

    15.8 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

    Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (7.9 s).

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Cumulative Layout Shift: 0.182

    0.182

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

  • Time to Interactive: 5.6 s

    5.6 s

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

  • 21 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

3 checks passed

  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 34 ms

    34 ms

    Scripts block the page for only 34 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix78

  • Page weight: 2.3 MB in 93 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 93 requests on a phone: images 1.0 MB (26), scripts 602 KiB (28) and fonts 324 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 14 images below the first screen load straight away

    14 images further down the page (398 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images in older formats

    3 images (470 KiB) 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.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

1 checks passed

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 9194

  • 3 text elements with low contrast

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

  • All page content should be contained by landmarks (2 elements)

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo 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 contentinfo landmark (1 element)

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Headings skip levels

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

  • 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 26 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 7 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8590

  • 8 H1 headlines

    There are 8 <h1> headlines (“„Der Tower liest sich wie ein Sturz aus dem 32. S…”, “„Der Kerl ist wirklich eine Bereicherung für den …” and “„Ivar Leon Menger hat ein selten schönes Stück Sp…”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • 26 internal links, 35 external

    The homepage links to 26 pages on psychothriller.de and 35 external pages.

6 checks passed

  • Meta description: 127 characters

    Your meta description is 127 characters: “Entdecken Sie die aktuelle Thriller-Neuerscheinung des deutschen Thriller-Autors Ivar Leon Menger auf der offiziellen W…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Spiegel-Bestsellerautor Ivar Leon Menger – Offizielle Webseite”.

  • Canonical URL set

    The canonical URL is https://ivarleonmenger.de/.

  • Structured data in place

    Structured data found: BreadcrumbList, Event, Organization, Person and WebPage.

  • 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.ivarleonmenger.de/sitemap_index.xml.

AI search readiness

100
4 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://ivarleonmenger.de/llms.txt (5 KiB, 6 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65

  • 1 linked page is broken

    Your homepage links to https://ivarleonmenger.de/biographie, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 5 pages without a meta description

    https://ivarleonmenger.de/veranstaltung/georgsmarienhuette-buchhandlung-sedlmair, https://ivarleonmenger.de/veranstaltung/weiterstadt-lesung-duester, https://ivarleonmenger.de/veranstaltung/2027-keine-lesungen-dieses-jahr, https://ivarleonmenger.de/impressum and https://ivarleonmenger.de/datenschutz2018 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://ivarleonmenger.de/datenschutz2018 has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://ivarleonmenger.de/veranstaltung/georgsmarienhuette-buchhandlung-sedlmair and https://ivarleonmenger.de/veranstaltung/weiterstadt-lesung-duester 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.

  • 6 pages slow to respond

    https://ivarleonmenger.de/buecher, https://ivarleonmenger.de/hoerspiele, https://ivarleonmenger.de/lesungen, https://ivarleonmenger.de/autogramm, https://ivarleonmenger.de/biografie and https://ivarleonmenger.de/veranstaltung/weiterstadt-lesung-duester took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 checks passed

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

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    21 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90

  • Thin social proof

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

  • 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 585 words of copy

    The homepage carries about 585 words of visible text.

4 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop”.

  • 2 calls to action

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 2 cookies set on arrival

    2

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

  • No consent tool detected

    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.

  • 4 other companies contacted

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

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 psychothriller.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Neue Medien Muennich GmbH

Company

Founded
2009
Headquarters
Mühltal

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on psychothriller.de, including 16 speed issues, 3 SEO issues and 1 conversion gap. 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