Website review, no card needed
solo.io website review
Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 84 checks
This review found 36 issues worth fixing on solo.io, 10 of them high impact, across 84 checks. The most urgent: render-blocking 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
71CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 4.5 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 185 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 256 ms |
| Jun 20, 2026 | 262 ms |
| Jun 27, 2026 | 255 ms |
| Jul 4, 2026 | 238 ms |
| Jul 11, 2026 | 213 ms |
| Jul 18, 2026 | 202 ms |
| Jul 25, 2026 | 205 ms |
| Aug 1, 2026 | 194 ms |
| Aug 8, 2026 | 195 ms |
| Aug 15, 2026 | 191 ms |
| Aug 22, 2026 | 184 ms |
| Aug 29, 2026 | 180 ms |
| Sep 5, 2026 | 182 ms |
| Sep 12, 2026 | 251 ms |
| Sep 19, 2026 | 265 ms |
| Sep 26, 2026 | 275 ms |
| Oct 3, 2026 | 301 ms |
| Oct 10, 2026 | 246 ms |
| Oct 17, 2026 | 240 ms |
| Oct 24, 2026 | 229 ms |
| Oct 31, 2026 | 214 ms |
| Nov 7, 2026 | 212 ms |
| Nov 14, 2026 | 200 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
1.4 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Reduce unused JavaScript
1.1 s · 379 KiBAbout 379 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Use efficient cache lifetimes
950 ms · 291 KiB18 files are served with short cache lifetimes, so returning visitors download them again (291 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, website-files.com and Clarity and others), adding 1.1 MB and 981 ms of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 661 ms. During a long task the page ignores taps.
Google Tag Manager adds 570 ms
570 msGoogle Tag Manager costs a phone 570 ms of main-thread work and 518 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
450 ms · 82 KiBAbout 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Minify JavaScript
300 ms · 57 KiB57 KiB could be saved by minifying JavaScript.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
website-files.com adds 79 ms
79 mswebsite-files.com costs a phone 79 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.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 7 ms
7 msYour server sent the HTML in 7 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 FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 14.4 s
14.4 sThe page becomes fully interactive after 14.4 s. Good is under 3.8 s.
Total Blocking Time: 967 ms
967 msScripts block taps and scrolling for 967 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 402 ms
402 msReal visitors wait 402 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 994 ms
994 msReal visitors wait 994 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 185 ms to 200 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.7 s 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
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 55.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 110 requests
1.6 MBYour homepage downloads 1.6 MB in 110 requests on a phone: scripts 1.2 MB (36), other files 157 KiB (53) and fonts 151 KiB (4). That is a lean page.
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
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.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
64 internal links, 24 external
The homepage links to 64 pages on solo.io and 24 external pages.
8 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Solo.io builds agentgateway, the gateway for API and AI agent traffic, plus Istio Ambient service mesh, kagent, and age…”.
One H1 headline
Your main headline reads: “Infrastructure for Production-grade AI Agents”.
Title: 51 characters
Your title is a healthy 51 characters: “Solo.io | Reimagining Infrastructure for Cloud & AI”.
Canonical URL set
The canonical URL is https://www.solo.io/.
Structured data in place
Structured data found: 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.solo.io/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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (390 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.solo.io/llms.txt (74 KiB, 350 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.solo.io/resources/workshops is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share a meta description
https://www.solo.io/resources/lab, https://www.solo.io/resources/webinar, https://www.solo.io/resources/workshops and https://www.solo.io/resources use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187186365&tm=gtm002&Ver=2&mid=7e2df1f8-f267-403e-9920-d2cae5fa3f26&bo=1&sid=484b86c0e39111f18b75e3c67f754e78&vid=484bc070e39111f1917557bbc430811e&vids=1&msclkid=N>m_.
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to script at 'https://hivemind.solo.io/attribution-destinations/index.js' from origin 'https://www.solo.io' has …”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
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.
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.
Thin social proof
Social proof on the homepage: 20 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 348 words of copy
The homepage carries about 348 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Contact Solo.io” and “Contact Sales”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads 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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 2 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.
33 other companies contacted
Loading the homepage contacts 33 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 solo.io, 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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Webflow
Hiring
- Hiring
- 9 open roles
- Teams
- Field Engineering -Pre Sales (2), Marketing (2), Sales (2), Customer Success (1)
- Job board
- greenhouse
- Careers page
- www.solo.io/company/careers (opens in a new tab)
Company
- Employees
- 320
- Headquarters
- Cambridge
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on solo.io, including 22 speed issues and 5 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.