whileonearth.co website review

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

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

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

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

8 third-party services load with your homepage (alia-prod.com, Unpkg and rebuyengine.com and others), adding 2.2 MB and 802 ms of main-thread time.

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

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

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

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

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

Unpkg costs a phone 151 ms of main-thread work and 595 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.

rebuyengine.com costs a phone 129 ms of main-thread work and 706 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.

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

Polyfills for old browsers add 73 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).

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.

2 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 7.5 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 10.0 s (Speed Index). Good is under 3.4 s.

Real visitors wait 816 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 7.3 MB in 391 requests on a phone: images 3.6 MB (30), scripts 2.0 MB (122) and other files 1,010 KiB (191). Under 2 MB keeps phones on slow connections fast.

WOE_OURSTORY_HomepageSlider_DESKTOP_V2.jpg weighs 849 KiB. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example WOE_FieryCoralLaunch_HompageHero_MOBILE2a_2026_1001.jpg at 1,500 px wide, shown at 390 px. Resized copies would save about 665 KiB.

WOE_OURSTORY_HomepageSlider_MOBILE_V2.jpg 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 (849 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.06 g of CO₂e: 247.3 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”.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

1 image has no alt text, which hurts accessibility and image search.

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

ARIA role should be appropriate for the element: 30 elements on the page fail this check, rated minor by axe-core.

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

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.

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

The homepage links to 146 pages on whileonearth.co and 11 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://whileonearth.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://whileonearth.co/collections/mens-all, https://whileonearth.co/collections/mens-footwear and https://whileonearth.co/collections/mens-apparel use the same meta description. A description written for each page earns more clicks.

https://whileonearth.co/collections/shop-all, https://whileonearth.co/collections/mens-all, https://whileonearth.co/collections/mens-footwear and https://whileonearth.co/collections/mens-apparel have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Customer is not defined”.

Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 459 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 21 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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.