captainspreferredproducts.com website review

A phone's processor spends 5.8 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 (Shopify, Mailchimp and minmaxify.com and others), adding 1.9 MB and 827 ms of main-thread time.

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

About 834 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Mailchimp costs a phone 228 ms of main-thread work and 315 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 2,109 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Heroku costs a phone 24 ms of main-thread work and 413 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 images could be 128 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.

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

154 KiB could be saved by minifying JavaScript.

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

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.

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

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

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Boat cleaning kit by Captains Preferred Products.”.

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

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

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

Your homepage downloads 4.0 MB in 389 requests on a phone: scripts 1.5 MB (101), other files 1.3 MB (206) and images 680 KiB (33). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Your title is 66 characters, so Google will cut it off around 60: “Boat Cleaning Supplies & Accessories | Captains Preferred Products”.

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

The homepage links to 147 pages on captainspreferredproducts.com and 7 external pages.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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 18 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.