mambos.store website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.6 MB and 1.4 s of main-thread time.

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

22 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

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

Google CDN costs a phone 465 ms of main-thread work and 733 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.

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

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

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

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

3 images could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Desktop scores 67 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying CSS.

Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mambo's Online Store”.

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

The first text or image appears after 5.4 s on a phone. Good is under 1.8 s.

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

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

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

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

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.

Your homepage downloads 2.8 MB in 129 requests on a phone: scripts 1.8 MB (72), other files 389 KiB (18) and images 366 KiB (13). Under 2 MB keeps phones on slow connections fast.

5 images (212 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.

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

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

99 tap targets are too small or too close together to hit reliably with a finger.

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

Links must have discernible text: 15 elements on the page fail this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 20 characters: “Mambo's Online Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("wp-content/uploads/2021/10/isle-scaled-Recovered.jpg")”.

3 links have no real href, so search engines can't follow them.

The homepage links to 219 pages on mambos.store and 8 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://mambos.store/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.

https://mambos.store/shop, https://mambos.store/product-category/home-outdoor, https://mambos.store/product-category/home-outdoor/tables-home-outdoor, https://mambos.store/product-category/outdoor-leisure, https://mambos.store/product-category/kiddies/educational and https://mambos.store/product-category/kiddies/arts-n-crafts and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 72 found) and read each the way a search engine does.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

2 images are served at too low a resolution for sharp phone screens.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 501 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

Opening the homepage sets 6 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.