Website review, no card needed
meama.de website review
Visit site (opens in a new tab)Reviewed 11 November 202626 issues · 72 checks
This review found 26 issues worth fixing on meama.de, 7 of them high impact, across 72 checks. The most urgent: page weight: 9.1 MB in 256 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
85B- #14,749 of 107,794 reviewed websitesbeats 82%
- #9,388 of 61,005 online storesbeats 79%
- #9,132 of 55,667 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused JavaScript
450 ms · 424 KiBAbout 424 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.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Clarity and rechargecdn.com and others), adding 987 KiB and 581 ms of main-thread time.
Use efficient cache lifetimes
100 ms · 370 KiB19 files are served with short cache lifetimes, so returning visitors download them again (370 KiB).
Reduce unused CSS
300 ms · 72 KiBAbout 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 146 ms
146 msKlaviyo costs a phone 146 ms of main-thread work and 311 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.
Minify CSS
150 ms · 8 KiB8 KiB could be saved by minifying CSS.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 89 ms. During a long task the page ignores taps.
Improve image delivery
73 KiB2 images could be 73 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Video laden:”.
Speed Index: 4.6 s
4.6 sVisually, the page fills in at 4.6 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.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Total Blocking Time: 119 ms
119 msScripts block the page for only 119 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
Images and page weight
Page weight: 9.1 MB in 256 requests
9.1 MBYour homepage downloads 9.1 MB in 256 requests on a phone: media 5.8 MB (1), scripts 1.1 MB (89) and images 1,003 KiB (20). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
d1d4b5b07eec4cfda73354acbf75c4d4.thumbnail.0000000000.jpg 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 2.6 g of CO₂ per visit
2.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.57 g of CO₂e: 308.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 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
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
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.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
73 internal links, 6 external
The homepage links to 73 pages on meama.de and 6 external pages.
8 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Entdecke die Welt von Meama: Hochwertige Kapselmaschinen, Kaffeekapseln und Teekapseln für ein unvergleichliches Geschm…”.
One H1 headline
Your main headline reads: “MEAMA MEAMA”.
Title: 57 characters
Your title is a healthy 57 characters: “MEAMA Premium Kaffeekapseln, Teekapseln & Kapselmaschinen”.
Canonical URL set
The canonical URL is https://meama.de/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage, ImageObject, WebPage 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://meama.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 (498 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://meama.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://meama.de/pages/try-meama-multi-kapseln, https://meama.de/pages/about-meama, https://meama.de/blogs/news, https://meama.de/pages/for-businesses, https://meama.de/collections/all-capsules and https://meama.de/collections/standard-capsule-coffee and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://meama.de/pages/try-meama-multi-kapseln, https://meama.de/pages/about-meama, https://meama.de/pages/for-businesses, https://meama.de/collections/all-capsules, https://meama.de/collections/standard-capsule-coffee and https://meama.de/collections/multi-capsules-coffee 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 32 found) and read each the way a search engine does.
5 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
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 7 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 “Unexpected token 'function'”.
2 checks passed
Tap targets are thumb-sized
21 of 23 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 288 words of copy
The homepage carries about 288 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Try Meama”.
5 calls to action
The homepage has 5 calls to action, for example “Try Meama” and “Try MeamaTry Meama”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
33 other companies contacted
Loading the homepage contacts 33 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 meama.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Uppromote Affiliate · Tolstoy · Klaviyo Email Marketing Sms · Yoast Seo · Affliate By Secomapp · activehosted.com · trustpilot.com · pop-convert.com · rechargecdn.com · beeapp.me · good-apps.co
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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on meama.de, including 12 speed issues and 2 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.