Website review, no card needed

rueckwand24.com logo

rueckwand24.com website review

Visit site (opens in a new tab)Reviewed 4 November 202635 issues · 88 checks

This review found 35 issues worth fixing on rueckwand24.com, 13 of them high impact, across 88 checks. The most urgent: fails Core Web Vitals for real visitors. 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.3 s2.1 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
362 ms191 msMay 16Oct 31331 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026211 ms
May 23, 2026212 ms
May 30, 2026214 ms
Jun 6, 2026219 ms
Jun 13, 2026218 ms
Jun 20, 2026220 ms
Jun 27, 2026222 ms
Jul 4, 2026225 ms
Jul 11, 2026227 ms
Jul 18, 2026226 ms
Jul 25, 2026221 ms
Aug 1, 2026230 ms
Aug 8, 2026252 ms
Aug 15, 2026273 ms
Aug 22, 2026301 ms
Aug 29, 2026313 ms
Sep 5, 2026315 ms
Sep 12, 2026315 ms
Sep 19, 2026320 ms
Sep 26, 2026330 ms
Oct 3, 2026340 ms
Oct 10, 2026342 ms
Oct 17, 2026341 ms
Oct 24, 2026340 ms
Oct 31, 2026331 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 rueckwand24.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rueckwand24.com at 0.9 s0.9 s
  2. rueckwand24.com at 1.9 s1.9 s
  3. rueckwand24.com at 2.8 s2.8 s
  4. rueckwand24.com at 3.8 s3.8 s
  5. rueckwand24.com at 4.7 s4.7 s
  6. rueckwand24.com at 5.6 s5.6 s
  7. rueckwand24.com at 6.6 s6.6 s
  8. rueckwand24.com at 7.5 s7.5 s

Speed

11 to fix54
  • Main-thread work: 6.0 s

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

  • 6,012 HTML elements

    The page has 6,012 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 (Hotjar, Google Tag Manager and Shopify and others), adding 1.1 MB and 1.3 s of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • Render-blocking requests

    900 ms

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

  • Reduce unused JavaScript

    300 ms · 381 KiB

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

  • Use efficient cache lifetimes

    150 ms · 526 KiB

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

  • Hotjar adds 626 ms

    626 ms

    Hotjar costs a phone 626 ms of main-thread work and 65 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.

  • 12 long tasks on the main thread

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

  • Google Tag Manager adds 291 ms

    291 ms

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

  • Shopify adds 136 ms

    136 ms

    Shopify costs a phone 136 ms of main-thread work and 394 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

    150 ms · 58 KiB

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

  • Improve image delivery

    180 KiB

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    16 KiB

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

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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 69 ms

    69 ms

    Your server sent the HTML in 69 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.

  • Time to Interactive: 18.5 s

    18.5 s

    The page becomes fully interactive after 18.5 s. Good is under 3.8 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.

  • Largest Contentful Paint: 5.0 s

    5.0 s

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

  • Real-user INP: 271 ms

    271 ms

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

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

    +59%

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

  • Speed Index: 5.1 s

    5.1 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

6 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 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.

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 462 ms

    462 ms

    Real visitors wait 462 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.

  • 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: 4.2 MB in 292 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 292 requests on a phone: scripts 1.3 MB (129), images 1.2 MB (45) and other files 863 KiB (93). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (129 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 1.2 g of CO₂ per visit

    1.20 g

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

2 checks passed
  • 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

5 to fixGoogle 8392
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 9 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Zoom is disabled

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

  • Headings skip levels

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

  • autocomplete attributes are not used correctly

    autocomplete attributes are not used correctly (4 elements).

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 83 images in the HTML carry an alt attribute.

  • 49 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: 49 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 1,232 internal links, 5 external

    The homepage links to 1,232 pages on rueckwand24.com and 5 external pages.

8 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Deine individuelle Rückwand für jeden Wohnbereich: ✔️Küchenrückwand ✔️Duschrückwand ✔️Badrückwand ✔️Nischenrückwand ✔️S…”.

  • One H1 headline

    Your main headline reads: “Rueckwand24”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Rueckwand24 - Individuelle Rückwände nach Deinen Wünschen”.

  • Canonical URL set

    The canonical URL is https://rueckwand24.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://rueckwand24.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix88
  • 1 page without a meta description

    https://rueckwand24.com/policies/refund-policy has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://rueckwand24.com/collections/kuechenrueckwand and https://rueckwand24.com/collections/kuechenrueckwand-acryl-plexiglas use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://rueckwand24.com/policies/refund-policy, https://rueckwand24.com/collections/kuechenrueckwand, https://rueckwand24.com/collections/kuechenrueckwand-glas, https://rueckwand24.com/collections/kuechenrueckwand-acryl-plexiglas, https://rueckwand24.com/collections/kuechenrueckwand-aluverbund and https://rueckwand24.com/collections/kuechenrueckwand-keramik and 9 others 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 198 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 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://forms.soundestlink.com/REST/forms/v2/track/view?timestamp=1793764409914&brandID=650c6e16d924f42a3405b5ad&pageTitle=Rueckwand24+-+Individuelle+R%C3%BCckw%C3%A4nde+nach+Deinen+W%C3%BCnschen&page.

  • 12 small tap targets

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

  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • A 9-field form

    Your longest form asks for 9 fields (7 required). Every extra field lowers completion.

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

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

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Zurück zum Shop”.

  • Social proof on the page

    Social proof on the homepage: 37 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar, Mixpanel and TikTok Pixel.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 4 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.

  • 24 cookies set on arrival

    24

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

  • 50 other companies contacted

    Loading the homepage contacts 50 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 rueckwand24.com, 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
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar | Mixpanel
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on rueckwand24.com, including 19 speed 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