trilogyproducts.com website review

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

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

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

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

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

About 133 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 548 ms of main-thread work and 333 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 458 ms of main-thread work and 771 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 395 KiB of JavaScript is downloaded but never used on this page.

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

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

TikTok costs a phone 259 ms of main-thread work and 169 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.

9 images could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a woman holding a dropper”.

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

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

Your homepage downloads 4.1 MB in 395 requests on a phone: scripts 1.7 MB (187), other files 939 KiB (142) and images 791 KiB (38). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 349961c0-6cce-4349-84cc-aeaf747a85bd.png at 4,594 px wide, shown at 109 px. Resized copies would save about 115 KiB.

1 image (115 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 1.17 g of CO₂e: 140.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h6, h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 85 characters, so Google will cut it off around 60: “Trilogy Skincare | Force of Nature | Free Shipping $60+ – Trilogy Natural Products US”.

The homepage links to 258 pages on trilogyproducts.com and 15 external pages.

There is no https://www.trilogyproducts.com/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://www.trilogyproducts.com/collections/all, https://www.trilogyproducts.com/collections/shop-best-sellers, https://www.trilogyproducts.com/collections/new-arrivals, https://www.trilogyproducts.com/collections/cleansers, https://www.trilogyproducts.com/collections/exfoliate-and-tone and https://www.trilogyproducts.com/collections/serums-treatments have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Unexpected token '<'”.

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