Website review, no card needed
fishpondusa.com website review
Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 82 checks
This review found 26 issues worth fixing on fishpondusa.com, 5 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
86B- #12,130 of 124,954 reviewed websitesbeats 87%
- #7,315 of 70,076 online storesbeats 85%
- #7,084 of 63,690 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 919 ms |
| May 23, 2026 | 897 ms |
| May 30, 2026 | 890 ms |
| Jun 6, 2026 | 867 ms |
| Jun 13, 2026 | 851 ms |
| Jun 20, 2026 | 859 ms |
| Jun 27, 2026 | 855 ms |
| Jul 4, 2026 | 861 ms |
| Jul 11, 2026 | 870 ms |
| Jul 18, 2026 | 851 ms |
| Jul 25, 2026 | 860 ms |
| Aug 1, 2026 | 848 ms |
| Aug 8, 2026 | 842 ms |
| Aug 15, 2026 | 873 ms |
| Aug 22, 2026 | 873 ms |
| Aug 29, 2026 | 864 ms |
| Sep 5, 2026 | 853 ms |
| Sep 12, 2026 | 851 ms |
| Sep 19, 2026 | 838 ms |
| Sep 26, 2026 | 844 ms |
| Oct 3, 2026 | 838 ms |
| Oct 10, 2026 | 824 ms |
| Oct 17, 2026 | 819 ms |
| Oct 24, 2026 | 809 ms |
| Oct 31, 2026 | 819 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 72 ms |
| May 23, 2026 | 72 ms |
| May 30, 2026 | 72 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 73 ms |
| Jun 20, 2026 | 74 ms |
| Jun 27, 2026 | 76 ms |
| Jul 4, 2026 | 76 ms |
| Jul 11, 2026 | 75 ms |
| Jul 18, 2026 | 74 ms |
| Jul 25, 2026 | 74 ms |
| Aug 1, 2026 | 73 ms |
| Aug 8, 2026 | 73 ms |
| Aug 15, 2026 | 73 ms |
| Aug 22, 2026 | 72 ms |
| Aug 29, 2026 | 72 ms |
| Sep 5, 2026 | 74 ms |
| Sep 12, 2026 | 73 ms |
| Sep 19, 2026 | 74 ms |
| Sep 26, 2026 | 74 ms |
| Oct 3, 2026 | 74 ms |
| Oct 10, 2026 | 74 ms |
| Oct 17, 2026 | 73 ms |
| Oct 24, 2026 | 72 ms |
| Oct 31, 2026 | 71 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.9 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
960 KiB9 images could be 960 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
600 ms · 148 KiBAbout 148 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 135 KiB11 files are served with short cache lifetimes, so returning visitors download them again (135 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, cloudfront.net and Foursixty and others), adding 609 KiB and 158 ms of main-thread time.
Reduce unused CSS
150 ms · 19 KiBAbout 19 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
8 KiB8 KiB JavaScript is shipped twice across bundles.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 397 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Link to Follow the Birds”.
Time to Interactive: 10.5 s
10.5 sThe page becomes fully interactive after 10.5 s. Good is under 3.8 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 72 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 71 ms
71 msReal visitors wait 71 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 413 ms
413 msReal visitors wait 413 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.9 s
2.9 sVisually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.9 MB in 269 requests
3.9 MBYour homepage downloads 3.9 MB in 269 requests on a phone: images 2.0 MB (20), other files 974 KiB (149) and scripts 630 KiB (61). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
RoadLessTraveled_Swap_DS_1152x.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).
About 1.1 g of CO₂ per visit
1.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 131.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (25 elements)
ARIA role should be appropriate for the element: 25 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (13 elements).
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
140 internal links, 7 external
The homepage links to 140 pages on fishpondusa.com and 7 external pages.
6 checks passed
Title: 42 characters
Your title is a healthy 42 characters: “Fishpond | Fishing, Lifestyle & Field Gear”.
Canonical URL set
The canonical URL is https://fishpondusa.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://fishpondusa.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (566 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fishpondusa.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without a meta description
https://fishpondusa.com/policies/shipping-policy, https://fishpondusa.com/collections/stormshadow, https://fishpondusa.com/collections/nomad-nets, https://fishpondusa.com/collections/lumbar, https://fishpondusa.com/collections/sling and https://fishpondusa.com/collections/chest and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages slow to respond
https://fishpondusa.com/collections/accessories and https://fishpondusa.com/collections/replacement-parts took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0593/9586/6784/files/FP_horizontal_white.svg?v=1783353835.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>.”.
2 checks passed
Tap targets are thumb-sized
27 of 28 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 329 words of copy
The homepage carries about 329 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Bring The Best SHOP NOMAD LANDING NETS” and “Follow the Birds SHOP SALTWATER”.
3 calls to action
The homepage has 3 calls to action, for example “Contact Us” and “Contact”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
No consent tool detected
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.
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at fishpondusa.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Wick Fishpond Pro Program · cloudfront.net · klaviyo.com · chimpstatic.com · useamp.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- smartrecruiters
Company
- Headquarters
- Denver
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on fishpondusa.com, including 8 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.