Website review, no card needed

recoveryforathletes.com logo

recoveryforathletes.com website review

Visit site (opens in a new tab)Reviewed 20 November 202639 issues · 86 checks

This review found 39 issues worth fixing on recoveryforathletes.com, 14 of them high impact, across 86 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
2.6 s2.0 sMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.6 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Nov 7, 20262.1 s
Nov 14, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
268 ms214 msMay 30Nov 14220 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026255 ms
Jun 6, 2026262 ms
Jun 13, 2026251 ms
Jun 20, 2026249 ms
Jun 27, 2026246 ms
Jul 4, 2026255 ms
Jul 11, 2026262 ms
Jul 18, 2026248 ms
Jul 25, 2026253 ms
Aug 1, 2026253 ms
Aug 8, 2026246 ms
Aug 15, 2026245 ms
Aug 22, 2026235 ms
Aug 29, 2026228 ms
Sep 5, 2026221 ms
Sep 12, 2026220 ms
Sep 19, 2026221 ms
Sep 26, 2026222 ms
Oct 3, 2026228 ms
Oct 10, 2026231 ms
Oct 17, 2026229 ms
Oct 24, 2026229 ms
Oct 31, 2026229 ms
Nov 7, 2026223 ms
Nov 14, 2026220 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 recoveryforathletes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. recoveryforathletes.com at 1.2 s1.2 s
  2. recoveryforathletes.com at 2.3 s2.3 s
  3. recoveryforathletes.com at 3.5 s3.5 s
  4. recoveryforathletes.com at 4.7 s4.7 s
  5. recoveryforathletes.com at 5.9 s5.9 s
  6. recoveryforathletes.com at 7.0 s7.0 s
  7. recoveryforathletes.com at 8.2 s8.2 s
  8. recoveryforathletes.com at 9.4 s9.4 s

Speed

15 to fix35
  • Reduce unused JavaScript

    1.8 s · 2.2 MB

    About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Main-thread work: 18.0 s

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

  • Mobile performance score: 35

    35/100

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

  • 5,748 HTML elements

    The page has 5,748 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 (Google CDN, Amazon Web Services and Yotpo and others), adding 3.8 MB and 3.3 s of main-thread time.

  • Use efficient cache lifetimes

    500 ms · 1.0 MB

    39 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

  • 20 long tasks on the main thread

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

  • Google CDN adds 919 ms

    919 ms

    Google CDN costs a phone 919 ms of main-thread work and 1.2 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.

  • Amazon Web Services adds 870 ms

    870 ms

    Amazon Web Services costs a phone 870 ms of main-thread work and 148 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

    450 ms · 146 KiB

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

  • Improve image delivery

    100 ms · 448 KiB

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

  • Yotpo adds 481 ms

    481 ms

    Yotpo costs a phone 481 ms of main-thread work and 545 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.

  • Shopify adds 336 ms

    336 ms

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

  • Attentive adds 241 ms

    241 ms

    Attentive costs a phone 241 ms of main-thread work and 324 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.

  • Minify CSS

    150 ms · 15 KiB

    15 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    100 ms · 45 KiB

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

  • Minify JavaScript

    15 KiB

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 32 ms

    32 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Largest Contentful Paint: 11.3 s

    11.3 s

    Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Copper Compression”.

  • Time to Interactive: 44.9 s

    44.9 s

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

  • Speed Index: 13.3 s

    13.3 s

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

  • Total Blocking Time: 2.6 s

    2.6 s

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

  • Real-user INP: 245 ms

    245 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 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.

7 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 746 ms

    746 ms

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

  • Tap response (INP) got 14% faster for real visitors

    -14%

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

  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

  • Cumulative Layout Shift: 0.055

    0.055

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

Images and page weight

1 to fix70
  • Page weight: 8.9 MB in 520 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 520 requests on a phone: scripts 4.3 MB (152), other files 2.2 MB (288) and images 1.3 MB (23). Under 2 MB keeps phones on slow connections fast.

  • About 2.5 g of CO₂ per visit

    2.53 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9090
  • 3 text elements with low contrast

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

  • 3 links without text

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

  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

  • 17 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 18 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Sports Recovery and Home Fitness Equipment — Recovery For Athletes”.

  • 5 links crawlers can't follow

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

  • 670 internal links, 16 external

    The homepage links to 670 pages on recoveryforathletes.com and 16 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Recovery For Athletes is the most trusted injury and muscle recovery store providing the best muscle & injury recovery …”.

  • One H1 headline

    Your main headline reads: “Best Sellers”.

  • Canonical URL set

    The canonical URL is https://www.recoveryforathletes.com/.

  • Structured data in place

    Structured data found: 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://www.recoveryforathletes.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 (3,477 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.recoveryforathletes.com/pages/contact-us is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://www.recoveryforathletes.com/pages/learning-center, https://www.recoveryforathletes.com/pages/recovery-rooms, https://www.recoveryforathletes.com/pages/recovery-for-athletes-rewards-program and https://www.recoveryforathletes.com/collections/most-popular have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.recoveryforathletes.com/pages/our-story, https://www.recoveryforathletes.com/collections/brands, https://www.recoveryforathletes.com/pages/why-buy-from-us, https://www.recoveryforathletes.com/pages/reviews, https://www.recoveryforathletes.com/pages/faqs and https://www.recoveryforathletes.com/pages/contact-us and 8 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 197 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 a title

    All 14 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7770
  • 10 broken images

    10 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/Product/1086465808/892831803/square.jpg?1789751109.

  • 27 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “analytics is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No call to action on the first screen

    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 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 1,282 words of copy

    The homepage carries about 1,282 words of visible text.

5 checks passed
  • 45 calls to action

    The homepage has 45 calls to action, for example “Why Buy From Us”, “Contact Us” and “Shop By Track”.

  • 2 short forms

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

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Umami.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 4 email links.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 35 cookies set on arrival

    35

    Opening the homepage sets 35 cookies, 1 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.

  • 58 other companies contacted

    Loading the homepage contacts 58 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 recoveryforathletes.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;Shopify Plus
Hosting
Shopify

Company

Employees
11
Headquarters
Charlotte

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on recoveryforathletes.com, including 23 speed issues, 2 SEO issues and 1 conversion gap. 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