mubo.co website review

About 415 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, amaicdn.com and Unpkg and others), adding 848 KiB and 585 ms of main-thread time.

Google Tag Manager costs a phone 443 ms of main-thread work and 602 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 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

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

1 image could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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_9d798ad7-c378-49b7-94bd-2b67aa52abbb_3500x.jpg weighs 607 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 1_9d798ad7-c378-49b7-94bd-2b67aa52abbb_3500x.jpg at 3,280 px wide, shown at 390 px. Resized copies would save about 530 KiB.

Your homepage downloads 2.3 MB in 161 requests on a phone: scripts 945 KiB (48), other files 677 KiB (82) and images 657 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 13 characters: “Mubo Boutique”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 18 pages on mubo.co and 6 external pages.

Your homepage links to https://www.mubo.co/a/returns, which answers with an error. Visitors hit a dead end and search engines drop it.

/ and https://www.mubo.co/a/faq all use the title “Mubo Boutique”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mubo.co/collections/mubo-monday-drops-mubomonday, https://www.mubo.co/collections/graphic-tees-sweatshirts, https://www.mubo.co/a/faq, https://www.mubo.co/policies/terms-of-service and https://www.mubo.co/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Error from API: undefined”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 97 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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.

Opening the homepage sets 11 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.