Website review, no card needed

achgut.com logo

achgut.com website review

Visit site (opens in a new tab)Reviewed 7 November 202650 issues · 88 checks

This review found 50 issues worth fixing on achgut.com, 12 of them high impact, across 88 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
1.0 s932 msMay 16Oct 31989 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026996 ms
May 23, 2026999 ms
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 20261.0 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 2026978 ms
Aug 1, 2026967 ms
Aug 8, 2026958 ms
Aug 15, 2026948 ms
Aug 22, 2026945 ms
Aug 29, 2026943 ms
Sep 5, 2026943 ms
Sep 12, 2026955 ms
Sep 19, 2026964 ms
Sep 26, 2026973 ms
Oct 3, 2026981 ms
Oct 10, 2026980 ms
Oct 17, 2026981 ms
Oct 24, 2026985 ms
Oct 31, 2026989 ms
Real-visitor tap response (INP)75th percentile, phones
257 ms211 msMay 16Oct 31237 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026216 ms
May 23, 2026219 ms
May 30, 2026229 ms
Jun 6, 2026235 ms
Jun 13, 2026242 ms
Jun 20, 2026247 ms
Jun 27, 2026246 ms
Jul 4, 2026245 ms
Jul 11, 2026244 ms
Jul 18, 2026244 ms
Jul 25, 2026245 ms
Aug 1, 2026247 ms
Aug 8, 2026252 ms
Aug 15, 2026252 ms
Aug 22, 2026248 ms
Aug 29, 2026248 ms
Sep 5, 2026247 ms
Sep 12, 2026249 ms
Sep 19, 2026251 ms
Sep 26, 2026250 ms
Oct 3, 2026248 ms
Oct 10, 2026245 ms
Oct 17, 2026242 ms
Oct 24, 2026239 ms
Oct 31, 2026237 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 achgut.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. achgut.com at 0.6 s0.6 s
  2. achgut.com at 1.3 s1.3 s
  3. achgut.com at 1.9 s1.9 s
  4. achgut.com at 2.5 s2.5 s
  5. achgut.com at 3.1 s3.1 s
  6. achgut.com at 3.8 s3.8 s
  7. achgut.com at 4.4 s4.4 s
  8. achgut.com at 5.0 s5.0 s

Speed

10 to fix71
  • Use efficient cache lifetimes

    1.6 s · 2.1 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (cdntrf.com, Taboola and Google/Doubleclick Ads and others), adding 1.9 MB and 816 ms of main-thread time.

  • Mobile performance score: 71

    71/100

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

  • Reduce unused JavaScript

    300 ms · 516 KiB

    About 516 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.

  • Render-blocking requests

    700 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Improve image delivery

    150 ms · 442 KiB

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

  • cdntrf.com adds 295 ms

    295 ms

    cdntrf.com costs a phone 295 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.

  • Taboola adds 197 ms

    197 ms

    Taboola costs a phone 197 ms of main-thread work and 1,017 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: 2.8 s

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

  • Google/Doubleclick Ads adds 123 ms

    123 ms

    Google/Doubleclick Ads costs a phone 123 ms of main-thread work and 310 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.

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    47 KiB

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

  • Reduce unused CSS

    13 KiB

    About 13 KiB of CSS is downloaded but never applied on this page.

  • 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: 54 ms

    54 ms

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

Core Web Vitals

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

  • Time to Interactive: 15.1 s

    15.1 s

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

  • Real-user INP: 275 ms

    275 ms

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

  • Speed Index: 5.7 s

    5.7 s

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

  • Cumulative Layout Shift: 0.217

    0.217

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

    Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • 21 images without width and height

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

  • Total Blocking Time: 255 ms

    255 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

4 checks passed
  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 371 ms

    371 ms

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

Images and page weight

3 to fix68
  • Page weight: 3.6 MB in 145 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 145 requests on a phone: images 1.9 MB (42), scripts 1.3 MB (22) and fonts 289 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 12 images in older formats

    12 images (903 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.

  • 10 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    1.02 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.02 g of CO₂e: 121.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

11 to fixGoogle 7685
  • 51 text elements with low contrast

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

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

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

  • 9 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 8373
  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (62 characters)

    Your meta description is only 62 characters: “Die Achse des Guten: Wir leisten uns was. Eine eigene Meinung.”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

    No XML sitemap at https://www.achgut.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 53 internal links, 23 external

    The homepage links to 53 pages on achgut.com and 23 external pages.

3 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Startseite – DIE ACHSE DES GUTEN. ACHGUT.COM”.

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

AI search readiness

2 to fix53
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-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 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.achgut.com/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 1 crawler

    robots.txt blocks ClaudeBot, 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 (1,261 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 9 pages without a meta description

    https://www.achgut.com/meinung, https://www.achgut.com/video, https://www.achgut.com/podcast, https://www.achgut.com/woche, https://www.achgut.com/presseschau and https://www.achgut.com/seite/achgut_kontakt and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.achgut.com/meinung, https://www.achgut.com/video, https://www.achgut.com/podcast, https://www.achgut.com/woche, https://www.achgut.com/presseschau and https://www.achgut.com/autoren have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 4 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://ups.xplosion.de/ctx?event_id=ctx_json&_sid=24141&hostSiteUrl=https://www.achgut.com/&referr…”.

1 checks passed
  • 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.

  • 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 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 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 1,392 words of copy

    The homepage carries about 1,392 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop” and “Zum Shop”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Outbrain and Taboola and 2 mores (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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

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

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

Upkeep, stack and company

Stack

Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on achgut.com, including 19 speed issues, 5 SEO issues 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