mojosw.com website review

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

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

8 third-party services load with your homepage (alia-prod.com, Shopify and cloudfront.net and others), adding 2.3 MB and 1.5 s of main-thread time.

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

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

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

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

alia-prod.com costs a phone 492 ms of main-thread work and 369 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.

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

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

Shopify costs a phone 192 ms of main-thread work and 927 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.

cloudfront.net costs a phone 185 ms of main-thread work and 367 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.

smile.io costs a phone 81 ms of main-thread work and 368 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 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

29 KiB could be saved by minifying JavaScript.

17 KiB JavaScript is shipped twice across bundles.

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 page becomes fully interactive after 23.1 s. Good is under 3.8 s.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.8 MB in 300 requests on a phone: scripts 2.0 MB (150), images 1.2 MB (25) and other files 1.1 MB (104). Under 2 MB keeps phones on slow connections fast.

MojoDayONE-286.png 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).

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

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

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

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.

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

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

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

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

Your title is 76 characters, so Google will cut it off around 60: “Mojo Performance and Lifestyle | Get Your Mojo On! – Mojo Sportswear Company”.

The homepage links to 141 pages on mojosw.com and 12 external pages.

https://www.mojosportswearcompany.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.mojosportswearcompany.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.mojosportswearcompany.com/customer_authentication/redirect, https://www.mojosportswearcompany.com/collections/fresh-off-the-boat, https://www.mojosportswearcompany.com/collections/best-sellers, https://www.mojosportswearcompany.com/collections/the-add-ons, https://www.mojosportswearcompany.com/blogs/the-insider-review and https://www.mojosportswearcompany.com/collections/americana-collection and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mojosportswearcompany.com/customer_authentication/redirect, https://www.mojosportswearcompany.com/pages/pro-staff, https://www.mojosportswearcompany.com/pages/collaborators and https://www.mojosportswearcompany.com/collections/mens have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Social proof on the homepage: a star rating. 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 556 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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 29 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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.