Website review, no card needed
messgewander.de website review
Visit site (opens in a new tab)Reviewed 16 November 202630 issues · 80 checks
This review found 30 issues worth fixing on messgewander.de, 12 of them high impact, across 80 checks. The most urgent: page weight: 36.4 MB in 363 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- #38,865 of 114,427 reviewed websitesbeats 60%
- #26,347 of 66,188 online storesbeats 54%
- #25,451 of 60,578 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 143 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 147 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 177 ms |
| Jul 11, 2026 | 191 ms |
| Jul 18, 2026 | 181 ms |
| Jul 25, 2026 | 176 ms |
| Aug 1, 2026 | 178 ms |
| Aug 8, 2026 | 174 ms |
| Aug 15, 2026 | 183 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 208 ms |
| Sep 5, 2026 | 195 ms |
| Sep 12, 2026 | 190 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 153 ms |
| Oct 3, 2026 | 160 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 141 ms |
| Oct 31, 2026 | 131 ms |
| Nov 7, 2026 | 136 ms |
| Nov 14, 2026 | 137 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
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.9 s
2.3 s
2.8 s
3.3 s
3.7 s
Speed
Reduce unused JavaScript
1.2 s · 293 KiBAbout 293 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Main-thread work: 6.1 s
A phone's processor spends 6.1 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,012 HTML elements
The page has 3,012 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
983 KiB20 images could be 983 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
5 third-party services on the page
5 third-party services load with your homepage (Shopify, Trusted Shops and etrusted.com and others), adding 1.1 MB and 501 ms of main-thread time.
Shopify adds 405 ms
405 msShopify costs a phone 405 ms of main-thread work and 848 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.
Render-blocking requests
400 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
Reduce unused CSS
150 ms · 68 KiBAbout 68 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
150 ms · 58 KiB18 files are served with short cache lifetimes, so returning visitors download them again (58 KiB).
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
Font display
50 msWeb 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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.7 s
11.7 sYour largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 17.5 s
17.5 sThe page becomes fully interactive after 17.5 s. Good is under 3.8 s.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 221 ms
221 msScripts block taps and scrolling for 221 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 146 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
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: 165 ms
165 msReal visitors wait 165 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 36.4 MB in 363 requests
36.4 MBYour homepage downloads 36.4 MB in 363 requests on a phone: media 31.8 MB (2), images 2.2 MB (40) and scripts 1.0 MB (136). Under 2 MB keeps phones on slow connections fast.
About 10.3 g of CO₂ per visit
10.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.32 g of CO₂e: 1238.7 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
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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
Meta description is long (171 characters)
Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
279 internal links, 0 external
The homepage links to 279 pages on messgewander.de and 0 external pages.
6 checks passed
One H1 headline
Your main headline reads: “MESSGEWANDER.DE”.
Title: 43 characters
Your title is a healthy 43 characters: “Kasel - Kaseln - Messgewand - Kirchenbedarf”.
Canonical URL set
The canonical URL is https://messgewander.de/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://messgewander.de/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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,851 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://messgewander.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without an H1
https://messgewander.de/collections/bestseller, https://messgewander.de/collections/empfohlen, https://messgewander.de/collections/neuheit, https://messgewander.de/collections/grun-kaseln, https://messgewander.de/collections/rote-kaseln and https://messgewander.de/collections/violette-kaseln and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://messgewander.de/collections/empfohlen and https://messgewander.de/collections/neuheit took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 107 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
15 small tap targets
15 of 60 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
1 checks passed
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.
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 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,410 words of copy
The homepage carries about 1,410 words of visible text.
3 checks passed
17 short forms
17 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 1 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.
27 other companies contacted
Loading the homepage contacts 27 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 messgewander.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Depict Search Merchandising · Gdpr Cookie Consent · Forms · trustedshops.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
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on messgewander.de, including 12 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.