Website review, no card needed
wero.de website review
Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 78 checks
This review found 35 issues worth fixing on wero.de, 14 of them high impact, across 78 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81B- #39,341 of 116,285 reviewed websitesbeats 61%
- #26,507 of 66,755 online storesbeats 54%
- #24 of 77 Shopware storesbeats 66%
Closest competitors among Shopware stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 145 ms |
| May 9, 2026 | 141 ms |
| May 16, 2026 | 146 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 148 ms |
| Jun 6, 2026 | 151 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 156 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 157 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 147 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 143 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 140 ms |
| Sep 12, 2026 | 141 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 131 ms |
| Oct 17, 2026 | 124 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
Speed
Render-blocking requests
1.8 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused CSS
1.1 s · 199 KiBAbout 199 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 49
49/100Your mobile performance score is 49 (desktop: 69). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 third-party services on the page
7 third-party services load with your homepage (codeblick.dev, PayPal and ccm19.de and others), adding 476 KiB and 901 ms of main-thread time.
Reduce unused JavaScript
450 ms · 298 KiBAbout 298 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 490 ms. During a long task the page ignores taps.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
codeblick.dev adds 396 ms
396 mscodeblick.dev costs a phone 396 ms of main-thread work and 4 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.
2,740 HTML elements
The page has 2,740 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
244 KiB7 files are served with short cache lifetimes, so returning visitors download them again (244 KiB).
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
Improve image delivery
15 KiB1 image could be 15 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.
1 checks passed
Server response: 120 ms
120 msYour server sent the HTML in 120 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 6.1 s
6.1 sYour largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ein orangefarbener Erste-Hilfe-Kasten steht neben einem Coo…”.
Time to Interactive: 10.4 s
10.4 sThe page becomes fully interactive after 10.4 s. Good is under 3.8 s.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 634 ms
634 msScripts block taps and scrolling for 634 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 813 ms
813 msReal visitors wait 813 ms 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.
7 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 122 ms
122 msReal visitors wait 122 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 145 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.02
0.02The layout barely moves while loading (CLS 0.02, good is under 0.1).
Images and page weight
Page weight: 13.3 MB in 166 requests
13.3 MBYour homepage downloads 13.3 MB in 166 requests on a phone: media 11.8 MB (1), scripts 857 KiB (96) and images 333 KiB (42). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Kachel-Klein_3Spalten-1Zeile_426x292_Ubersicht_ErsteHilfe.we 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 3.8 g of CO₂ per visit
3.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.77 g of CO₂e: 452.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
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails 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.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 106 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
410 internal links, 14 external
The homepage links to 410 pages on wero.de and 14 external pages.
7 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Markenprodukte und Dienstleistungen der WERO GmbH & Co. KG ✓ Erste Hilfe ✓ Hautschutz & Hygiene ✓ Arbeitsschutz ✓ Takti…”.
One H1 headline
Your main headline reads: “Gut geschützt durch die kalte Jahreszeit”.
Title: 57 characters
Your title is a healthy 57 characters: “WERO GmbH & Co. KG Onlineshop - Best in Work.Life.Safety.”.
Canonical URL set
The canonical URL is https://www.wero.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.wero.de/sitemap.xml.
AI search readiness
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,875 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.wero.de/llms.txt (4 KiB, 11 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.wero.de/%7B%7Battributes.Deeplink%7D%7D, which answers with an error. Visitors hit a dead end and search engines drop it.
1 linked page hidden from search
https://www.wero.de/wishlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.wero.de/karriere, https://www.wero.de/factfinder/result and https://www.wero.de/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.wero.de/p/wero-smart-case-erste-hilfe-koffer-din-13157-erweitert-allround, whose canonical is https://www.wero.de/p/wero-smart-case-erste-hilfe-koffer-din-13157-erweitert. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.wero.de/wishlist, https://www.wero.de/erste-hilfe/erste-hilfe-materialien/din-oenorm/din-13157 and https://www.wero.de/erste-hilfe/erste-hilfe-materialien/din-oenorm/din-13169 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 192 found) and read each the way a search engine does.
2 checks passed
Titles are unique
Every page we checked has its own title.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 4 trust badges. 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 989 words of copy
The homepage carries about 989 words of visible text.
3 checks passed
10 short forms
10 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 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.
8 other companies contacted
Loading the homepage contacts 8 hosts 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 wero.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
- Tailwind CSS
- Analytics
- Google Tag Manager
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 wero.de, including 18 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.