captharry.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.8 MB and 960 ms of main-thread time.

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

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

Google Tag Manager costs a phone 545 ms of main-thread work and 692 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.

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

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

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

6 KiB could be saved by minifying CSS.

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

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

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.

Your largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Previous Next 【Newest Arrivals】 QUANTUM EXCEED SPINNING REE…”.

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

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

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

Real visitors wait 841 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 3.7 MB in 211 requests on a phone: scripts 1.5 MB (66), other files 1.2 MB (94) and images 837 KiB (38). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

9 buttons have no accessible name, so screen readers announce just “button”.

Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

22 tap targets are too small or too close together to hit reliably with a finger.

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

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

Some list items are not inside a list.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

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

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

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

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

Your title is 68 characters, so Google will cut it off around 60: “Capt. Harry's Fishing Supply | Salt Water Fishing Tackle & Equipment”.

There are 2 <h1> headlines (“” and “Subscribe to our Newsletter”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization, ProfessionalService and WebSite) but with 1 problem, for example “ld+json block 3 is not valid JSON (Unexpected non-whitespace character after JSON at position 3)”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 170 pages on captharry.com and 14 external pages.

There is no /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.

/collections/clearance-selection and /collections/fishing-reel-accessories 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 /collections/saltwater-fishing-reels, whose canonical is /collections/reels. 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 138 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example http://www.milehighthemes.com/.

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.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 242 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

DMARC is set to p=none, so mail pretending to be captharry.com is still delivered. Add a report address, check the reports, then move to quarantine.

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, Meta Pixel 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 15 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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.