tryrrwellness.com website review

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

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

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

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

8 third-party services load with your homepage (OptiMonk, Klaviyo and Google CDN and others), adding 2.9 MB and 860 ms of main-thread time.

7 images could be 671 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

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

OptiMonk costs a phone 269 ms of main-thread work and 340 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.

Klaviyo costs a phone 206 ms of main-thread work and 382 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 48 ms of main-thread work and 1.7 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.

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

podium.com costs a phone 123 ms of main-thread work and 302 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 237 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.

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

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

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

17 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “New Pure Bliss Gummies Discover a gentle balance of calm, c…”.

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

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

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

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

Scripts block taps and scrolling for 293 ms 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 9.9 MB in 380 requests on a phone: media 4.5 MB (3), images 2.3 MB (61) and scripts 1.4 MB (109). Under 2 MB keeps phones on slow connections fast.

19 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

11 images are downloaded at several times the size a phone draws them, for example c21edd17bd3336ad0fbf9cb36bea7cea58fdba2e.jpg at 1,100 px wide, shown at 350 px. Resized copies would save about 408 KiB.

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

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

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

ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

46 links have no real href, so search engines can't follow them.

There are 2 <h1> headlines (“New Pure Bliss Gummies” and “Lasting Relief”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//tryrrwellness.com/cdn/shop/t/4/assets/RR-reskin-nav_A…”.

The homepage links to 172 pages on tryrrwellness.com and 8 external pages.

/pages/contact has no meta description, so Google writes the search snippet from whatever text it finds.

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

6 errors were logged to the browser console while the page loaded, for example “WebFont is not defined”.

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

7 links from your homepage to your own site are broken, for example https://tryrrwellness.com/pages/cbd-101 (404).

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.

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

tryrrwellness.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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 963 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 Klaviyo (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 13 cookies, 1 of them by other companies (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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.