sentelabs.com website review

hcaptcha.com costs a phone 4.2 s of main-thread work and 4.3 MB 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.

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

14 images could be 371 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

8 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Google CDN and others), adding 7.7 MB and 6.5 s of main-thread time.

About 3.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 280 ms faster on a phone.

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

Google Tag Manager costs a phone 943 ms of main-thread work and 1,005 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.

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

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

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

Yotpo costs a phone 234 ms of main-thread work and 554 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.

Facebook costs a phone 256 ms of main-thread work and 284 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 1,742 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

29 KiB could be saved by minifying JavaScript.

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

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.

For real visitors the layout shifts by 1.00 (75th percentile). Good is under 0.1.

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

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

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

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

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Home Hero Top Image”.

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

8 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' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.2 MB in 426 requests on a phone: scripts 7.7 MB (152), HTML 1.8 MB (11) and other files 1.1 MB (164). Under 2 MB keeps phones on slow connections fast.

logo--white.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

4 buttons have no accessible name, so screen readers announce just “button”.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

6 images have no alt text, which hurts accessibility and image search.

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

14 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

There are 3 <h1> headlines (“Setting the Standard in Skin Health”, “Your Skincare Regimen” and “The Senté Difference”). One clear main headline is easier for people and search engines.

The homepage links to 132 pages on sentelabs.com and 5 external pages.

There is no https://sentelabs.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://sentelabs.com/pages/sente-skincare-quiz has no <h1> headline, so visitors and search engines get no clear main topic.

https://sentelabs.com/collections/fine-lines-and-wrinkles took over 3 s to send its HTML from our server.

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Social proof on the homepage: 45 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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