Website review, no card needed
biconomy.io website review
Visit site (opens in a new tab)Reviewed 20 October 202623 issues · 61 checks
This review found 23 issues worth fixing on biconomy.io, 6 of them high impact, across 61 checks. The most urgent: fails Core Web Vitals for real visitors. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 243 ms |
| May 9, 2026 | 296 ms |
| May 16, 2026 | 266 ms |
| May 23, 2026 | 266 ms |
| May 30, 2026 | 266 ms |
| Jun 6, 2026 | 265 ms |
| Jun 13, 2026 | 256 ms |
| Jun 20, 2026 | 205 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 188 ms |
| Jul 11, 2026 | 191 ms |
| Jul 18, 2026 | 190 ms |
| Jul 25, 2026 | 215 ms |
| Aug 1, 2026 | 249 ms |
| Aug 8, 2026 | 221 ms |
| Aug 15, 2026 | 216 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 217 ms |
| Sep 5, 2026 | 222 ms |
| Sep 12, 2026 | 224 ms |
| Sep 19, 2026 | 206 ms |
| Sep 26, 2026 | 186 ms |
| Oct 3, 2026 | 201 ms |
| Oct 10, 2026 | 199 ms |
| Oct 17, 2026 | 195 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
Speed
Mobile performance score: 89
89/100Your mobile performance score is 89 (desktop: 99). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Improve image delivery
810 KiB16 images could be 810 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
430 ms · 100 KiBAbout 100 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 430 ms faster on a phone.
Reduce unused CSS
290 ms · 11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
38 KiB5 files are served with short cache lifetimes, so returning visitors download them again (38 KiB).
3 third-party services on the page
3 third-party services load with your homepage (posthog.com, Plausible and Google Fonts), adding 91 KiB and 25 ms of main-thread time.
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.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 187 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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 LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
68 images without width and height
68 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The smart wallet and execution engine for high performance …”.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.9 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user INP: 185 ms
185 msReal visitors wait 185 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.
Tap response (INP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 243 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.9 s
2.9 sVisually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.
Time to Interactive: 3.1 s
3.1 sThe page is fully interactive after 3.1 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 9 ms
9 msScripts block the page for only 9 ms while loading. Good is under 200 ms.
Images and page weight
4 images far larger than shown
634 KiB4 images are downloaded at several times the size a phone draws them, for example trust.jpg at 2,500 px wide, shown at 56 px. Resized copies would save about 634 KiB.
Page weight: 3.0 MB in 59 requests
3.0 MBYour homepage downloads 3.0 MB in 59 requests on a phone: media 1.9 MB (1), images 871 KiB (45) and scripts 213 KiB (7). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (692 KiB) 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.
6 images below the first screen load straight away
6 images further down the page (718 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 101.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
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.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Biconomy is the universal execution layer for Web3. Composable orchestration, gas sponsorship, cross-chain transactions…”.
Title: 49 characters
Your title is a healthy 49 characters: “Biconomy - Your Universal Interface to All Chains”.
Canonical URL set
The canonical URL is https://biconomy.io/.
Structured data in place
Structured data found: FAQPage, ItemList, Organization, SoftwareApplication 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://biconomy.io/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 464 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://www.biconomy.io/llms.txt (7 KiB, 0 links), a plain-text guide to the site for AI tools.
Best practices
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”.
2 checks passed
Tap targets are thumb-sized
6 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
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.
About 464 words of copy
The homepage carries about 464 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start Building” and “Book a Demo”.
Analytics in place
Analytics detected: Plausible.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 biconomy.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Plausible
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on biconomy.io, including 11 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.