Website review, no card needed

retro-stage.de logo

retro-stage.de website review

Visit site (opens in a new tab)Reviewed 9 November 202656 issues · 99 checks

This review found 56 issues worth fixing on retro-stage.de, 25 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. 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.2 s1.9 sMay 23Nov 72.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Nov 7, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
199 ms166 msMay 23Nov 7170 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026188 ms
May 30, 2026182 ms
Jun 6, 2026177 ms
Jun 13, 2026179 ms
Jun 20, 2026185 ms
Jun 27, 2026190 ms
Jul 4, 2026194 ms
Jul 11, 2026195 ms
Jul 18, 2026195 ms
Jul 25, 2026192 ms
Aug 1, 2026192 ms
Aug 8, 2026192 ms
Aug 15, 2026188 ms
Aug 22, 2026188 ms
Aug 29, 2026188 ms
Sep 5, 2026186 ms
Sep 12, 2026185 ms
Sep 19, 2026180 ms
Sep 26, 2026179 ms
Oct 3, 2026177 ms
Oct 10, 2026175 ms
Oct 17, 2026173 ms
Oct 24, 2026174 ms
Oct 31, 2026173 ms
Nov 7, 2026170 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 retro-stage.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. retro-stage.de at 1.5 s1.5 s
  2. retro-stage.de at 3.0 s3.0 s
  3. retro-stage.de at 4.5 s4.5 s
  4. retro-stage.de at 6.0 s6.0 s
  5. retro-stage.de at 7.5 s7.5 s
  6. retro-stage.de at 9.0 s9.0 s
  7. retro-stage.de at 10.5 s10.5 s
  8. retro-stage.de at 12.0 s12.0 s

Speed

13 to fix36
  • Reduce unused JavaScript

    3.3 s · 934 KiB

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

  • Shopify adds 1.3 s

    1.3 s

    Shopify costs a phone 1.3 s of main-thread work and 311 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 10.1 s

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

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

  • 4,226 HTML elements

    The page has 4,226 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 (Shopify, loox.io and Google Tag Manager and others), adding 1.3 MB and 2.6 s of main-thread time.

  • Improve image delivery

    50 ms · 1.2 MB

    14 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

  • Render-blocking requests

    750 ms

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

  • Use efficient cache lifetimes

    250 ms · 318 KiB

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

  • Reduce unused CSS

    450 ms · 116 KiB

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

  • 18 long tasks on the main thread

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

  • Google Tag Manager adds 334 ms

    334 ms

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

  • loox.io adds 371 ms

    371 ms

    loox.io costs a phone 371 ms of main-thread work and 17 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.

  • Legacy JavaScript

    150 ms · 23 KiB

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

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

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

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 20.6 s

    20.6 s

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

  • Time to Interactive: 25.0 s

    25.0 s

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

  • Speed Index: 12.8 s

    12.8 s

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

  • Cumulative Layout Shift: 0.261

    0.261

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

  • Total Blocking Time: 626 ms

    626 ms

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • 36 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

5 checks passed
  • Real-user INP: 167 ms

    167 ms

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

  • 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: 1.7 s

    1.7 s

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

  • Real-user TTFB: 374 ms

    374 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

Images and page weight

4 to fix43
  • Page weight: 6.9 MB in 221 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 221 requests on a phone: images 3.8 MB (40), scripts 1.7 MB (68) and other files 908 KiB (85). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (507 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.

  • 2 images far larger than shown

    144 KiB

    2 images are downloaded at several times the size a phone draws them, for example samt_allesunter35_261026_1024x.jpg at 1,024 px wide, shown at 173 px. Resized copies would save about 144 KiB.

  • About 2.0 g of CO₂ per visit

    1.95 g

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

Accessibility

16 to fixGoogle 6581
  • Invalid ARIA attributes

    8 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (8 elements)

    Certain ARIA roles must contain particular children: 8 elements on the page fail this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (7 elements)

    ARIA attributes must conform to valid values: 7 elements on the page fail this check, rated critical by axe-core.

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

    77 elements hidden from screen readers can still receive keyboard focus.

  • Interactive controls must not be nested (16 elements)

    Interactive controls must not be nested: 16 elements on the page fail this check, rated serious by axe-core.

  • 11 text elements with low contrast

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

  • 11 tap targets too small

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

  • ARIA input fields must have an accessible name (9 elements)

    ARIA input fields must have an accessible name: 9 elements on the page fail this check, rated serious by axe-core.

  • ARIA toggle fields must have an accessible name (7 elements)

    ARIA toggle fields must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

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

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

  • Zoom is disabled

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

  • 47 links without text

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

  • Elements marked as presentational should be consistently ignored (8 elements)

    Elements marked as presentational should be consistently ignored: 8 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 208 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 66 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 16 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 9282
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “RetroStage® | Vintage-Mode | Accessoires | Schuhe – retro stage-German”.

  • 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 long (175 characters)

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

  • 17 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 345 internal links, 6 external

    The homepage links to 345 pages on retro-stage.de and 6 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Retro Stage”.

  • Canonical URL set

    The canonical URL is https://www.retro-stage.de/.

  • 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.retro-stage.de/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.retro-stage.de/collections/neu-am-5-nov-1 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.retro-stage.de/collections/neu-1 and https://www.retro-stage.de/collections/neu-am-5-nov-1 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 171 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 2 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://www.retro-stage.de/.

  • 81 small tap targets

    81 of 185 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 (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'dataset')”.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

3 checks passed
  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics, Microsoft Clarity and TikTok Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 2 of them by other companies (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.

  • 44 other companies contacted

    Loading the homepage contacts 44 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 retro-stage.de, 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

Microsoft Clarity · Ta Labels Badges · Minmaxify Order Limits · Countdown Timer · Avada Faqs · Unlimited Bundles · Freegifts · loox.io · revy.io · seel.com · hextom.com · omnisnippet1.com · bogos.io · webgains.com · kiwisizing.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

Framework
jQuery
E-commerce
Shopify
Analytics
Google 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 56 issues on retro-stage.de, including 21 speed issues, 4 SEO issues and 3 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
retro-stage.de website review: scores and fixes