1thrive.com website review

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

8 third-party services load with your homepage (Shopify, maestra-static.io and Cloudflare CDN and others), adding 13.1 MB and 749 ms of main-thread time.

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

Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.

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

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

About 345 KiB of JavaScript is downloaded but never used on this page.

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

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

maestra-static.io costs a phone 213 ms of main-thread work and 299 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.

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

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

About 33 KiB of CSS is downloaded but never applied on this page.

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.

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

3 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “These Are All Words Our 1THRIVE Community Has Used To Descr…”. Most of its time is element render delay (2.5 s).

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

Your homepage downloads 16.1 MB in 295 requests on a phone: media 11.9 MB (3), scripts 1.3 MB (70) and images 1.2 MB (43). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

13 tap targets are too small or too close together to hit reliably with a finger.

4 elements hidden from screen readers can still receive keyboard focus.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Your meta description is 313 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.

Your <h1> is empty.

The homepage links to 170 pages on 1thrive.com and 5 external pages.

/products/wall-organizer-gift-card is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/collections/all, /policies/shipping-policy, /pages/design-your-own-command-center, /pages/corporate-sales, /pages/ideas and /products/wall-organizer-gift-card and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/design-your-own-command-center, /pages/corporate-sales, /pages/ideas and /pages/gift-guide have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 image is served at too low a resolution for sharp phone screens.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

1thrive.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

1thrive.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 1,118 words of visible text.

DMARC is set to p=none, so mail pretending to be 1thrive.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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