wellpeople.com website review

43 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).

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

Signyfyd costs a phone 1.2 s of main-thread work and 265 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.

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

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

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

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

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

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

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

100 KiB could be saved by minifying JavaScript.

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

vidjet.io costs a phone 153 ms of main-thread work and 2.4 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.

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

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

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

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

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.

4 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

Your homepage downloads 8.9 MB in 329 requests on a phone: media 3.6 MB (4), scripts 2.0 MB (115) and images 1.7 MB (66). Under 2 MB keeps phones on slow connections fast.

3 images (827 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.

1 image is downloaded at several times the size a phone draws it, for example kustomer-icon-wp_1.gif at 390 px wide, shown at 49 px. Resized copies would save about 113 KiB.

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

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

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

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 75 characters, so Google will cut it off around 60: “Well People: Clean Beauty, Award Winning Makeup and Skin Care | Well People”.

There are 4 <h1> headlines (“Well People”, “Enter a Gleamstate” and “Lash Expression,”). One clear main headline is easier for people and search engines.

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

The homepage links to 161 pages on wellpeople.com and 20 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.wellpeople.com/blogs/articles has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wellpeople.com/products/gleamstate-brightening-serum-concealer, https://www.wellpeople.com/blogs/articles, https://www.wellpeople.com/pages/about-us and https://www.wellpeople.com/pages/find-your-shade have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Social proof on the homepage: 36 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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