No checks match that filter.
Full diagnostics
Every check that ran, grouped by what it affects. Problems appear first in each group.
Meta Tags & Search Snippet Simulator
The tags that decide how this page is titled and described in search results.
Onbixo is no-code product onboarding with built-in AI (OnbiAI): build guided tours, tooltips, checklists, a resource center, announcements, and in-app…
Onbixo is no-code product onboarding with built-in AI (OnbiAI): build guided tours, tooltips, checklists, a resource center, announcements, and in-app…
The meta description is 272 characters and will likely be truncated.
Onbixo is no-code product onboarding with built-in AI (OnbiAI): build guided tours, tooltips, checklists, a resource center, announcements, and in-app surveys in minutes, or let AI draft them. Install with one line. Flat-rate pricing, no MAU surprise bills, no sales call.
The title length is well judged.
Rendered width
| Desktop | 529px | / 580px | |
| Mobile | 476px | / 920px |
Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 59.
Nothing in this section matches the current filter.
Crawling & indexing
Whether search engines can reach, read and index this page at all.
The page returns 200 OK.
The URL resolves without redirects.
No directive prevents indexing.
The canonical correctly references this page.
https://onbixo.com/
Language is declared as "en".
lang="en"
No hreflang annotations, which is correct for a single-language page.
The viewport is configured for mobile.
width=device-width, initial-scale=1
The page declares UTF-8 encoding.
A favicon is declared.
All resources load securely.
The URL is 19 characters.
The URL is clean and readable.
The page is 0 levels deep.
The URL has no query parameters.
robots.txt is present and does not block crawling.
A sitemap is published, listing 112 URLs.
Lists 112 URLs
Nothing in this section matches the current filter.
Content & metadata
What the page says it is about, and how it reads.
Heading hierarchy
The heading outline skips levels (h2 → h4).
h1: Turn more signups into activated users.
h2: Most signups never reach the moment that makes them stay.
h2: Everything you need to guide a user.
h3: Multi-step guided tours
h3: Tooltips & hints
h3: Checklists & launcher
h3: Resource center
h3: Announcements
h3: Surveys & NPS
h2: Your onboarding copilot, built in.
h2: Ship it before your next standup.
h3: Build, no codeHow to fix
Open Graph tags are present.
twitter:card is set to summary_large_image.
The page has exactly one h1.
Turn more signups into activated users.
The page has roughly 2109 words.
Text is 15.2% of the page source.
The page's prominent terms appear in its title, description or headings.
Where these terms appear
| Term | Count | Density | Title | Description | Headings |
|---|---|---|---|---|---|
| users | 21 | 1.56% | ✕ | ✕ | ✓ |
| free | 18 | 1.33% | ✕ | ✕ | ✕ |
| onbiai | 16 | 1.19% | ✕ | ✓ | ✕ |
| flow | 15 | 1.11% | ✕ | ✕ | ✕ |
| onbixo | 13 | 0.96% | ✓ | ✓ | ✕ |
No term is repeated unnaturally often.
The page's most frequent terms, from 1350 words of content.
What this page is about
Term size reflects how often it appears. Density is not a ranking factor, this is a view of the page's subject, not a target to hit.
Nothing in this section matches the current filter.
AI & answer readiness
Whether answer engines and AI overviews can extract and trust this page.
Content freshness
The page publishes no date in any machine-readable form, so engines cannot tell how current it is.
How to fix
Page subject
FAQPage declared without a name or headline.
FAQPage
How to fix
2 headings are followed by a snippet-shaped answer.
Attribution signals present: publisher in structured data, about page, contact page, privacy policy.
publisher in structured data, about page, contact page
Answer-friendly structured data: FAQPage, Question.
FAQPage, Question
2 types: FAQPage, Question
2109 words across 27 headings, 11 lists and 0 tables.
The page names who is behind it: Onbixo.
The page reads the same with and without JavaScript.
llms.txt is published, giving AI agents a curated map of the site.
Every AI crawler checked is allowed to read this page.
Nothing in this section matches the current filter.
Speed & delivery
What makes the page slow, and what the loading experience measures.
Largest Contentful Paint
Target ≤ 2.5s
What this measures
How long until the largest thing on screen, usually the hero image, video or headline block, has finished rendering. It is a proxy for "when did this page feel loaded".
What moves it: Serve the hero image in a modern format at the size it is displayed, preload it, and remove render-blocking CSS and JavaScript ahead of it. A slow server response delays it too, so check TTFB first.
Interaction to Next Paint
Target ≤ 200ms
What this measures
How long the page takes to respond visibly after a tap, click or key press, measured across every interaction, not just the first. High INP is what makes a page feel unresponsive even once it looks ready.
What moves it: Break up long JavaScript tasks so the main thread is free to respond, defer work that is not needed for the interaction, and avoid large re-renders on every event.
Cumulative Layout Shift
Target ≤ 0.1
What this measures
How much visible content jumps around while the page loads. This is what makes someone tap the wrong thing because a banner or image pushed the layout down underneath their finger.
What moves it: Give images and video explicit width and height so the browser reserves the space, reserve room for ads and embeds, and avoid inserting content above what is already on screen.
First Contentful Paint
Target ≤ 1.8s
What this measures
How long until anything at all appears, the first text or image painted. It separates "the page starts slowly" from "the biggest element is slow": a fast FCP with a slow LCP points at the hero, while both slow points at the server.
What moves it: Cut render-blocking CSS and JavaScript in the head, inline the styles needed for the first screen, and improve the server response time.
Real-user response time
Needs real-user data from Chrome UX Report
Render-blocking resources
4 found
4 resources in <head> block the first paint, delaying when anything appears on screen.
stylesheet: /assets/css/app.css?v=1788761910
stylesheet: /assets/css/public.css?v=1789267935
script: /assets/js/islands/theme-init.js?v=1785894220
script: /assets/js/islands/bfcache-guard.js?v=1785894220
How to fix
Time to first byte is 137 ms.
The HTML document is 81 KB.
No deprecated HTML tags are used.
0 inline style attributes.
The response is compressed with zstd.
Content-Encoding: zstd
The page loads 14 requests totalling 451 KB.
What loaded, by type
| Type | Requests | Transferred | |
|---|---|---|---|
| script | 8 | 194 KB | |
| stylesheet | 2 | 173 KB | |
| font | 1 | 66 KB | |
| document | 1 | 16 KB | |
| other | 2 | 1 KB |
Of these, 3 requests (184 KB) come from third-party domains.
3 third-party services load on this page, adding 184 KB.
Third-party services
| Service | Transferred | Main thread | |
|---|---|---|---|
| Google Tag Manager | 173 KB | 164ms | |
| Cloudflare | 10 KB | 23ms | |
| Google Analytics | 1 KB | , |
0.2s of main-thread time
Cache lifetimes are long enough that a returning visitor re-downloads only 4 KB.
Short cache lifetimes
| File | Cache lifetime | Size |
|---|---|---|
| static.cloudflareinsights.com/…6df95cf4e85bb4c19e7a9bdbcba1788362987495 | 1d | 10 KB |
Nothing in this section matches the current filter.
Security
Transport security and the response headers that protect visitors.
HTTPS is enforced with Strict-Transport-Security.
max-age=31536000; includeSubDomains
MIME sniffing is disabled.
The page is protected against framing.
Referrer-Policy is "strict-origin-when-cross-origin".
strict-origin-when-cross-origin
A Content-Security-Policy is set.
No software versions are disclosed in headers.
The TLS certificate is valid for another 35 days.
35 days remaining
Nothing in this section matches the current filter.
Links, media & schema
Links, images and structured data.
Anchor text
3 found
3 links have no anchor text, so its purpose is unreadable without sight of the layout.
Line Link
890 https://x.com/onbixo 891 https://www.linkedin.com/company/onbixo 892 https://www.facebook.com/onbixoapp
How to fix
| Line | Link |
|---|---|
| 890 | https://x.com/onbixo |
| 891 | https://www.linkedin.com/company/onbixo |
| 892 | https://www.facebook.com/onbixoapp |
Structured data is valid: Organization, WebSite, SoftwareApplication, FAQPage.
Organization, WebSite, SoftwareApplication, FAQPage
4 types: Organization, WebSite, SoftwareApplication, FAQPage
Eligible for rich results via Organization, FAQPage.
Organization, FAQPage
2 types: Organization, FAQPage
124 internal and 3 external links.
124 internal, 3 external
124 internal, 3 external
Outbound link rel attributes look appropriate.
In-page anchors resolve to real targets.
The page contains no images.
All 25 checked links resolve.
Nothing in this section matches the current filter.
What to fix first
Ranked by impact against effort, the top of this list buys the most for the least work.
Score breakdown
How each area scored. Categories that could not be measured are excluded rather than counted as zero.