lifeboostcoffee.net website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Vimeo and others), adding 2.2 MB and 879 ms of main-thread time.

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

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

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

Google Tag Manager costs a phone 252 ms of main-thread work and 398 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.

Shopify costs a phone 238 ms of main-thread work and 417 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 images could be 276 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Vimeo costs a phone 167 ms of main-thread work and 1.0 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.

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

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

About 65 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.

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

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

3 KiB could be saved by minifying JavaScript.

Your largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Secure Your Supply of Our Delicious, Immune-Boosting, Low-A…”.

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

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

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

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

Scripts block taps and scrolling for 276 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 8.9 MB in 310 requests on a phone: images 5.5 MB (102), scripts 2.4 MB (139) and fonts 467 KiB (11). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.0 MB together. 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 inc500logo_nobg.svg at 2,746 px wide, shown at 180 px. Resized copies would save about 1.2 MB.

36 images further down the page (4.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

18 images (2.7 MB) 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 2.53 g of CO₂e: 304.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://lifeboostcoffee.com)”.

2 links have no real href, so search engines can't follow them.

The homepage links to 147 pages on lifeboostcoffee.net and 27 external pages.

https://lifeboostcoffee.net/collections/bean-blonde, https://lifeboostcoffee.net/collections/bean-medium, https://lifeboostcoffee.net/collections/bean-dark, https://lifeboostcoffee.net/collections/bean-midnight, https://lifeboostcoffee.net/collections/beans and https://lifeboostcoffee.net/collections/ground and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://lifeboostcoffee.net/blogs/lifeboost and https://lifeboostcoffee.net/collections/all-products-new have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://lifeboostcoffee.net/pages/healthy-coffee-ot2e-19-cp-net?_su_rec=XM7LZ-ZESS53n3vqdcizPQiRwG_FWJG2pjNmUYekBnO5Bi5BR2sFhHfRifSydJdZDMdcHnbz2jyNiNZFPsesnhl3OXofDYjryFsaLKNgYyrLFox2bse5vMQumdhqhdN4.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “window.Shopify.loadFeatures is not a function”.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 2,277 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Tag Manager, Klaviyo and Microsoft Ads and 4 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 51 cookies, 5 of them by other companies (measured from a US location before any click).

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