Website review, no card needed
crossfit.com website review
Visit site (opens in a new tab)Reviewed 4 November 202648 issues · 91 checks
This review found 48 issues worth fixing on crossfit.com, 25 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
63D- #110,770 of 116,487 reviewed websitesbeats 4%
- #65,307 of 66,776 online storesbeats 2%
- #59,855 of 60,929 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.0 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 4.9 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 5.0 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.1 s |
| Jul 4, 2026 | 5.1 s |
| Jul 11, 2026 | 5.1 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.0 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 4.9 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 5.0 s |
| Sep 26, 2026 | 4.9 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 4.9 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.9 s |
| Oct 31, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 154 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 156 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 153 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 158 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 164 ms |
| Oct 24, 2026 | 165 ms |
| Oct 31, 2026 | 164 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
Improve image delivery
12.6 s · 7.0 MB11 images could be 7.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.6 s faster on a phone.
Use efficient cache lifetimes
8.8 s · 1.8 MB13 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Reduce unused JavaScript
8.7 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.7 s faster on a phone.
Render-blocking requests
3.8 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.
Reduce unused CSS
1.4 s · 212 KiBAbout 212 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 22
22/100Your mobile performance score is 22. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Segment and others), adding 1.8 MB and 1.1 s of main-thread time.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 264 ms
264 msGoogle CDN costs a phone 264 ms of main-thread work and 742 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 336 ms. During a long task the page ignores taps.
Google Tag Manager adds 238 ms
238 msGoogle Tag Manager costs a phone 238 ms of main-thread work and 339 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
200 ms · 52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify JavaScript
150 ms · 34 KiB34 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
150 ms · 13 KiB13 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.35
0.35For real visitors the layout shifts by 0.35 (75th percentile). Good is under 0.1.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 14.9 s
14.9 sThe first text or image appears after 14.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 46.1 s
46.1 sYour largest element takes 46.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 49.1 s
49.1 sThe page becomes fully interactive after 49.1 s. Good is under 3.8 s.
Speed Index: 14.9 s
14.9 sVisually, the page fills in at 14.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.345
0.345The layout shifts by 0.345 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 660 ms
660 msScripts block taps and scrolling for 660 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 154 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.0 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 11.8 MB in 66 requests
11.8 MBYour homepage downloads 11.8 MB in 66 requests on a phone: images 7.4 MB (18), scripts 2.9 MB (25) and other files 1.1 MB (12). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
261104app-1024x575.png weighs 795 KiB. On a phone connection a single image that size takes seconds.
7 images in older formats
7 images (2.9 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
6 images below the first screen load straight away
6 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.4 g of CO₂ per visit
3.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.35 g of CO₂e: 402.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails 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. (1 element).
2 checks passed
Every image has alt text
All 22 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 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.
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.
65 internal links, 21 external
The homepage links to 65 pages on crossfit.com and 21 external pages.
7 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “CrossFit offers a results-based, community-driven approach that helps you build fitness and improve your health. Learn …”.
One H1 headline
Your main headline reads: “Train With Purpose. Find Your Gym.”.
Title: 57 characters
Your title is a healthy 57 characters: “CrossFit | CrossFit: The Path to Better Health | CrossFit”.
Canonical URL set
The canonical URL is https://www.crossfit.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.
XML sitemap found
Your XML sitemap is reachable at https://www.crossfit.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.
No llms.txt
There is no https://www.crossfit.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 (965 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.crossfit.com/map has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.crossfit.com/wod, whose canonical is https://www.crossfit.com/261104. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.crossfit.com/map and https://www.crossfit.com/wod have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.crossfit.com/what-to-expect-from-a-crossfit-class, https://www.crossfit.com/crossfit-methodology, https://www.crossfit.com/certificate-courses/level-1 and https://www.crossfit.com/heroes took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
13 small tap targets
13 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
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,051 words of copy
The homepage carries about 1,051 words of visible text.
3 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Learn More”, “Start Getting Stronger” and “Do I need to be fit to start?”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Segment.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Segment and TikTok 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
15 other companies contacted
Loading the homepage contacts 15 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 crossfit.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- E-commerce
- Shopify Plus
- Analytics
- Google Tag Manager | Segment
- Hosting
- AWS
Hiring
- Hiring
- 5 open roles
- Teams
- EDU (3), Affiliates & Ops (1), Marketing (1)
- Job board
- lever
- Careers page
- www.crossfit.com/careers (opens in a new tab)
Company
- Founded
- 2000
- Headquarters
- Santa Cruz
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on crossfit.com, including 23 speed issues, 3 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.