lightlife.com website review

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

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

About 866 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.8 MB and 860 ms of main-thread time.

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

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

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

Google CDN costs a phone 269 ms of main-thread work and 733 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.

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

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

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

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Desktop scores 77 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Real visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Your largest element takes 10.8 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.2 s. Good is under 3.8 s.

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

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

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

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 4.1 MB in 136 requests on a phone: scripts 2.0 MB (57), images 1.1 MB (27) and fonts 417 KiB (9). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.16 g of CO₂e: 138.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is only 9 characters: “LightLife”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 86 pages on lightlife.com and 9 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 /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.

/, /en_ca and /fr_ca all use the title “LightLife”. Search engines can't tell which page to show for a search, so each competes with the others.

/product/smart-bacon, /product/smart-dogs, /product/smart-ground-original and /product/smoky-tempeh-strips have no meta description, so Google writes the search snippet from whatever text it finds.

/our-food, /tempeh-products, /recipes, /where-to-buy-2, /our-story and /tempehfy and 3 others use the same meta description. A description written for each page earns more clicks.

/en_ca and /fr_ca have no <h1> headline, so visitors and search engines get no clear main topic.

/tempehfy took over 3 s to send its HTML from our server.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 326 words of visible text.

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