setactive.co website review

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

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

About 1.5 MB of JavaScript is downloaded but never used on this page.

8 third-party services load with your homepage (route.com, Clarity and rebuyengine.com and others), adding 2.9 MB and 1.2 s of main-thread time.

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

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

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

route.com costs a phone 467 ms of main-thread work and 1.1 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.

486 KiB JavaScript is shipped twice across bundles.

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

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

rebuyengine.com costs a phone 154 ms of main-thread work and 735 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 78 ms of main-thread work and 556 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 88 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.

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

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

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

2 KiB could be saved by minifying JavaScript.

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

Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

3 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 153 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.7 MB in 561 requests on a phone: scripts 3.0 MB (232), images 1.7 MB (47) and other files 1.3 MB (230). Under 2 MB keeps phones on slow connections fast.

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

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your page has no <title>, so Google has to invent the blue link in search results.

No meta description, so Google writes its own snippet from whatever text it finds.

There are 2 <h1> headlines (“” and “OFF-DUTY LOOKS GOOD ON YOU.”). One clear main headline is easier for people and search engines.

Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or ']' after array element in JSON at position )”.

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

The homepage links to 495 pages on setactive.co and 11 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://setactive.co/products/luxform-lux-baseline-tank-onyx, https://setactive.co/products/formcloud-cloud-duo-stripe-halter-tank-onyx, https://setactive.co/products/aeraline-breathe-cross-cami-onyx, https://setactive.co/collections/all-products, https://setactive.co/collections/activewear and https://setactive.co/collections/basics and 9 others have no <title>, so Google invents the link text in results.

https://setactive.co/products/luxform-lux-baseline-tank-onyx, https://setactive.co/products/formcloud-cloud-duo-stripe-halter-tank-onyx and https://setactive.co/products/aeraline-breathe-cross-cami-onyx are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://setactive.co/products/luxform-lux-baseline-tank-onyx, https://setactive.co/products/formcloud-cloud-duo-stripe-halter-tank-onyx, https://setactive.co/products/aeraline-breathe-cross-cami-onyx, https://setactive.co/collections/all-products, https://setactive.co/collections/activewear and https://setactive.co/collections/basics and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://setactive.co/collections/back-in-stock-1, whose canonical is https://setactive.co/collections/back-in-stock. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://setactive.co/collections/pro-shop has no <h1> headline, so visitors and search engines get no clear main topic.

https://setactive.co/collections/pro-shop and https://setactive.co/collections/back-in-stock-1 took over 3 s to send their HTML from our server.

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

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

Social proof on the homepage: 12 customer or partner logos. 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 803 words of visible text.

Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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 (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 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.