simmsfishing.com website review

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

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

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

35 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

8 third-party services load with your homepage (Signyfyd, Klaviyo and Google Tag Manager and others), adding 2.1 MB and 2.0 s of main-thread time.

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

Signyfyd costs a phone 789 ms of main-thread work and 260 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 482 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

visually.io costs a phone 86 ms of main-thread work and 357 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.

Polyfills for old browsers add 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

About 45 KiB of CSS is downloaded but never applied on this page.

12 KiB could be saved by minifying JavaScript.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A man fly fishing in a river, wearing a light green cap, a …”.

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

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

The first text or image appears after 2.4 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 129 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.3 MB in 401 requests on a phone: images 3.0 MB (71), scripts 1.9 MB (128) and other files 830 KiB (157). Under 2 MB keeps phones on slow connections fast.

home-hero-banner-M-RipLinePro-rTaylor-10.13.26.1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate 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.

22 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

The homepage links to 457 pages on simmsfishing.com and 24 external pages.

https://www.simmsfishing.com/pages/g3-pro-guide-waders is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.simmsfishing.com/collections/mens, https://www.simmsfishing.com/pages/orders-returns, https://www.simmsfishing.com/pages/store-locator, https://www.simmsfishing.com/collections/new-mens, https://www.simmsfishing.com/pages/rip-line-pro-rain-suit and https://www.simmsfishing.com/pages/g3-pro-guide-waders have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.simmsfishing.com/cdn/shop/t/551/assets/supplement.min.css?v=171152' because it…”.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Tag Manager, Hotjar and Klaviyo (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 16 cookies (measured from a US location before any click).

Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.