whatmoreeee.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 9.4 s faster on a phone.

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

The page goes through 1 redirect before it starts loading, costing about 2.3 s. Link and advertise the final URL directly.

Your mobile performance score is 38. 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 CDN, Google Tag Manager and laylo.com and others), adding 2.5 MB and 1.3 s of main-thread time.

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

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

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

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

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

cartcoders.com costs a phone 109 ms of main-thread work and 297 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 KiB could be saved by minifying JavaScript.

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

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

13 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 45.3 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 46.9 s. Good is under 3.8 s.

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

Scripts block taps and scrolling for 723 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.

Your homepage downloads 9.3 MB in 256 requests on a phone: scripts 3.1 MB (79), fonts 2.7 MB (6) and other files 2.6 MB (126). Under 2 MB keeps phones on slow connections fast.

WHATMORE-Logo-white_08293525-bfbc-472c-8bf4-4e68aef6fc2a.web is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (36 KiB) is 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.

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

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

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

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.

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

button, link, and menuitem elements do not have accessible names. (1 element).

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

Your title is only 22 characters: “Mainfactor Merch Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your canonical URL points to mainfactormerch.com, not whatmoreeee.com, so Google may credit that host instead.

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

Your meta description is only 63 characters: “Official Merchandise: T-Shirts, hoodies, accessories, and more!”. 70 to 160 characters is enough to sell the click.

1 link has no real href, so search engines can't follow it.

The homepage links to 35 pages on whatmoreeee.com and 24 external pages.

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.

/collections/all, /collections/boy-golden and /collections/songsbyjoan have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/mf-superstore-featured-collection/products/the-best-of-friends-cd and /collections/mf-superstore-featured-collection/products/the-best-of-friends-vinyl use the same meta description. A description written for each page earns more clicks.

/collections/boy-golden, /collections/songsbyjoan, /collections/katherine-li and /collections/the-high-mighty-merch have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/the-high-mighty-merch has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/collections/all, /pages/contact, /collections/boy-golden, /collections/songsbyjoan, /collections/mf-superstore-featured-collection/products/unisex-garment-dyed-pocket-t-shirt and /collections/mf-superstore-featured-collection/products/royksopp-logo-tote and 6 others took over 3 s to send their HTML from our server.

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

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”).

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 has only about 72 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 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 7 cookies, 2 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.