Website review, no card needed

roller.de logo

roller.de website review

Visit site (opens in a new tab)Reviewed 29 October 202640 issues · 90 checks

This review found 40 issues worth fixing on roller.de, 14 of them high impact, across 90 checks. The most urgent: render-blocking requests. 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.7 s1.8 sMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.3 s
Sep 26, 20262.1 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
259 ms240 msMay 9Oct 24243 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026245 ms
May 16, 2026242 ms
May 23, 2026243 ms
May 30, 2026244 ms
Jun 6, 2026245 ms
Jun 13, 2026245 ms
Jun 20, 2026245 ms
Jun 27, 2026248 ms
Jul 4, 2026253 ms
Jul 11, 2026256 ms
Jul 18, 2026257 ms
Jul 25, 2026254 ms
Aug 1, 2026251 ms
Aug 8, 2026251 ms
Aug 15, 2026252 ms
Aug 22, 2026253 ms
Aug 29, 2026252 ms
Sep 5, 2026251 ms
Sep 12, 2026248 ms
Sep 19, 2026246 ms
Sep 26, 2026246 ms
Oct 3, 2026246 ms
Oct 10, 2026245 ms
Oct 17, 2026244 ms
Oct 24, 2026243 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 roller.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. roller.de at 1.2 s1.2 s
  2. roller.de at 2.4 s2.4 s
  3. roller.de at 3.7 s3.7 s
  4. roller.de at 4.9 s4.9 s
  5. roller.de at 6.1 s6.1 s
  6. roller.de at 7.3 s7.3 s
  7. roller.de at 8.6 s8.6 s
  8. roller.de at 9.8 s9.8 s

Speed

11 to fix32
  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 8.5 s

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

  • Reduce unused JavaScript

    600 ms · 1,005 KiB

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

  • Improve image delivery

    950 ms · 565 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, ZenDesk and Google CDN and others), adding 1.5 MB and 1.0 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 579 ms

    579 ms

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

  • ZenDesk adds 218 ms

    218 ms

    ZenDesk costs a phone 218 ms of main-thread work and 428 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.

  • Google CDN adds 191 ms

    191 ms

    Google CDN costs a phone 191 ms of main-thread work and 296 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.

  • 1,578 HTML elements

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

  • Reduce unused CSS

    150 ms · 36 KiB

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

  • Use efficient cache lifetimes

    53 KiB

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

1 checks passed
  • Server response: 111 ms

    111 ms

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

Core Web Vitals

8 to fix33
  • 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: 21.6 s

    21.6 s

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

  • Total Blocking Time: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “KW4426 - 20P Teuerster Artikel”.

  • Speed Index: 8.3 s

    8.3 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Real-user INP: 249 ms

    249 ms

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

  • Real-user CLS: 0.20

    0.20

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

  • Tap response (INP) held steady for real visitors

    0%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 713 ms

    713 ms

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

  • Largest content (LCP) got 23% faster for real visitors

    -23%

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

  • Cumulative Layout Shift: 0.009

    0.009

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

Images and page weight

2 to fix81
  • Page weight: 3.6 MB in 147 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 147 requests on a phone: scripts 2.3 MB (76), images 814 KiB (35) and fonts 328 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Teaser-einloggen-App_mobile_v2 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 1.0 g of CO₂ per visit

    1.01 g

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

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

9 to fixGoogle 8089
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 4 text elements with low contrast

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

  • Links must have discernible text (4 elements)

    Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 23 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.

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

  • 11 tap targets too small

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

  • 2 form fields without a label

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

    Elements with visible text labels do not have matching accessible names. (16 elements).

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

    Structured data found ((untyped), Organization, WebPage and WebSite) but with 1 problem, for example “block has no @type”.

  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 127 internal links, 10 external

    The homepage links to 127 pages on roller.de and 10 external pages.

6 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Über 20.000 Artikel online ✓ Möbel direkt abholen oder liefern lassen ✓ Online & in über 110 Filialen ✓ Tiefpreisgarant…”.

  • One H1 headline

    Your main headline reads: “ROLLER.de: Dein Möbelhaus online”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Dein günstiges Möbelhaus » Lass Schönes einziehen!”.

  • Canonical URL set

    The canonical URL is https://www.roller.de/.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.roller.de/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.

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.

  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 4 pages without a meta description

    https://www.roller.de/wunschliste, https://www.roller.de/moebelhaeuser, https://www.roller.de/sale and https://www.roller.de/wohnideen-inspirationen/marken have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages slow to respond

    https://www.roller.de/moebelhaeuser, https://www.roller.de/moebel, https://www.roller.de/kueche, https://www.roller.de/wohnbereiche/kueche/elektrogeraete, https://www.roller.de/lampen-und-leuchten and https://www.roller.de/weihnachtsmarkt and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

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

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 27 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 543 words of visible text.

1 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Nuxt
Hosting
Google Cloud

Hiring

Hiring
18 open roles
Teams
GTM (8), Tech (6), Finance (1)
Job board
greenhouse

Company

Founded
1969
Headquarters
Gelsenkirchen

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on roller.de, including 19 speed issues, 2 SEO issues and 7 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