Website review, no card needed

orbotix.com logo

orbotix.com website review

Visit site (opens in a new tab)Reviewed 19 November 202638 issues · 77 checks

This review found 38 issues worth fixing on orbotix.com, 14 of them high impact, across 77 checks. The most urgent: hcaptcha.com adds 3.3 s. 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

Full-page screenshot of orbotix.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. orbotix.com at 1.2 s1.2 s
  2. orbotix.com at 2.4 s2.4 s
  3. orbotix.com at 3.7 s3.7 s
  4. orbotix.com at 4.9 s4.9 s
  5. orbotix.com at 6.1 s6.1 s
  6. orbotix.com at 7.3 s7.3 s
  7. orbotix.com at 8.5 s8.5 s
  8. orbotix.com at 9.8 s9.8 s

Speed

14 to fix32
  • hcaptcha.com adds 3.3 s

    3.3 s

    hcaptcha.com costs a phone 3.3 s of main-thread work and 5.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 13.5 s

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

  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 697 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google CDN adds 1.1 s

    1.1 s

    Google CDN costs a phone 1.1 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32. 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 (hcaptcha.com, Google Tag Manager and Google CDN and others), adding 9.9 MB and 6.3 s of main-thread time.

  • Reduce unused JavaScript

    770 ms · 2.4 MB

    About 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.

  • Use efficient cache lifetimes

    750 ms · 540 KiB

    25 files are served with short cache lifetimes, so returning visitors download them again (540 KiB).

  • Render-blocking requests

    650 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • 20 long tasks on the main thread

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

  • sphero.com adds 368 ms

    368 ms

    sphero.com costs a phone 368 ms of main-thread work and 524 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

    310 ms · 62 KiB

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

  • 1,710 HTML elements

    The page has 1,710 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • customerfields.com adds 127 ms

    127 ms

    customerfields.com costs a phone 127 ms of main-thread work and 294 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

    209 KiB

    8 images could be 209 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    150 ms · 33 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

6 to fix34
  • Largest Contentful Paint: 13.1 s

    13.1 s

    Your largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We've Redefined Robotics. Sphero Blueprint Robotics now ava…”.

  • Speed Index: 15.7 s

    15.7 s

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

  • Time to Interactive: 61.2 s

    61.2 s

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

  • Total Blocking Time: 3.7 s

    3.7 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

  • 10 images without width and height

    10 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 12.0 MB in 275 requests

    12.0 MB

    Your homepage downloads 12.0 MB in 275 requests on a phone: scripts 6.1 MB (79), HTML 2.8 MB (20) and other files 1.3 MB (107). Under 2 MB keeps phones on slow connections fast.

  • 9 images below the first screen load straight away

    9 images further down the page (657 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 7 images far larger than shown

    248 KiB

    7 images are downloaded at several times the size a phone draws them, for example Standards.jpg at 1,400 px wide, shown at 350 px. Resized copies would save about 248 KiB.

  • About 3.4 g of CO₂ per visit

    3.41 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.41 g of CO₂e: 409.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 use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9395
  • 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 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 14 form fields without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (11 elements).

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 51 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: 51 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9280
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Sphero Coding Robots & Kits | PK-12 STEM Education, AI Literacy & CTE”.

  • Canonical points to another host

    Your canonical URL points to sphero.com, not orbotix.com, so Google may credit that host instead.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: url points at a different host (https://sphero.com/)”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 40 internal links, 65 external

    The homepage links to 40 pages on orbotix.com and 65 external pages.

4 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Sphero builds future-forward skills & AI Literacy through fun, hands-on coding robots, STEM kits, CTE & computer scienc…”.

  • One H1 headline

    Your main headline reads: “Sphero makes learning fun. Inspiring CS, CTE, and AI skills for students.”.

  • 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://sphero.com/sitemap.xml.

AI search readiness

100
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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,352 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17323658&tm=gtm002&Ver=2&mid=77c95356-e528-4f8a-966f-afab4d291fb5&bo=1&sid=c446d9a0e46611f1b01fdfb5a13eee7b&vid=c446f280e46611f1a70f678232883eed&vids=1&msclkid=N&pi=91.

  • 9 small tap targets

    9 of 21 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: the server responded with a status of 403 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 538 words of copy

    The homepage carries about 538 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 “Get a Quote / Schedule a Meeting”, “Shop All” and “Shop Collections”.

  • 5 short forms

    5 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and HubSpot.

  • Direct contact links

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

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 2 mores (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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 4 of them by other companies (measured from a US location before any click).

  • 52 other companies contacted

    Loading the homepage contacts 52 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.

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 orbotix.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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Hulk Form Builder · Helium Customer Fields · Sitemap Noindex Pro Seo · Elevar Conversion Tracking · Wingify · Selleasy

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

CMS
WordPress
Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
CloudFront

Hiring

Hiring
1 open role
Teams
Accounting (1)
Job board
rippling

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on orbotix.com, including 20 speed issues, 5 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

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