Website review, no card needed
catapult.com website review
Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 96 checks
This review found 33 issues worth fixing on catapult.com, 8 of them high impact, across 96 checks. The most urgent: page weight: 16.4 MB in 81 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 102 ms |
| May 16, 2026 | 100 ms |
| May 23, 2026 | 99 ms |
| May 30, 2026 | 99 ms |
| Jun 6, 2026 | 100 ms |
| Jun 13, 2026 | 101 ms |
| Jun 20, 2026 | 103 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 106 ms |
| Jul 11, 2026 | 109 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 100 ms |
| Aug 1, 2026 | 93 ms |
| Aug 8, 2026 | 83 ms |
| Aug 15, 2026 | 80 ms |
| Aug 22, 2026 | 81 ms |
| Aug 29, 2026 | 83 ms |
| Sep 5, 2026 | 86 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 88 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
catapult.com does not allow embedding, so this is Google's rendering of the page.
Speed
Render-blocking requests
1.4 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Hubspot and Cookiebot and others), adding 2.4 MB and 994 ms of main-thread time.
Use efficient cache lifetimes
450 ms · 681 KiB10 files are served with short cache lifetimes, so returning visitors download them again (681 KiB).
Mobile performance score: 70
70/100Your mobile performance score is 70 (desktop: 44). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
846 KiBAbout 846 KiB of JavaScript is downloaded but never used on this page.
Google CDN adds 438 ms
438 msGoogle CDN costs a phone 438 ms of main-thread work and 1.1 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.
Hubspot adds 347 ms
347 msHubspot costs a phone 347 ms of main-thread work and 778 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 0 ms
0 msGoogle Tag Manager costs a phone 0 ms of main-thread work and 342 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.
Improve image delivery
218 KiB1 image could be 218 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.
Reduce unused CSS
26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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.
Time to Interactive: 20.5 s
20.5 sThe page becomes fully interactive after 20.5 s. Good is under 3.8 s.
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ATHLETE MONITORING”.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 903 ms
903 msReal visitors wait 903 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 276 ms
276 msScripts block taps and scrolling for 276 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
7 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 77 ms
77 msReal visitors wait 77 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 102 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.048
0.048The layout barely moves while loading (CLS 0.048, good is under 0.1).
Images and page weight
Page weight: 16.4 MB in 81 requests
16.4 MBYour homepage downloads 16.4 MB in 81 requests on a phone: media 11.9 MB (3), scripts 2.3 MB (39) and images 1.2 MB (13). Under 2 MB keeps phones on slow connections fast.
About 4.7 g of CO₂ per visit
4.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.66 g of CO₂e: 558.8 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
Unlabelled dropdowns
1 dropdown has no label.
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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.
92 internal links, 11 external
The homepage links to 92 pages on catapult.com and 11 external pages.
7 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Discover Catapult. The cutting-edge sports technology, data analytics, and insights that will unleash your team's and a…”.
Title: 48 characters
Your title is a healthy 48 characters: “Catapult | Sports Technology | Unleash Potential”.
Canonical URL set
The canonical URL is https://www.catapult.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://www.catapult.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no /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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
3 pages share a title
/solutions/impect, /solutions/impect-analysis and /solutions/impect-scouting all use the title “Impect | Football Event Data”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
/perch has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
/solutions/impect, /solutions/impect-analysis and /solutions/impect-scouting use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
/solutions/impect, /solutions/impect-analysis and /solutions/impect-scouting 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 60 found) and read each the way a search engine does.
4 checks passed
Linked pages load
11 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “fallback is not defined”.
2 checks passed
Tap targets are thumb-sized
14 of 17 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No HSTS header
No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
2 links through redirect chains
2 links go through two or more redirects, for example https://one.catapultsports.com/.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
6 checks passed
Served over HTTPS
The homepage is served over HTTPS (catapult.com).
Valid certificate (85 days left)
The certificate from Let's Encrypt · YE2 verifies for catapult.com and is valid for another 85 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
http:// redirects to https
http://catapult.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 51 links work
All 51 links checked from your homepage (40 internal, 11 external) answered without errors.
Domain and trust
No CAA record
catapult.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
catapult.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 33 years old
33 yearscatapult.com was registered in Aug 1993 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.
Registered until Aug 2027
catapult.com is registered until Aug 2027.
Content and conversion
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.
Only about 120 words
The homepage has only about 120 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT” and “REQUEST A DEMO”.
10 calls to action
The homepage has 10 calls to action, for example “Catapult Pricing”, “Contact” and “Request a Demo”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be catapult.com is still delivered. Reports are on, so moving to quarantine is the next step.
Email authentication score: 70/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com include:mail.zendesk.com include:5216869.spf05.hubspotemail.net include:mg-spf.greenhous…”.
DKIM signing found
A DKIM key is published (selector “google”), so receivers can verify mail really came from you.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
Upkeep, stack and company
- It runs WordPress 3.7.1; the current release is 7.1.3.
Stack
- CMS
- WordPress 3.7.1
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on catapult.com, including 16 speed issues, 2 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.