mugempire.com website review

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

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

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

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

8 third-party services load with your homepage (Yotpo, Google CDN and Shopify and others), adding 375 KiB and 84 ms of main-thread time.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

About 38 KiB of CSS is downloaded but never applied on this page.

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

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

3 KiB could be saved by minifying CSS.

Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “2018 The Year I Marry The Most Awesome And Smokin' Hot Girl…”.

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

51 images have no width and height attributes, so the layout jumps as each one loads.

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

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

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.6 MB in 214 requests on a phone: images 1.2 MB (53), other files 830 KiB (109) and scripts 370 KiB (42). Under 2 MB keeps phones on slow connections fast.

36 images further down the page (952 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 63 pages on mugempire.com and 1 external page.

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.

https://mugempire.com/collections/all, https://mugempire.com/collections/best-selling/products/2018-the-year-i-marry-the-most-awesome-and-smokin-hot-girl-alive, https://mugempire.com/collections/best-selling/products/all-you-need-is-love and https://mugempire.com/collections/best-selling/products/2018-the-year-i-marry-the-most-amazing-man-alive have no meta description, so Google writes the search snippet from whatever text it finds.

https://mugempire.com/collections/best-selling/products/out-of-all-the-grand-kids, https://mugempire.com/collections/best-selling/products/im-a-math-teacher, https://mugempire.com/collections/best-selling/products/all-i-care-about-are-my-cats-and-like-maybe-3-people, https://mugempire.com/collections/best-selling/products/cats-make-me-happy, https://mugempire.com/collections/best-selling/products/i-am-silently-correcting-your-grammar and https://mugempire.com/collections/best-selling/products/the-best-nurses-are-classy-sassy-and-a-bit-smart-assy and 1 other use the same meta description. A description written for each page earns more clicks.

Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://mugempire.com/collections/best-selling/products/2018-the-year-i-marry-the-most-awesome-and-smokin-hot-girl-alive, whose canonical is https://mugempire.com/products/2018-the-year-i-marry-the-most-awesome-and-smokin-hot-girl-alive. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 644 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 and Google Tag Manager (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, 1 of them by other companies (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.