Website review, no card needed
bluefishsport.com website review
Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 76 checks
This review found 32 issues worth fixing on bluefishsport.com, 6 of them high impact, across 76 checks. The most urgent: main-thread work: 15.8 s. 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
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
2.1 s
3.1 s
4.2 s
5.2 s
6.2 s
7.3 s
8.3 s
Speed
Main-thread work: 15.8 s
A phone's processor spends 15.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.0 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
7,717 HTML elements
The page has 7,717 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (omnisnippet1.com, amaicdn.com and Shopify and others), adding 1.1 MB and 908 ms of main-thread time.
Improve image delivery
650 ms · 369 KiB8 images could be 369 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
340 ms · 350 KiBAbout 350 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 340 ms faster on a phone.
Use efficient cache lifetimes
401 KiB20 files are served with short cache lifetimes, so returning visitors download them again (401 KiB).
amaicdn.com adds 326 ms
326 msamaicdn.com costs a phone 326 ms of main-thread work and 401 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.
omnisnippet1.com adds 353 ms
353 msomnisnippet1.com costs a phone 353 ms of main-thread work and 119 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.
Reduce unused CSS
300 ms · 59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 265 ms. During a long task the page ignores taps.
Shopify adds 173 ms
173 msShopify costs a phone 173 ms of main-thread work and 486 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.
Legacy JavaScript
58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need.
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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.4 s
8.4 sYour largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.0 s
16.0 sThe page becomes fully interactive after 16.0 s. Good is under 3.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 464 ms
464 msScripts block taps and scrolling for 464 ms in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 324 requests
3.4 MBYour homepage downloads 3.4 MB in 324 requests on a phone: scripts 1.1 MB (117), images 1.0 MB (35) and other files 895 KiB (151). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
055454c5-f18f-464a-9f3e-e65b7b85f544.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.0 g of CO₂ per visit
0.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.2 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
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.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 240 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Bluefish Sport” and “Bluefish Sport”). One clear main headline is easier for people and search engines.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
279 internal links, 13 external
The homepage links to 279 pages on bluefishsport.com and 13 external pages.
6 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Bluefish Sport creates fashion-forward tennis, fitness, and athleisure apparel with premium fabrics — so you can look y…”.
Title: 53 characters
Your title is a healthy 53 characters: “Bluefish Sport | Tennis, Fitness & Athleisure Apparel”.
Canonical URL set
The canonical URL is https://www.bluefishsport.com/.
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://www.bluefishsport.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
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 (3,263 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bluefishsport.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 pages share a meta description
https://www.bluefishsport.com/collections/core-collection, https://www.bluefishsport.com/collections/skorts, https://www.bluefishsport.com/collections/jackets, https://www.bluefishsport.com/collections/long-sleeves, https://www.bluefishsport.com/collections/cami and https://www.bluefishsport.com/collections/tanks and 7 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 120 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
36 of 36 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: 1 trust badge. 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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 659 words of copy
The homepage carries about 659 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
14 calls to action
The homepage has 14 calls to action, for example “SHOP”, “Register / Login” and “Shop now”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
15 cookies set on arrival
15Opening the homepage sets 15 cookies, 2 of them by other companies (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.
28 other companies contacted
Loading the homepage contacts 28 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 bluefishsport.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
Inbox · Omnisend · Pre Order · Back In Stock · covet.pics
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
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Miami
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on bluefishsport.com, including 17 speed issues, 4 SEO issues and 2 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.