Website review, no card needed

platzangst.com logo

platzangst.com website review

Visit site (opens in a new tab)Reviewed 9 November 202621 issues · 76 checks

This review found 21 issues worth fixing on platzangst.com, 3 of them high impact, across 76 checks. The most urgent: interactive controls must not be nested (1 element). 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
948 ms763 msMay 23Nov 7784 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026889 ms
May 30, 2026843 ms
Jun 6, 2026829 ms
Jun 13, 2026819 ms
Jun 20, 2026825 ms
Jun 27, 2026865 ms
Jul 4, 2026877 ms
Jul 11, 2026912 ms
Jul 18, 2026906 ms
Jul 25, 2026877 ms
Aug 1, 2026882 ms
Aug 8, 2026894 ms
Aug 15, 2026891 ms
Aug 22, 2026918 ms
Aug 29, 2026924 ms
Sep 5, 2026917 ms
Sep 12, 2026927 ms
Sep 19, 2026911 ms
Sep 26, 2026910 ms
Oct 3, 2026874 ms
Oct 10, 2026841 ms
Oct 17, 2026835 ms
Oct 24, 2026799 ms
Oct 31, 2026802 ms
Nov 7, 2026784 ms
Real-visitor tap response (INP)75th percentile, phones
117 ms94 msMay 23Nov 7106 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202697 ms
May 30, 202697 ms
Jun 6, 202698 ms
Jun 13, 202698 ms
Jun 20, 2026100 ms
Jun 27, 2026102 ms
Jul 4, 2026101 ms
Jul 11, 2026104 ms
Jul 18, 2026103 ms
Jul 25, 202699 ms
Aug 1, 2026100 ms
Aug 8, 2026100 ms
Aug 15, 202697 ms
Aug 22, 2026101 ms
Aug 29, 2026103 ms
Sep 5, 2026106 ms
Sep 12, 2026112 ms
Sep 19, 2026111 ms
Sep 26, 2026114 ms
Oct 3, 2026111 ms
Oct 10, 2026113 ms
Oct 17, 2026113 ms
Oct 24, 2026109 ms
Oct 31, 2026112 ms
Nov 7, 2026106 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 platzangst.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. platzangst.com at 0.4 s0.4 s
  2. platzangst.com at 0.8 s0.8 s
  3. platzangst.com at 1.1 s1.1 s
  4. platzangst.com at 1.5 s1.5 s
  5. platzangst.com at 1.9 s1.9 s
  6. platzangst.com at 2.3 s2.3 s
  7. platzangst.com at 2.6 s2.6 s
  8. platzangst.com at 3.0 s3.0 s

Speed

3 to fix93
  • Render-blocking requests

    650 ms

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

  • Improve image delivery

    472 KiB

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

  • 1,504 HTML elements

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

  • Reduce unused CSS

    150 ms · 13 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, shop.app and Klaviyo), adding 159 KiB and 21 ms of main-thread time.

  • Reduce unused JavaScript

    22 KiB

    About 22 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    8 KiB

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

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

3 checks passed
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.5 s

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

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

1 to fix100
  • Largest Contentful Paint: 3.2 s

    3.2 s

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

  • Tap response (INP) got 12% slower for real visitors

    +12%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

11 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: 0.8 s

    0.8 s

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

  • Real-user INP: 106 ms

    106 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.6 s

    0.6 s

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

  • Real-user TTFB: 338 ms

    338 ms

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

  • Time to Interactive: 3.2 s

    3.2 s

    The page is fully interactive after 3.2 s.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.2 s

    2.2 s

    Visually, the page fills in at 2.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.016

    0.016

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    pla-start-mobil-Neuheiten2026_f3a18e0a-1efb-4cd4-9c61-57f4a3 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.5 g of CO₂ per visit

    0.46 g

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

3 checks passed
  • Page weight: 1.6 MB in 102 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 102 requests on a phone: images 1.1 MB (21), scripts 253 KiB (49) and fonts 167 KiB (4). That is a lean page.

  • 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

4 to fixGoogle 9796
  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

  • 40 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 9280
  • No H1 headline

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

  • Meta description is long (281 characters)

    Your meta description is 281 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization, Product and WebSite) but with 1 problem, for example “Product: image is not an absolute URL ("//www.platzangst.com/cdn/shop/files/IMG_1003.jpg?v=17929915…”.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 112 internal links, 4 external

    The homepage links to 112 pages on platzangst.com and 4 external pages.

5 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “MTB and gravel clothing from Platzangst – Functional & Stylish”.

  • Canonical URL set

    The canonical URL is https://www.platzangst.com/en.

  • 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.platzangst.com/sitemap.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, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.platzangst.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://www.platzangst.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.platzangst.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.platzangst.com/customer_authentication/redirect and https://www.platzangst.com/en/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.platzangst.com/customer_authentication/redirect, https://www.platzangst.com/en/collections/all and https://www.platzangst.com/en/collections/mtb-handschuhe have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.platzangst.com/customer_authentication/redirect and https://www.platzangst.com/en/collections/all took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

2 checks passed
  • Tap targets are thumb-sized

    66 of 72 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 337 words of copy

    The homepage carries about 337 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 7 calls to action

    The homepage has 7 calls to action, for example “Learn more”, “Shop” and “Start shopping”.

  • 16 short forms

    16 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 6 cookies set on arrival

    6

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

  • 2 other companies contacted

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

Apps on your store

Your storefront loads 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Essential A B Testing · Pandectes Gdpr · Multifeeds · Judge Me Reviews · Klaviyo Email Marketing Sms · Microsoft Clarity · Arrivesby · Swatch King · Analyzify Ga4 Ads Tracking · Gdpr Cookie Consent · Stape Remix · Locales Ai · nfcube.com · cloudfront.net · trustedshops.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on platzangst.com, including 4 speed issues, 4 SEO issues and 2 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