Website review, no card needed
megaloh.de website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 63 checks
This review found 38 issues worth fixing on megaloh.de, 14 of them high impact, across 63 checks. The most urgent: use efficient cache lifetimes. 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
59F- #107,704 of 110,094 reviewed websitesbeats 2%
- #62,067 of 62,514 online storesbeats 1%
- #56,730 of 57,037 Shopify storesbeats 0%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.3 s |
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.4 s
0.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.1 s
3.5 s
Speed
Use efficient cache lifetimes
3.3 s · 1,005 KiB10 files are served with short cache lifetimes, so returning visitors download them again (1,005 KiB).
Improve image delivery
2.5 s · 700 KiB9 images could be 700 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Reduce unused JavaScript
2.5 s · 377 KiBAbout 377 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Render-blocking requests
800 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
6 third-party services on the page
6 third-party services load with your homepage (Stripe, Cookie-Script.com and FontAwesome CDN and others), adding 3.2 MB and 143 ms of main-thread time.
Reduce unused CSS
310 ms · 102 KiBAbout 102 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
tickettoaster.de adds 0 ms
0 mstickettoaster.de costs a phone 0 ms of main-thread work and 2.7 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.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 86 ms. During a long task the page ignores taps.
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 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.
1 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 495 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
Cumulative Layout Shift: 1.766
1.766The layout shifts by 1.766 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 15.0 s
15.0 sYour largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “In Indigo geschrieben”.
Time to Interactive: 15.1 s
15.1 sThe page becomes fully interactive after 15.1 s. Good is under 3.8 s.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
1 checks passed
Total Blocking Time: 100 ms
100 msScripts block the page for only 100 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.6 MB in 60 requests
5.6 MBYour homepage downloads 5.6 MB in 60 requests on a phone: media 2.7 MB (2), images 1.9 MB (12) and scripts 752 KiB (15). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Ohne_Titel_1786709306.png 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).
6 images in older formats
6 images (877 KiB) are 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.
3 images below the first screen load straight away
3 images further down the page (271 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 189.1 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
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.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (7 characters)
Your title is only 7 characters: “Megaloh”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (52 characters)
Your meta description is only 52 characters: “Offizieller Ticket- und Merchandise-Shop von Megaloh”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://shop.megaloh.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.
No llms.txt
There is no https://shop.megaloh.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.
1 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.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.
2 checks passed
Tap targets are thumb-sized
14 of 16 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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 131 words
The homepage has only about 131 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
10 other companies contacted
Loading the homepage contacts 10 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 megaloh.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Plus.line AG
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on megaloh.de, including 14 speed issues, 8 SEO issues and 6 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.