Website review, no card needed

100ms.ai logo

100ms.ai website review

Visit site (opens in a new tab)Reviewed 17 November 202633 issues · 76 checks

This review found 33 issues worth fixing on 100ms.ai, 15 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
3.1 s1.9 sMay 30Nov 142.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20262.6 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.7 s
Jul 18, 20262.6 s
Jul 25, 20262.8 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.6 s
Aug 22, 20262.5 s
Aug 29, 20262.8 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.1 s
Oct 31, 20262.2 s
Nov 7, 20262.5 s
Nov 14, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
148 ms96 msMay 30Nov 14138 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026131 ms
Jun 6, 2026121 ms
Jun 13, 2026128 ms
Jun 20, 2026127 ms
Jun 27, 2026129 ms
Jul 4, 2026139 ms
Jul 11, 2026142 ms
Jul 18, 2026127 ms
Jul 25, 2026119 ms
Aug 1, 2026111 ms
Aug 8, 2026102 ms
Aug 29, 2026114 ms
Sep 5, 2026115 ms
Sep 12, 2026113 ms
Sep 19, 2026106 ms
Sep 26, 2026114 ms
Oct 3, 2026107 ms
Oct 10, 2026106 ms
Oct 17, 2026113 ms
Oct 24, 2026108 ms
Oct 31, 2026126 ms
Nov 7, 2026138 ms
Nov 14, 2026138 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

Full-page screenshot of 100ms.ai (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 100ms.ai at 0.4 s0.4 s
  2. 100ms.ai at 0.8 s0.8 s
  3. 100ms.ai at 1.1 s1.1 s
  4. 100ms.ai at 1.5 s1.5 s
  5. 100ms.ai at 1.9 s1.9 s
  6. 100ms.ai at 2.3 s2.3 s
  7. 100ms.ai at 2.6 s2.6 s
  8. 100ms.ai at 3.0 s3.0 s

Speed

11 to fix34
  • Reduce unused JavaScript

    2.0 s · 2.3 MB

    About 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

  • Calendly adds 1.3 s

    1.3 s

    Calendly costs a phone 1.3 s of main-thread work and 3.2 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: 34

    34/100

    Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Calendly, Google CDN and Stripe and others), adding 4.9 MB and 2.3 s of main-thread time.

  • Reduce unused CSS

    1.3 MB

    About 1.3 MB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    350 ms · 799 KiB

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

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    750 ms

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

  • Google CDN adds 335 ms

    335 ms

    Google CDN costs a phone 335 ms of main-thread work and 739 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.

  • Stripe adds 274 ms

    274 ms

    Stripe costs a phone 274 ms of main-thread work and 287 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

    45 KiB

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

  • 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: 1 ms

    1 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Time to Interactive: 38.7 s

    38.7 s

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

  • Largest Contentful Paint: 8.1 s

    8.1 s

    Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Getting a patient on specialty medication takes multiple st…”.

  • Speed Index: 12.0 s

    12.0 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 2.6 s

    2.6 s

    Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 1.9 s

    1.9 s

    Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 914 ms

    914 ms

    Real visitors wait 914 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 20 images without width and height

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 131 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 144 ms

    144 ms

    Real visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 11% faster for real visitors

    -11%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 7.5 MB in 99 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 99 requests on a phone: scripts 4.1 MB (41), media 1.5 MB (3) and stylesheets 1.4 MB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (28 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.14 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 256.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

98

Not measured in this review.

SEO

2 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “100ms | Benefits checks and prior auths for specialty practices, at no cost”.

  • 10 internal links, 0 external

    The homepage links to 10 pages on 100ms.ai and 0 external pages.

6 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “We handle the insurance work behind specialty care: benefits checks and prior auths. Free for your practice and your pa…”.

  • Canonical URL set

    The canonical URL is https://www.100ms.ai/.

  • Structured data in place

    Structured data found: Organization.

  • 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.100ms.ai/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    4%

    A phone browser shows 391 words, but the HTML your server sends has only 16. 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.

  • No llms.txt

    There is no https://www.100ms.ai/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 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, logo, sameAs (social profiles) and description; contact details would complete it.

Other pages

1 to fix95
  • 9 pages without an H1

    https://www.100ms.ai/psychiatry, https://www.100ms.ai/gastroenterology, https://www.100ms.ai/neurology, https://www.100ms.ai/allergy-immunology, https://www.100ms.ai/who-we-serve/hub-operations and https://www.100ms.ai/who-we-serve/pharma-manufacturers and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://www.100ms.ai/psychiatry, https://www.100ms.ai/gastroenterology, https://www.100ms.ai/neurology, https://www.100ms.ai/allergy-immunology, https://www.100ms.ai/who-we-serve/hub-operations and https://www.100ms.ai/who-we-serve/pharma-manufacturers and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 9 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 9 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • 4 third-party cookies

    4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

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

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    7 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 391 words of visible text.

1 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Book a call”.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, HubSpot, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

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

  • 26 other companies contacted

    Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 100ms.ai, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Vercel

Company

Employees
110
Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on 100ms.ai, including 21 speed issues, 2 SEO issues and 4 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