mecca.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.

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

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

reddit costs a phone 1.2 s of main-thread work and 27 KiB 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.

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

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

8 third-party services load with your homepage (reddit, Google Tag Manager and Evergage and others), adding 1.5 MB and 2.9 s of main-thread time.

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

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

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

2 images could be 621 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

11 KiB could be saved by minifying JavaScript.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

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.

Your largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Currently we only ship to Australia and New Zealand, and do…”.

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

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

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

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

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

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

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

Your homepage downloads 4.9 MB in 262 requests on a phone: scripts 3.6 MB (65), images 826 KiB (96) and HTML 198 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 6 problems, for example “Organization: sameAs is not an absolute URL ("facebook=https://www.facebook.com/MECCA/")”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 422 pages on mecca.com and 16 external pages.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.mecca.com/mecca-memo/gifting/new-holiday-beauty-products-2026, whose canonical is https://www.mecca.com/en-au/mecca-memo/gifting/new-holiday-beauty-products-2026. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.mecca.com/en-au/gifts/advent-calendars took over 3 s to send its HTML from our server.

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

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

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

1 image is served at too low a resolution for sharp phone screens.

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

Large scripts ship without source maps.

Social proof on the homepage: “250,000+ reviews”. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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 482 words of visible text.

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

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