Website review, no card needed

rewe-dortmund.de logo

rewe-dortmund.de website review

Visit site (opens in a new tab)Reviewed 19 November 202631 issues · 73 checks

This review found 31 issues worth fixing on rewe-dortmund.de, 18 of them high impact, across 73 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
2.7 s1.9 sMay 30Nov 142.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.5 s
Nov 7, 20262.5 s
Nov 14, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
127 ms85 msMay 30Nov 14108 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026118 ms
Jun 6, 2026117 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026114 ms
Jul 4, 2026114 ms
Jul 11, 2026114 ms
Jul 18, 2026119 ms
Jul 25, 2026120 ms
Aug 1, 2026121 ms
Aug 8, 2026122 ms
Aug 15, 2026120 ms
Aug 22, 2026118 ms
Aug 29, 2026116 ms
Sep 5, 2026113 ms
Sep 12, 2026107 ms
Sep 19, 2026102 ms
Sep 26, 202696 ms
Oct 3, 202690 ms
Oct 10, 202695 ms
Oct 17, 202696 ms
Oct 24, 202698 ms
Oct 31, 2026103 ms
Nov 7, 2026105 ms
Nov 14, 2026108 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 rewe-dortmund.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rewe-dortmund.de at 0.6 s0.6 s
  2. rewe-dortmund.de at 1.2 s1.2 s
  3. rewe-dortmund.de at 1.7 s1.7 s
  4. rewe-dortmund.de at 2.3 s2.3 s
  5. rewe-dortmund.de at 2.9 s2.9 s
  6. rewe-dortmund.de at 3.5 s3.5 s
  7. rewe-dortmund.de at 4.1 s4.1 s
  8. rewe-dortmund.de at 4.6 s4.6 s

Speed

5 to fix46
  • Use efficient cache lifetimes

    7.8 s · 27.9 MB

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

  • Reduce unused JavaScript

    2.1 s · 429 KiB

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

  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 46

    46/100

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

  • Reduce unused CSS

    450 ms · 105 KiB

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

  • Font display

    250 ms

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

  • Document request latency

    228 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Improve image delivery

    43 KiB

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

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 465 ms

    465 ms

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

Core Web Vitals

10 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: 10.1 s

    10.1 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Time to Interactive: 10.1 s

    10.1 s

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

  • Speed Index: 7.4 s

    7.4 s

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

  • Cumulative Layout Shift: 0.285

    0.285

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

3 checks passed
  • Real-user INP: 115 ms

    115 ms

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

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). 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 fix70
  • Page weight: 28.3 MB in 72 requests

    28.3 MB

    Your homepage downloads 28.3 MB in 72 requests on a phone: media 26.5 MB (2), scripts 987 KiB (28) and HTML 341 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 8.0 g of CO₂ per visit

    8.02 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

3 to fixGoogle 9694
  • 3 text elements with low contrast

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

  • 3 images without alt text

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

  • 6 links without text

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

1 checks passed
  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 1 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 9273
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), 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.

  • 89 internal links, 18 external

    The homepage links to 89 pages on rewe-dortmund.de and 18 external pages.

4 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “Rewe Dortmund – Aus der Region”.

  • Canonical URL set

    The canonical URL is https://www.rewe-dortmund.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.rewe-dortmund.de/wp-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.

  • No llms.txt

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

2 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 (356 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.rewe-dortmund.de/ueber-uns, https://www.rewe-dortmund.de/stiftung, https://www.rewe-dortmund.de/nachhaltigkeit, https://www.rewe-dortmund.de/compliance, https://www.rewe-dortmund.de/genossenschaft and https://www.rewe-dortmund.de/partnerinfos and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.rewe-dortmund.de/stiftung, https://www.rewe-dortmund.de/genossenschaft and https://www.rewe-dortmund.de/sponsoring have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 pages slow to respond

    https://www.rewe-dortmund.de/ueber-uns, https://www.rewe-dortmund.de/stiftung, https://www.rewe-dortmund.de/nachhaltigkeit, https://www.rewe-dortmund.de/compliance, https://www.rewe-dortmund.de/genossenschaft and https://www.rewe-dortmund.de/partnerinfos and 6 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 20 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

2 to fixGoogle 10087
  • 6 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 463 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

  • 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 other company contacted

    Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Hetzner

Company

Employees
170,000
Founded
1927
Headquarters
Cologne

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on rewe-dortmund.de, including 15 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