trycharlottesweb.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.6 s faster on a phone.

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

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

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

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

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

hsappstatic.net costs a phone 538 ms of main-thread work and 715 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 500 ms.

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

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

Google Tag Manager costs a phone 388 ms of main-thread work and 348 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,786 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

4 images could be 244 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 19 KiB JavaScript that modern phones do not need.

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

3 KiB could be saved by minifying JavaScript.

Your largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Charlotte's Web broad-spectrum hemp products for Sleep, Cal…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.9 MB in 358 requests on a phone: scripts 2.7 MB (106), fonts 1.1 MB (32) and images 939 KiB (44). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

The robots meta tag says “noindex”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

Your title is 82 characters, so Google will cut it off around 60: “Charlotte's Web | The Worlds Most Trusted Hemp – Charlotte's Web Hemp & Botanicals”.

There are 2 <h1> headlines (“” and “Broad-Spectrum Support for Daily Wellness”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 152 pages on trycharlottesweb.com and 2 external pages.

There is no https://www.trycharlottesweb.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.

Your homepage links to https://www.trycharlottesweb.com/collections/all-products, https://www.trycharlottesweb.com/collections/sleep and https://www.trycharlottesweb.com/collections/calm, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.trycharlottesweb.com/collections/the-california-collection is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, Klaviyo and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 cookies (measured from a US location before any click).

Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.