Website review, no card needed

mumm-official.com logo

mumm-official.com website review

Visit site (opens in a new tab)Reviewed 8 November 202653 issues · 81 checks

This review found 53 issues worth fixing on mumm-official.com, 27 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
3.0 s2.4 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20263.0 s
Jul 18, 20262.8 s
Jul 25, 20262.7 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.7 s
Aug 22, 20262.8 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20262.9 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
239 ms184 msMay 16Oct 31196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026203 ms
May 23, 2026203 ms
May 30, 2026214 ms
Jun 6, 2026233 ms
Jun 13, 2026226 ms
Jun 20, 2026218 ms
Jun 27, 2026216 ms
Jul 4, 2026212 ms
Jul 11, 2026216 ms
Jul 18, 2026210 ms
Jul 25, 2026208 ms
Aug 1, 2026206 ms
Aug 8, 2026206 ms
Aug 15, 2026212 ms
Aug 22, 2026215 ms
Aug 29, 2026209 ms
Sep 5, 2026204 ms
Sep 12, 2026202 ms
Sep 19, 2026196 ms
Sep 26, 2026190 ms
Oct 3, 2026196 ms
Oct 10, 2026196 ms
Oct 17, 2026199 ms
Oct 24, 2026203 ms
Oct 31, 2026196 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 mumm-official.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mumm-official.com at 0.6 s0.6 s
  2. mumm-official.com at 1.2 s1.2 s
  3. mumm-official.com at 1.8 s1.8 s
  4. mumm-official.com at 2.4 s2.4 s
  5. mumm-official.com at 3.0 s3.0 s
  6. mumm-official.com at 3.6 s3.6 s
  7. mumm-official.com at 4.2 s4.2 s
  8. mumm-official.com at 4.8 s4.8 s

Speed

14 to fix17
  • Use efficient cache lifetimes

    2.5 s · 22.7 MB

    141 files are served with short cache lifetimes, so returning visitors download them again (22.7 MB).

  • Improve image delivery

    1.1 s · 6.3 MB

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

  • Reduce unused JavaScript

    4.7 s · 864 KiB

    About 864 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

  • liteshop.tw adds 1.3 s

    1.3 s

    liteshop.tw costs a phone 1.3 s of main-thread work and 28.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    3.9 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 3.9 s.

  • Mobile performance score: 17

    17/100

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

  • Main-thread work: 4.3 s

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

  • 3,331 HTML elements

    The page has 3,331 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 (liteshop.tw, Google Tag Manager and Facebook and others), adding 30.4 MB and 2.2 s of main-thread time.

  • Reduce unused CSS

    630 ms · 114 KiB

    About 114 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 630 ms faster on a phone.

  • Google Tag Manager adds 492 ms

    492 ms

    Google Tag Manager costs a phone 492 ms of main-thread work and 687 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.

  • 17 long tasks on the main thread

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

  • Facebook adds 228 ms

    228 ms

    Facebook costs a phone 228 ms of main-thread work and 318 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.

  • Other Google APIs/SDKs adds 36 ms

    36 ms

    Other Google APIs/SDKs costs a phone 36 ms of main-thread work and 506 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.

  • Legacy JavaScript

    150 ms · 32 KiB

    Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    150 ms · 11 KiB

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

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

11 to fix0
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 1.98

    1.98

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

  • Cumulative Layout Shift: 2.054

    2.054

    The layout shifts by 2.054 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 22.4 s

    22.4 s

    Your largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Time to Interactive: 36.6 s

    36.6 s

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

  • Speed Index: 12.3 s

    12.3 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user INP: 224 ms

    224 ms

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

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 s (75th percentile). 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.

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user TTFB: 521 ms

    521 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

Images and page weight

3 to fix45
  • Page weight: 33.4 MB in 212 requests

    33.4 MB

    Your homepage downloads 33.4 MB in 212 requests on a phone: images 28.0 MB (136), other files 2.2 MB (33) and scripts 1.9 MB (18). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    fjjUUeTfvHmaHFmaSLS98vNR-b2842b8c-2efc-4415-9da5-8296ffb0267 weighs 549 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    68 KiB

    1 image is downloaded at several times the size a phone draws it, for example bf89ed47-539f-4724-899d-042384310381-465f80f8-0865-4275-864e at 1,920 px wide, shown at 140 px. Resized copies would save about 68 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (72 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 9.5 g of CO₂ per visit

    9.47 g

    By the Sustainable Web Design model, a visit to your homepage emits about 9.47 g of CO₂e: 1136.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 use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 7184
  • Hidden but focusable

    130 elements hidden from screen readers can still receive keyboard focus.

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

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

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (15 elements)

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

  • Heading levels should only increase by one (2 elements)

    Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 checks passed
  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8363
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (4 characters)

    Your title is only 4 characters: “mumm”. 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.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://mumm-official.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 346 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://mumm-official.com/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

3 to fixGoogle 7385
  • 122 small tap targets

    122 of 268 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 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 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.

  • About 346 words of copy

    The homepage carries about 346 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 10 cookies set on arrival

    10

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 mumm-official.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

E-commerce
Shopify;Shopify Plus
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on mumm-official.com, including 25 speed issues, 6 SEO issues and 4 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