livepacha.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.0 s faster on a phone.

16 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

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

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

Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, YouTube and Shopify and others), adding 2.9 MB and 1.4 s of main-thread time.

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

YouTube costs a phone 392 ms of main-thread work and 1,018 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 122 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.

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

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

42 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 28.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “★★★★★ 3,300+ 5-STAR REVIEWS For People Who’ve Given Up on B…”.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 113 ms to 133 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.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.2 MB in 354 requests on a phone: scripts 2.8 MB (119), images 1.8 MB (34) and other files 930 KiB (147). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example Header-homepage2.webp at 3,000 px wide, shown at 360 px. Resized copies would save about 620 KiB.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 2 <h1> headlines (“As Seen On” and “Nourish Your Body & Our Planet”). One clear main headline is easier for people and search engines.

Your meta description is 210 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 59 pages on livepacha.com and 7 external pages.

https://livepacha.com/pages/regenerative-agriculture-1 and https://livepacha.com/pages/regenerative-agriculture all use the title “Regenerative Agriculture”. Search engines can't tell which page to show for a search, so each competes with the others.

https://livepacha.com/collections/pacha-best-sellers, https://livepacha.com/blogs/news, https://livepacha.com/blogs/pacha-recipes and https://livepacha.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://livepacha.com/pages/regenerative-agriculture-1 and https://livepacha.com/pages/regenerative-agriculture 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://livepacha.com/pages/regenerative-agriculture, whose canonical is https://livepacha.com/pages/regenerative-agriculture-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://livepacha.com/products/buckwheat-sourdough-loaf has no <h1> headline, so visitors and search engines get no clear main topic.

https://livepacha.com/pages/meet-our-people took over 3 s to send its HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Unexpected token ','”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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 374 words of visible text.

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