Skip to content
SiteList

Quantibot Review: Strong workflow, slow mobile (73/100)

Quantibot scores 73/100 for a clear, no-code conversational AI investment research workflow supported by strong accessibility and writing scores. Its most material weakness is mobile performance, with the homepage reaching its largest content at 9.23 seconds and the tools page at 14.91 seconds in the supplied lab runs.

Reviewed by SiteList Engine · 11 of 13 dimensions · published Reviewed on November 1, 2026

Is this your site?

Claim it

Quick facts

Quantibot is a conversational AI investment research product with US-stock examples, a freemium model and a 40-page crawl on 2026-10-22.

Fact Value
Domain quantibot.ai
Category Conversational AI investment research and stock analysis
Pricing Freemium; free tier available; paid plan pricing was not captured in the supplied slice
Platforms Web
Crawl 40 pages, crawled 2026-10-22
Evidence
Domain
quantibot.ai
Pricing model
freemium; free tier available; paid plan pricing was not captured in the supplied slice
Crawl
40 pages on 2026-10-22

Executive summary

Quantibot’s 73/100 score reflects a product that explains a real job clearly: investors can pursue stock analysis, screening, and backtesting without code. The strongest results are accessibility at 86/100, writing quality at 83.1/100, and usability at 81.8/100. The site’s positioning is also clear within five seconds, with a concrete research workflow rather than a generic promise.

The main constraint is speed on mobile. In the supplied PageSpeed Insights lab runs, the homepage reached its largest content at 9.23 seconds and the tools page at 14.91 seconds. The next gaps are self-serve help at 55.8/100, audience and messaging at 67.3/100, and technical SEO at 68.5/100. Six stock pages in the sitemap carry noindex, and the unknown-path probe is a soft 404. Design execution, risk and stability, and editorial QA are more settled at 72/100, 72/100, and 75/100 respectively.

Evidence
Overall score
73/100
Homepage largest content
9.23 seconds
Tools page largest content
14.91 seconds

01 · First impressions & positioning — a clear research workflow with a broad audience frame

Quantibot.ai is legible within five seconds as conversational investment research for stock analysis, screening, and backtesting without code. The line "Backtest, screen, and analyze stocks — just by asking" names both the action and the interaction, while the homepage supports it with examples including 240 matches and a 13.1% CAGR. The positioning is strongest when the product demonstrates its output and keeps illustrative results beside the investment disclaimer. The remaining decision is audience priority: the About page names individual investors, advanced individual investors, and investment professionals, while the hero speaks to all three. Choose one primary entry segment, then add a concise alternatives frame for spreadsheets, code, and expensive platforms. Pair product demonstrations with attributable validation where available, without blurring illustrative performance and market proof.

Evidence
Time to understand category
within five seconds
Screener example
240 matches
Backtest example
13.1% CAGR

02 · Audience & messaging — free entry is concrete, paid limits are not

A first-time visitor can understand the core job: ask a research question and receive a screen, backtest, or analysis without code. The language is direct—"Free to start — no card required"—and the supplied evidence says the tools can be run without sign-up. The audience is also explicit, covering individual investors, advanced individual investors, and investment professionals. The evaluation becomes less complete at the commercial edge. Feature pages mention upgrades for more tickers, longer windows, custom filters, and Pro strategies, but the supplied surface does not provide a usable paid-plan total or limit matrix. Add plan prices, data-universe limits, history length, and upgrade commitment beside each free-tool CTA. Add clear support, cancellation, refund, and result-remediation expectations so a serious prospect can evaluate the full decision boundary.

Evidence
Free-start promise
Free to start — no card required
Named audience groups
3
Paid-plan detail
No usable total or limit matrix in supplied excerpts

03 · Usability — strong task paths, but 9.2 s mobile LCP delays first use

The public information architecture gives visitors clear routes to the offer, portfolio backtesting, FAQ answers, and research content. The portfolio path moves from the homepage to a page with "Try it free" and a visible "Run backtest" interface; the FAQ uses direct question labels; and the Research Blog exposes a heading, search field, category chips, and article grid. The main friction is mobile. The homepage lab run records 9.2 s LCP and 11.0 s TTI, while FAQ, About Us, and Contact sit inside collapsed footer groups. The free-start CTA is prominent, but the supplied crawl verifies only its entry point, not the destination form or confirmation state. Prioritize the first mobile viewport, expose help and company paths earlier, and make signup success and error states observable.

Evidence
Mobile homepage LCP
9.2 s
Mobile homepage TTI
11.0 s
Backtesting entry action
Try it free / Run backtest

04 · Accessibility — 86/100 baseline, with blog structure and contrast still to repair

Quantibot’s sampled accessibility evidence is solid but not complete. The homepage reports header, navigation, main, footer, and section landmarks, a skip link, seven images without missing alt attributes, and no positive tabindex values. The feature-page form exposes a combobox name through aria-labelledby, and the 390px mobile capture shows a single-column layout without visible clipping. The blog capture is the urgent exception: it reports no landmarks, no heading sequence, and no skip link. Lighthouse also reports insufficient color contrast on /blog, while privacy and terms each report two h1 elements. Verify the rendered blog DOM, restore its page structure, fix the contrast pair, and reproduce the homepage ARIA findings with element-level audit details. Keyboard order, focus trapping, announcements, and captions remain unverified.

Evidence
Accessibility score
86/100
Homepage image alt coverage
7 images with no missing alt attributes
Blog landmark result
none reported

05 · Design execution — 140 colors and 15 small homepage tap targets

Quantibot has a recognizable visual system: blue navigation, warm orange primary actions, restrained card borders, and a clear desktop-to-mobile reflow. Its execution is held back by measurable drift. The sampled CSS contains 140 colors, 76 font sizes, 33 radii, 129 spacing values, and 5 font families across 2,508,331 bytes, making a smaller documented token layer the highest-leverage craft improvement. Mobile structure is otherwise sound: sampled 390px renders report scrollWidth 390 with a valid viewport setting. Hit areas need attention, with 15 small targets on the homepage and 5 on each sampled feature page, including a 102x36px header CTA and 32x32px prompt send control. Increase actionable areas to at least 44x44px, then make the homepage h1 and 15.2px paragraph sample slightly more decisive typographically.

Evidence
Distinct CSS colors
140
Homepage small tap targets
15
Homepage sampled width
scrollWidth 390 at 390px

06 · Performance — 9.23 s homepage LCP and 14.91 s on /tools

In the supplied PageSpeed Insights lab runs, mobile performance is the material product constraint. The homepage reaches largest content at 9.23 s, while /tools reaches it at 14.91 s. The homepage server-response time is only 41 ms, so the measured delay sits after the response in render-blocking work, JavaScript, and delivery. The homepage run estimates 770 ms of render-blocking savings and 272 KiB of unused JavaScript; /tools carries an estimate of 700 KiB unused JavaScript, 1.86 s bootup, and 2.43 s main-thread work. Split route code by interaction, defer below-the-fold work, and identify the exact LCP node with a trace before changing presentation code. Reserve blog image space with dimensions or aspect-ratio to address the sampled CLS failures.

Evidence
Homepage mobile LCP
9.23 s
/tools mobile LCP
14.91 s
Homepage server-response time
41 ms

07 · Writing quality — a 13.1% CAGR example gives the message useful weight

Quantibot’s strongest writing puts a real research action beside a measurable example. "$10k in AAPL · 50/200 MA cross · 2015–2025 → 13.1% CAGR" and the portfolio-overlap example make the product legible without coding experience. The homepage then repeats its promise in adjacent lines, so keep the first positioning sentence and use the second for a distinct proof point or audience cue. The About page needs the same editorial discipline in structure: its heading tree moves from H1 directly to H3 sections such as Our Mission and Who We Serve; promote those major sections to H2. Carry the example-first method into research introductions and keep the illustrative-performance disclaimer beside each result. Shorten the homepage’s 77-character title and the 70-character portfolio title while preserving the product noun and intent.

Evidence
Illustrative backtest result
13.1% CAGR
Homepage title length
77 characters
Portfolio backtesting title length
70 characters

08 · Risk & stability — six noindex stock URLs and a soft 404 define the main exposure

Quantibot is live, HTTPS-enabled, and mostly server-rendered in the supplied crawl, but two boundary conditions need prompt correction. Six stock pages—AMD, PLTR, ORCL, VOO, INTC, and AMC—appear in the sitemap while carrying noindex,follow. If those pages are meant to attract stock searches, the sitemap and robots policy are working against each other. The guaranteed-nonexistent path also returns the homepage with HTTP 200, which creates soft-404 ambiguity. Rendering is resilient on most samples, but /stock/GOOG has 10 raw words versus 288 after rendering, and the mobile homepage records 9,232.5 ms LCP. Align stock indexing policy, return a real 404 for unknown paths, and move primary stock content into initial HTML or reliable prerendering. Connect Search Console before attributing traffic changes to search updates.

Evidence
Conflicting stock URLs
6 sitemap URLs marked noindex,follow
Unknown-path response
HTTP 200 with homepage title
GOOG raw versus rendered words
10 versus 288

09 · Editorial QA of content — illustrative results need a visible evidence trail

Quantibot is closer to a competent editorial program than an unedited content pipeline. Its trading-agent article defines a concrete distinction between a rule-following bot and a goal-directed agent, while the FAQ answers portfolio-backtesting questions directly. The main QA gap is traceability around illustrative figures: the homepage presents 13.1% CAGR, 31% overlap, and 38% tech look-through, but the supplied evidence does not show the source context for those calculations. Add the test window, universe, benchmark, and methodology link at the point of use. Feature pages also repeat "Conversational research", "No coding required", and "For every investor"; retain shared reassurance, but give each page a distinct proof paragraph. Finally, validate the rendered FAQ structured data against its visible questions and answers rather than treating the supplied schema records as conclusive.

Evidence
Illustrative CAGR example
13.1%
Illustrative portfolio overlap
31%
Repeated feature bullets
3

10 · Docs & self-serve help — one FAQ page carries the public help surface

Quantibot’s FAQ is a useful answer layer: it covers stock analysis, portfolio backtesting, screening, stress testing, and the non-advice position, and the supplied crawl records FAQPage markup plus a clear free-start CTA. The public documentation surface is still concentrated in one crawled documentation URL. The evidence does not show a task-oriented getting-started guide, and the FAQ reports no search box or breadcrumbs. That leaves visitors with answers but not a complete first-workflow path. Add a Help hub with guides for asking a first stock question, running a first portfolio backtest, and building a first screener. Each guide should state prerequisites, numbered actions, expected results, and troubleshooting links. Keep the FAQ concise, link it from primary navigation, and use the existing /llms.txt layer as machine-readable support rather than a substitute for human onboarding.

Evidence
Crawled documentation URLs
1
FAQ search box
false
Machine-readable help file
2,839-byte /llms.txt body

11 · Technical SEO — 73 URLs, six noindex conflicts, and a client-rendered stock page

Quantibot has a sound crawl foundation: robots.txt allows the public surface, declares primary and blog sitemaps, and the verified sitemap contains 73 URLs. Homepage markup includes Organization, WebSite, and SoftwareApplication entities. Indexability is the main technical SEO risk. Six stock URLs are in the sitemap while marked noindex,follow, and the guaranteed-nonexistent path returns the homepage with HTTP 200 instead of a 404. /stock/GOOG also has a substantial raw-to-rendered gap—10 words versus 288, with js_only_share 0.917. Resolve the sitemap and noindex policy, return a real 404, and server-render primary stock content and metadata. Then change the HTTP root redirect from 302 to 301 and enforce one trailing-slash policy. Mobile homepage LCP remains a material supporting issue at 9.2 s in lab testing.

Evidence
Verified sitemap URLs
73
Stock sitemap/noindex conflict
6 URLs
GOOG JS-only share
0.917

Verdict — 73/100: strong workflow, slow mobile experience

Quantibot works best when it shows a concrete research action and lets the reader understand the no-code path quickly. Accessibility scored 86/100, writing quality 83.1/100, and usability 81.8/100, giving the product a credible foundation for individual investors, advanced individual investors, and investment professionals seeking quantitative research without coding.

Three fixes would materially strengthen the experience: reduce the homepage and tools-page mobile loading times, expand the self-serve help surface behind the 55.8/100 docs score, and resolve the indexability issues reflected in the 68.5/100 technical SEO score. The sitemap’s six stock pages with noindex are a specific place to start. Quantibot is a good fit for people who want to ask for stock research, screening, or backtesting without writing code, provided they can accept the current mobile wait.

Evidence
Accessibility
86/100
Docs & self-serve help
55.8/100
Technical SEO
68.5/100

Methodology & data notes

This is a 13-dimension review based on the supplied crawl of 40 pages captured on 2026-10-22, the public dimension score table, and current product facts extracted from the site’s JSON-LD. The review uses the supplied public summaries and scores; it does not turn planning, assistance, or research workflows into verification or assurance claims.

Two dimensions were excluded from article sections: 12 · Decision-support surfaces was marked failed, and 13 · Review-content integrity was marked not_applicable. Enrichment is pending for Google Search Console: it was not connected and access was not available in the supplied profile. Paid-plan pricing was also not captured, so this review states only the confirmed freemium model and free tier. See the SiteList methodology for the full 13-dimension review method and scoring context.

Evidence
Review scope
13 dimensions
Excluded dimension 12
Decision-support surfaces — failed
Excluded dimension 13
Review-content integrity — not_applicable

Questions buyers actually ask

What is Quantibot for?

Quantibot is for individual investors, advanced individual investors, and investment professionals seeking quantitative research and stock analysis without coding. The site presents conversational research, screening, and backtesting workflows.

Does Quantibot have a free plan?

Yes. The supplied product facts identify Quantibot as freemium with a free tier available. Paid-plan pricing was not captured in the supplied crawl slice.

How fast is Quantibot on mobile?

The supplied PageSpeed Insights lab runs recorded 9.23 seconds for the homepage’s largest content and 14.91 seconds for the tools page. Mobile performance is the clearest area for focused improvement.

Is Quantibot easy to understand?

Yes. The positioning is legible within five seconds, and the site explains concrete research actions such as asking for a backtest, screen, or analysis without code. Usability scored 81.8/100.

What should Quantibot improve first?

The highest-priority work is mobile performance, followed by stronger self-serve help and clearer indexability handling. Docs and self-serve help scored 55.8/100, while technical SEO scored 68.5/100.

How this review was made

SiteList reviewed quantibot.ai on November 1, 2026 — pages, screenshots, performance runs, structured data and public records — then scored it across 11 of the 13 public dimensions. Every claim above is sourced from what we collected; nothing is hand-tuned and the score is never for sale.

Not covered in this write-up: Decision-support surfaces (could not be assessed), Review-content integrity (not applicable). Dimensions without a score are excluded and their weight is redistributed across the scored ones.

Pending enrichment (data we could not fetch this run): SERP samples were not available because no SERP endpoint was configured., No external competitor H1 comparison was available., SERP samples were unavailable because no SERP endpoint was configured., Google Suggest returned no suggestions for the sampled Quantibot queries., No Reddit or other external voice-of-customer sample was supplied., Live click-through of the “Get started free” CTA and signup validation state., Mobile screenshots or scripted runs for the FAQ and portfolio backtesting destinations., Live axe-core results and a scripted keyboard/tab-order probe were not supplied.…

Read the full methodology

73/100QuantibotJump to review