Website review, no card needed

mbg-amberroom.com logo

mbg-amberroom.com website review

Visit site (opens in a new tab)Reviewed 13 November 202636 issues · 85 checks

This review found 36 issues worth fixing on mbg-amberroom.com, 15 of them high impact, across 85 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.5 s1.2 sMay 23Nov 71.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Nov 7, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
153 ms128 msMay 23Nov 7143 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026131 ms
May 30, 2026138 ms
Jun 6, 2026144 ms
Jun 13, 2026145 ms
Jun 20, 2026144 ms
Jun 27, 2026139 ms
Jul 4, 2026138 ms
Jul 11, 2026139 ms
Jul 18, 2026138 ms
Jul 25, 2026142 ms
Aug 1, 2026144 ms
Aug 8, 2026146 ms
Aug 15, 2026150 ms
Aug 22, 2026147 ms
Aug 29, 2026146 ms
Sep 5, 2026146 ms
Sep 12, 2026142 ms
Sep 19, 2026142 ms
Sep 26, 2026142 ms
Oct 3, 2026139 ms
Oct 10, 2026141 ms
Oct 17, 2026143 ms
Oct 24, 2026144 ms
Oct 31, 2026144 ms
Nov 7, 2026143 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

Full-page screenshot of mbg-amberroom.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mbg-amberroom.com at 0.9 s0.9 s
  2. mbg-amberroom.com at 1.8 s1.8 s
  3. mbg-amberroom.com at 2.7 s2.7 s
  4. mbg-amberroom.com at 3.6 s3.6 s
  5. mbg-amberroom.com at 4.5 s4.5 s
  6. mbg-amberroom.com at 5.4 s5.4 s
  7. mbg-amberroom.com at 6.3 s6.3 s
  8. mbg-amberroom.com at 7.2 s7.2 s

Speed

13 to fix38
  • Improve image delivery

    8.0 s · 1.2 MB

    30 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.0 s faster on a phone.

  • Main-thread work: 12.5 s

    A phone's processor spends 12.5 s on main-thread work while loading, 4.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Render-blocking requests

    1.1 s

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 38

    38/100

    Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 3,738 HTML elements

    The page has 3,738 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, cloudfront.net and Shopify and others), adding 1.4 MB and 2.3 s of main-thread time.

  • Klaviyo adds 684 ms

    684 ms

    Klaviyo costs a phone 684 ms of main-thread work and 618 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.

  • cloudfront.net adds 509 ms

    509 ms

    cloudfront.net costs a phone 509 ms of main-thread work and 99 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

    300 ms · 95 KiB

    About 95 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.

  • Shopify adds 309 ms

    309 ms

    Shopify costs a phone 309 ms of main-thread work and 445 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 JavaScript

    337 KiB

    About 337 KiB of JavaScript is downloaded but never used on this page.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 321 ms. During a long task the page ignores taps.

  • Clarity adds 265 ms

    265 ms

    Clarity costs a phone 265 ms of main-thread work and 28 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.

  • Use efficient cache lifetimes

    181 KiB

    21 files are served with short cache lifetimes, so returning visitors download them again (181 KiB).

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 15 ms

    15 ms

    Your server sent the HTML in 15 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 25.2 s

    25.2 s

    Your largest element takes 25.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MBG Amber Room”.

  • Time to Interactive: 45.7 s

    45.7 s

    The page becomes fully interactive after 45.7 s. Good is under 3.8 s.

  • Speed Index: 11.0 s

    11.0 s

    Visually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 1.8 s

    1.8 s

    Scripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 131 ms to 143 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s 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.6 s

    1.6 s

    Real visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 146 ms

    146 ms

    Real visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 596 ms

    596 ms

    Real visitors wait 596 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

6 to fix19
  • Page weight: 26.1 MB in 318 requests

    26.1 MB

    Your homepage downloads 26.1 MB in 318 requests on a phone: media 14.4 MB (1), images 9.5 MB (108) and scripts 1.2 MB (106). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    3.6 MB

    6 images are downloaded at several times the size a phone draws them, for example goldberg-banner-accessoires-desktop.webp at 3,200 px wide, shown at 390 px. Resized copies would save about 3.6 MB.

  • 40 images in older formats

    40 images (11.3 MB) 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.

  • 10 images below the first screen load straight away

    10 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    goldberg-banner-accessoires-desktop.webp 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 7.4 g of CO₂ per visit

    7.41 g

    By the Sustainable Web Design model, a visit to your homepage emits about 7.41 g of CO₂e: 889.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fixGoogle 9493
  • 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 (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 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.

  • 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.

  • 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.

  • 16 links without text

    16 visible links have no text or label, so screen readers cannot say where they go.

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

Google 92100
  • 240 internal links, 5 external

    The homepage links to 240 pages on mbg-amberroom.com and 5 external pages.

8 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “MBG Amber Room Onlineshop für Spirituosen, Wein & Feinkost. Entdecke Marken und Produkte für verschiedene Anlässe - ein…”.

  • One H1 headline

    Your main headline reads: “Unser X-MAS Bestseller”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “MBG Amber Room | Spirituosen, Wein & Feinkost online ...”.

  • Canonical URL set

    The canonical URL is https://mbg-amberroom.com/.

  • Structured data in place

    Structured data found: Organization 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://mbg-amberroom.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,196 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://mbg-amberroom.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 6 linked pages hidden from search

    https://mbg-amberroom.com/collections/scavi-ray-geschenke, https://mbg-amberroom.com/collections/scavi-ray-accessoires, https://mbg-amberroom.com/collections/scavi-ray-bundles, https://mbg-amberroom.com/collections/scavi-ray-feinkost, https://mbg-amberroom.com/collections/scavi-ray-kunstflaschen and https://mbg-amberroom.com/collections/9-mile-vodka-flaschen are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 94 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 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

    49 of 54 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 634 words of copy

    The homepage carries about 634 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop” and “GOLDBERGCOCKTAIL ESSENTIALS BOOK 25,00 €”.

  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 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.

  • 43 other companies contacted

    Loading the homepage contacts 43 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 mbg-amberroom.com, 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

Pandectes Gdpr · Dr Free Gift · Uppromote Affiliate · Ai Index Pro · Klaviyo Email Marketing Sms · Microsoft Clarity · Gdpr Cookie Consent · Affliate By Secomapp · Checkout Regeln Grosse Warenkoerbe 2026 · loox.io · trustpilot.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
Bootstrap
E-commerce
Shopify
Analytics
Google Tag Manager | 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 36 issues on mbg-amberroom.com, including 17 speed 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25