Website review, no card needed
meama.at website review
Visit site (opens in a new tab)Reviewed 10 November 202633 issues · 78 checks
This review found 33 issues worth fixing on meama.at, 9 of them high impact, across 78 checks. The most urgent: avoid multiple page redirects. 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
One score from every part of this review. How it works
Speed
Avoid multiple page redirects
3.0 sThe page goes through 2 redirects before it starts loading, costing about 3.0 s. Link and advertise the final URL directly.
8 third-party services on the page
8 third-party services load with your homepage (meama.de, Clarity and Klaviyo and others), adding 8.4 MB and 907 ms of main-thread time.
Reduce unused JavaScript
750 ms · 424 KiBAbout 424 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
meama.de adds 258 ms
258 msmeama.de costs a phone 258 ms of main-thread work and 7.4 MB 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.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
450 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Use efficient cache lifetimes
100 ms · 331 KiB20 files are served with short cache lifetimes, so returning visitors download them again (331 KiB).
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 145 ms
145 msKlaviyo costs a phone 145 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.
Reduce unused CSS
230 ms · 72 KiBAbout 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 230 ms faster on a phone.
Document request latency
200 msThe HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Minify CSS
80 ms · 8 KiB8 KiB could be saved by minifying CSS.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.
Improve image delivery
74 KiB3 images could be 74 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.5 s
8.5 sYour largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Video laden:”.
Time to Interactive: 14.9 s
14.9 sThe page becomes fully interactive after 14.9 s. Good is under 3.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 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.
2 checks passed
Total Blocking Time: 97 ms
97 msScripts block the page for only 97 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 9.5 MB in 313 requests
9.5 MBYour homepage downloads 9.5 MB in 313 requests on a phone: media 5.8 MB (1), scripts 1.3 MB (105) and images 1.0 MB (32). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
9ceef2cc-7af5-46be-9e4f-d971542d317f.png weighs 606 KiB. On a phone connection a single image that size takes seconds.
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).
1 image in older formats
1 image (606 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 2.7 g of CO₂ per visit
2.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.69 g of CO₂e: 323.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
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.
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
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Premium Kaffeekapseln, Teekapseln & Kapselmaschinen - MEAMA – Meama.at”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Meama.at Meama.at”, “Meama” and “Kaffeekapseln, Tee & mehr”). One clear main headline is easier for people and search engines.
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.
81 internal links, 6 external
The homepage links to 81 pages on meama.at and 6 external pages.
4 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Kaffee & Tee in Kapseln neu gedacht: Meama steht für exzellenten Geschmack, hochwertige Qualität, elegantes Design und …”.
Canonical URL set
The canonical URL is https://meama.at/.
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.at/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 (838 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://meama.at/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://meama.at/pages/multikapsel-vorteile has 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 37 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
3 JavaScript errors while loading
3 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”.
1 call to action
The homepage has 1 call to action, for example “Try Meama”.
5 short forms
5 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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 6 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.
37 other companies contacted
Loading the homepage contacts 37 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.at, 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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · rechargecdn.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
- 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 33 issues on meama.at, including 14 speed issues, 4 SEO 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.