Website review, no card needed
acematetennis.com website review
Visit site (opens in a new tab)Reviewed 27 October 202641 issues · 83 checks
This review found 41 issues worth fixing on acematetennis.com, 15 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
69D- #106,486 of 124,235 reviewed websitesbeats 12%
- #64,035 of 69,824 online storesbeats 7%
- #59,055 of 63,496 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 399 ms |
| May 16, 2026 | 372 ms |
| May 23, 2026 | 341 ms |
| May 30, 2026 | 350 ms |
| Jun 6, 2026 | 350 ms |
| Jun 13, 2026 | 362 ms |
| Jun 20, 2026 | 356 ms |
| Jun 27, 2026 | 412 ms |
| Jul 4, 2026 | 485 ms |
| Jul 11, 2026 | 564 ms |
| Jul 18, 2026 | 610 ms |
| Jul 25, 2026 | 537 ms |
| Aug 1, 2026 | 466 ms |
| Aug 8, 2026 | 420 ms |
| Aug 15, 2026 | 432 ms |
| Aug 22, 2026 | 440 ms |
| Aug 29, 2026 | 463 ms |
| Sep 5, 2026 | 420 ms |
| Sep 12, 2026 | 364 ms |
| Sep 19, 2026 | 305 ms |
| Sep 26, 2026 | 227 ms |
| Oct 3, 2026 | 215 ms |
| Oct 10, 2026 | 219 ms |
| Oct 17, 2026 | 237 ms |
| Oct 24, 2026 | 270 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
1.4 s
2.8 s
4.3 s
5.7 s
7.1 s
8.5 s
9.9 s
11.3 s
Speed
Reduce unused JavaScript
3.3 s · 753 KiBAbout 753 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Improve image delivery
2.5 s · 625 KiB6 images could be 625 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 334 KiB20 files are served with short cache lifetimes, so returning visitors download them again (334 KiB).
Main-thread work: 11.4 s
A phone's processor spends 11.4 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 41). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,497 HTML elements
The page has 4,497 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 (Shopify, Google Tag Manager and Facebook and others), adding 2.7 MB and 1.8 s of main-thread time.
Shopify adds 588 ms
588 msShopify costs a phone 588 ms of main-thread work and 1.4 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.
Google Tag Manager adds 380 ms
380 msGoogle Tag Manager costs a phone 380 ms of main-thread work and 504 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 405 ms. During a long task the page ignores taps.
Facebook adds 333 ms
333 msFacebook costs a phone 333 ms of main-thread work and 313 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 · 40 KiBAbout 40 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.
Legacy JavaScript
250 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Render-blocking requests
150 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Minify JavaScript
6 KiB6 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 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 17 ms
17 msYour server sent the HTML in 17 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.
Largest Contentful Paint: 33.9 s
33.9 sYour largest element takes 33.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A player with Acemate on a sunlit tennis court”.
Time to Interactive: 36.1 s
36.1 sThe page becomes fully interactive after 36.1 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 228 ms
228 msReal visitors wait 228 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 399 ms to 270 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 424 requests
5.4 MBYour homepage downloads 5.4 MB in 424 requests on a phone: scripts 2.5 MB (202), images 1.5 MB (22) and other files 1,003 KiB (162). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.
4 images in older formats
4 images (1.6 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.
1 image far larger than shown
206 KiB1 image is downloaded at several times the size a phone draws it, for example your-court-final.webp at 1,860 px wide, shown at 350 px. Resized copies would save about 206 KiB.
About 1.5 g of CO₂ per visit
1.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 185.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 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. (3 elements).
2 checks passed
Every image has alt text
All 75 images in the HTML carry an alt attribute.
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 3 failed. 5 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.
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Acemate Tennis Robot |World's First Real Rally Al Tennis Ball Robot”.
Meta description is long (208 characters)
Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
103 internal links, 42 external
The homepage links to 103 pages on acematetennis.com and 42 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.acematetennis.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization 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.acematetennis.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (4,291 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.acematetennis.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.acematetennis.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.acematetennis.com/pages/reviews and https://www.acematetennis.com/pages/book-a-demo 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 28 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
8 small tap targets
8 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
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,565 words of copy
The homepage carries about 1,565 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Pre-order Now”.
10 calls to action
The homepage has 10 calls to action, for example “Contact UsTalk to the Acemate team.”, “Shop S10” and “Pre-order Now”.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks, a star rating, 8 trust badges and “20K+ Users”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Privacy and tracking
6 trackers load before any consent
6Before 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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
39 other companies contacted
Loading the homepage contacts 39 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 acematetennis.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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on acematetennis.com, including 22 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.