Website review, no card needed
xbotgo.com website review
Visit site (opens in a new tab)Reviewed 9 November 202622 issues · 80 checks
This review found 22 issues worth fixing on xbotgo.com, 3 of them high impact, across 80 checks. The most urgent: page weight: 64.5 MB in 106 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
93A- #433 of 94,632 reviewed websitesbeats 99%
- #141 of 50,827 online storesbeats 99%
- #134 of 45,954 Shopify storesbeats 99%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.3 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 22, 2026 | 1.3 s |
| Sep 5, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.0 s |
| Nov 7, 2026 | 915 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 137 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 159 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 178 ms |
| Jul 11, 2026 | 179 ms |
| Jul 25, 2026 | 177 ms |
| Aug 8, 2026 | 202 ms |
| Aug 22, 2026 | 232 ms |
| Sep 5, 2026 | 245 ms |
| Sep 19, 2026 | 252 ms |
| Sep 26, 2026 | 258 ms |
| Oct 10, 2026 | 266 ms |
| Oct 17, 2026 | 273 ms |
| Oct 24, 2026 | 275 ms |
| Nov 7, 2026 | 265 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
Speed
Render-blocking requests
750 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.
Improve image delivery
351 KiB10 images could be 351 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,674 HTML elements
The page has 2,674 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 0 ms
0 msGoogle Tag Manager costs a phone 0 ms of main-thread work and 356 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 114 ms. During a long task the page ignores taps.
6 third-party services on the page
6 third-party services load with your homepage (ahrefs.com, JSDelivr CDN and Shopify and others), adding 754 KiB and 5 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
37 KiBAbout 37 KiB of CSS is downloaded but never applied on this page.
Minify CSS
14 KiB14 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
11 KiB6 files are served with short cache lifetimes, so returning visitors download them again (11 KiB).
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.
3 checks passed
Mobile performance score: 99
99/100Your mobile performance score is 99. That is in Google's “good” band (90 and up).
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 59 ms of it running JavaScript. That is comfortably low.
Server response: 46 ms
46 msYour server sent the HTML in 46 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Tap response (INP) got 90% slower for real visitors
+90%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 137 ms to 265 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
13 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 0.7 s
0.7 sReal visitors wait 0.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 155 ms
155 msReal visitors wait 155 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 521 ms
521 msReal visitors wait 521 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.7 s
1.7 sYour largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.
Speed Index: 2.1 s
2.1 sVisually, the page fills in at 2.1 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 32 ms
32 msScripts block the page for only 32 ms while loading. Good is under 200 ms.
Time to Interactive: 1.9 s
1.9 sThe page is fully interactive after 1.9 s.
Images and page weight
Page weight: 64.5 MB in 106 requests
64.5 MBYour homepage downloads 64.5 MB in 106 requests on a phone: media 62.1 MB (13), images 1.1 MB (54) and scripts 841 KiB (25). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Frame_2147228597_1.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).
2 images far larger than shown
115 KiB2 images are downloaded at several times the size a phone draws them, for example Frame_2147228597_1.png at 2,400 px wide, shown at 390 px. Resized copies would save about 115 KiB.
About 18.3 g of CO₂ per visit
18.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 18.27 g of CO₂e: 2192.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
20 images without alt text
20 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail 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.
Alternative text of images should not be repeated as text (15 elements)
Alternative text of images should not be repeated as text: 15 elements on the page fail 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. (4 elements).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (28 characters)
Your title is only 28 characters: “XbotGo | 4K AI Sports Camera”. Between 30 and 65 characters leaves room to say what you do and for whom.
3 H1 headlines
There are 3 <h1> headlines (“Pro Soccer has arrived!”, “XbotGo Falcon” and “XbotGo Chameleon”). One clear main headline is easier for people and search engines.
Meta description is long (179 characters)
Your meta description is 179 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
150 internal links, 22 external
The homepage links to 150 pages on xbotgo.com and 22 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://xbotgo.com/.
Structured data in place
Structured data found: 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://xbotgo.com/sitemap.xml.
AI search readiness
4 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,326 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://xbotgo.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://xbotgo.com/products/nt3-pro-carbon-fiber-tripod-8-83ft has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://xbotgo.com/products/xbotgo-falcon-true-4k-ai-camera-for-team-sports, https://xbotgo.com/products/xbotgo-chameleon-ai-powered-4k-sports-camera-system-phone-mount, https://xbotgo.com/collections/accessories, https://xbotgo.com/products/nt3-pro-carbon-fiber-tripod-8-83ft, https://xbotgo.com/products/xbotgo-crab-clamp-mount-full-kit-with-dual-ball-magic-arm and https://xbotgo.com/products/xbotgo-t1-tripod-45inch and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://xbotgo.com/products/xbotgo-falcon-true-4k-ai-camera-for-team-sports and https://xbotgo.com/products/xbotgo-chameleon-ai-powered-4k-sports-camera-system-phone-mount have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://xbotgo.com/products/xbotgo-chameleon-ai-powered-4k-sports-camera-system-phone-mount took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.
5 checks passed
Linked pages load
7 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 19 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 “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 620 words of copy
The homepage carries about 620 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
20 calls to action
The homepage has 20 calls to action, for example “App Download”, “Learn More” and “Buy Now”.
12 short forms
12 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks, 69 customer or partner logos, a star rating and 73 trust badges.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
6 cookies set on arrival
6Opening the homepage sets 6 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.
6 other companies contacted
Loading the homepage contacts 6 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 xbotgo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Microsoft Clarity · Judge Me Reviews · Xcotton Guard · Powerful Form Builder · Easylocation · Omnisend · goaffpro.com · kickbooster.me · seel.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on xbotgo.com, including 5 speed issues and 4 SEO issues. 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.