Website review, no card needed

harrowsports.com logo

harrowsports.com website review

Visit site (opens in a new tab)Reviewed 23 October 202640 issues · 77 checks

This review found 40 issues worth fixing on harrowsports.com, 7 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.0 s1.3 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.6 s
May 30, 20261.7 s
Jun 6, 20261.9 s
Jun 13, 20263.1 s
Jun 20, 20263.4 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.4 s
Jul 18, 20263.2 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.9 s
Aug 29, 20262.8 s
Sep 5, 20263.0 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
311 ms58 msMay 2Oct 17275 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202696 ms
May 9, 202687 ms
May 16, 202687 ms
May 23, 202687 ms
May 30, 202691 ms
Jun 6, 202696 ms
Jun 13, 2026139 ms
Jun 20, 2026172 ms
Jun 27, 2026208 ms
Jul 4, 2026216 ms
Jul 11, 2026209 ms
Jul 18, 2026201 ms
Jul 25, 2026186 ms
Aug 1, 2026188 ms
Aug 8, 2026180 ms
Aug 15, 2026202 ms
Aug 22, 2026230 ms
Aug 29, 2026238 ms
Sep 5, 2026260 ms
Sep 12, 2026256 ms
Sep 19, 2026257 ms
Sep 26, 2026273 ms
Oct 3, 2026282 ms
Oct 10, 2026282 ms
Oct 17, 2026275 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

Full-page screenshot of harrowsports.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. harrowsports.com at 1.1 s1.1 s
  2. harrowsports.com at 2.2 s2.2 s
  3. harrowsports.com at 3.3 s3.3 s
  4. harrowsports.com at 4.4 s4.4 s
  5. harrowsports.com at 5.4 s5.4 s
  6. harrowsports.com at 6.5 s6.5 s
  7. harrowsports.com at 7.6 s7.6 s
  8. harrowsports.com at 8.7 s8.7 s

Speed

11 to fix55
  • Reduce unused JavaScript

    4.5 s · 818 KiB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 70). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and jotfor.ms and others), adding 2.4 MB and 456 ms of main-thread time.

  • Use efficient cache lifetimes

    450 ms · 102 KiB

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

  • Improve image delivery

    300 ms · 200 KiB

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

  • Shopify adds 214 ms

    214 ms

    Shopify costs a phone 214 ms of main-thread work and 1.5 MB 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 · 45 KiB

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

  • Main-thread work: 3.1 s

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

  • Render-blocking requests

    300 ms

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

  • Klaviyo adds 117 ms

    117 ms

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

  • jotfor.ms adds 62 ms

    62 ms

    jotfor.ms costs a phone 62 ms of main-thread work and 392 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

    150 ms · 35 KiB

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

  • 3 long tasks on the main thread

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • First Contentful Paint: 9.1 s

    9.1 s

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

  • Largest Contentful Paint: 22.3 s

    22.3 s

    Your largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 23.1 s

    23.1 s

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

  • Speed Index: 12.2 s

    12.2 s

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

  • Real-user LCP: 3.8 s

    3.8 s

    Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 319 ms

    319 ms

    Real visitors wait 319 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 204% slower for real visitors

    +204%

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

  • Largest content (LCP) got 34% slower for real visitors

    +34%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.1 s

    1.1 s

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

3 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 6 ms

    6 ms

    Scripts block the page for only 6 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix64
  • Page weight: 4.5 MB in 451 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 451 requests on a phone: scripts 1.9 MB (157), other files 1.2 MB (230) and images 904 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    stick-iq-header-2.png 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.3 g of CO₂ per visit

    1.26 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 151.6 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

2 to fix94
  • 4 tap targets too small

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

  • 2 links without text

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

1 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 9282
  • Title is short (13 characters)

    Your title is only 13 characters: “Harrow Sports”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 (“Harrow Sports” and “THIS IS HARROW”). One clear main headline is easier for people and search engines.

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

  • 151 internal links, 20 external

    The homepage links to 151 pages on harrowsports.com and 20 external pages.

5 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Harrow Sports is a leading manufacturer of squash, field hockey, lacrosse, and other racquet sports equipment, as well …”.

  • Canonical URL set

    The canonical URL is https://www.harrowsports.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.harrowsports.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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 (523 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.harrowsports.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 10 pages without a meta description

    https://www.harrowsports.com/collections/squash-racquet-signature-and-limited-editions, https://www.harrowsports.com/collections/squash-bags, https://www.harrowsports.com/collections/shoes, https://www.harrowsports.com/collections/squash-accessories, https://www.harrowsports.com/collections/squash-apparel and https://www.harrowsports.com/pages/custom-racquets and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.harrowsports.com/collections/padel and https://www.harrowsports.com/collections/padel-copy use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.harrowsports.com/collections/squash, https://www.harrowsports.com/collections/squash-racquets, https://www.harrowsports.com/collections/squash-racquet-signature-and-limited-editions, https://www.harrowsports.com/collections/squash-bags, https://www.harrowsports.com/collections/shoes and https://www.harrowsports.com/collections/squash-accessories and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • 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.

  • Only about 222 words

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP BY SPORT” and “SHOP CUSTOM GEAR”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Buy-Now Uniforms”, “Contact Us” and “Shop By Sport”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 23 testimonial or review blocks and a star rating.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 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.

  • 43 other companies contacted

    Loading the homepage contacts 43 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 harrowsports.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on harrowsports.com, including 22 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25