lifestraw.com website review

audioeye.com costs a phone 1.6 s of main-thread work and 349 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.

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

8 third-party services load with your homepage (audioeye.com, Klaviyo and POWr and others), adding 1.6 MB and 2.3 s of main-thread time.

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

22 images could be 459 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.

Your mobile performance score is 52 (desktop: 66). Pages that score under 90 lose visitors before the first paint.

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

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

Klaviyo costs a phone 222 ms of main-thread work and 612 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.

rechargecdn.com costs a phone 64 ms of main-thread work and 296 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.

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

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

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

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

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

23 KiB could be saved by minifying JavaScript.

6 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.

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 9.7 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 21.1 s. Good is under 3.8 s.

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

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

For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.

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

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

The layout shifts by 0.115 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your homepage downloads 17.3 MB in 331 requests on a phone: media 12.6 MB (2), images 1.9 MB (104) and scripts 1.8 MB (110). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (367 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (239 KiB) are 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 4.92 g of CO₂e: 589.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

Your title is 81 characters, so Google will cut it off around 60: “Water Filters & Water Purifiers | LifeStraw | LifeStraw Water Filters & Purifiers”.

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

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

The homepage links to 240 pages on lifestraw.com and 20 external pages.

https://lifestraw.com/pages/tracking and https://lifestraw.com/collections/replacement-spares-for-lifestraw-home use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://lifestraw.com/pages/impact-report-2024, whose canonical is https://lifestraw.com/pages/impact-report-2025. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lifestraw.com/pages/impact-report-2024 and https://lifestraw.com/pages/tracking have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://lifestraw.com/.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 1,200 words of visible text.

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