activeproducts.com website review

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

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

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

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

25 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Klaviyo, useamp.com and Clarity and others), adding 2.3 MB and 917 ms of main-thread time.

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

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

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

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

276 KiB JavaScript is shipped twice across bundles.

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

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

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

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

3 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BRAND NEW 2.0 Best-selling product comes back with better v…”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

26 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-24, real Chrome visitors' tap response (inp) went from 109 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.7 MB in 382 requests on a phone: images 3.6 MB (103), scripts 1.0 MB (108) and other files 732 KiB (102). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example Home_page_-_Catalogue_Images-01.jpg at 2,000 px wide, shown at 343 px. Resized copies would save about 891 KiB.

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

5 images (564 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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.

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is 88 characters, so Google will cut it off around 60: “Active Products | Electric Pressure Washer Products & Accessories – Active Products Inc.”.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 168 pages on activeproducts.com and 62 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.

/products/active%E2%84%A2-premium-pressure-washer-lance and /products/active%E2%84%A2-premium-quick-connect-kit use the same meta description. A description written for each page earns more clicks.

Your homepage links to 9 pages by a URL that isn't their canonical one, for example /products/active%E2%84%A2-2-0-electric-pressure-washer-tool-only, whose canonical is /products/active%e2%84%a2-2-0-electric-pressure-washer-tool-only. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

5 images failed to load on a phone, for example https://reviews-media.services.klaviyo.com/abc/width:260/height:260/resizing_type:fill/plain/https://klaviyo.s3.amazonaws.com/reviews/images/YiMD9q/thumb-75fdf48a-c0da-4c2c-847a-264bb937d36b.jpeg.

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

11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 links from your homepage to your own site are broken, for example https://activeproducts.com/pages/contact (503).

1 link to other sites is dead, for example https://www.obsessedgarage.com/ (503).

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.

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 1,158 words of visible text.

DMARC is set to p=none, so mail pretending to be activeproducts.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 Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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 21 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.