mbx.co website review

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

13 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Framer CDN costs a phone 485 ms of main-thread work and 8.1 MB 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.

17 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

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

About 982 KiB of JavaScript is downloaded but never used on this page.

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

Google CDN costs a phone 411 ms of main-thread work and 1.1 MB 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 Tag Manager costs a phone 188 ms of main-thread work and 308 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.

maily.so costs a phone 72 ms of main-thread work and 1.2 MB 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 Fonts costs a phone 7 ms of main-thread work and 508 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.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

14 KiB could be saved by minifying CSS.

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.

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

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

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

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MBX uses analytics cookies, including Google Analytics and …”. Most of its time is element render delay (2.4 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 11.7 MB in 223 requests on a phone: fonts 4.1 MB (22), images 3.8 MB (68) and scripts 3.0 MB (111). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example UiXFggW1JDspVmMNVXCdKxH8EI.png at 3,777 px wide, shown at 33 px. Resized copies would save about 1.0 MB.

UiXFggW1JDspVmMNVXCdKxH8EI.png weighs 548 KiB. On a phone connection a single image that size takes seconds.

4 images further down the page (109 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 3.31 g of CO₂e: 397.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 tap target is too small or too close together to hit reliably with a finger.

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.

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

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

There are 4 <h1> headlines (“nooni”, “nooni” and “nooni”). One clear main headline is easier for people and search engines.

The homepage links to 51 pages on mbx.co and 78 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.

There is no https://mbx.co/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://mbx.co/about, https://mbx.co/contact, https://mbx.co/culture, https://mbx.co/faq, https://mbx.co/privacy-policy and https://mbx.co/cookie-policy all use the title “MBX | Memebox Corporation”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mbx.co/about, https://mbx.co/contact, https://mbx.co/culture, https://mbx.co/faq, https://mbx.co/privacy-policy and https://mbx.co/cookie-policy use the same meta description. A description written for each page earns more clicks.

https://mbx.co/brand, https://mbx.co/about, https://mbx.co/contact, https://mbx.co/culture and https://mbx.co/cookie-policy have no <h1> headline, so visitors and search engines get no clear main topic.

https://mbx.co/faq and https://mbx.co/privacy-policy have 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.

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

7 of 17 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 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 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 196 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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 Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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