Website review, no card needed
contractpodai.com website review
Visit site (opens in a new tab)Reviewed 4 November 202619 issues · 76 checks
This review found 19 issues worth fixing on contractpodai.com, 5 of them high impact, across 76 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 157 ms |
| May 23, 2026 | 160 ms |
| May 30, 2026 | 152 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 134 ms |
| Jun 27, 2026 | 141 ms |
| Jul 4, 2026 | 160 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 167 ms |
| Jul 25, 2026 | 168 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 168 ms |
| Aug 15, 2026 | 172 ms |
| Aug 22, 2026 | 164 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 166 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 172 ms |
| Oct 3, 2026 | 164 ms |
| Oct 10, 2026 | 172 ms |
| Oct 17, 2026 | 174 ms |
| Oct 24, 2026 | 166 ms |
| Oct 31, 2026 | 163 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
Use efficient cache lifetimes
380 KiB5 files are served with short cache lifetimes, so returning visitors download them again (380 KiB).
cloudflarestream.com adds 252 ms
252 mscloudflarestream.com costs a phone 252 ms of main-thread work and 402 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 JavaScript
279 KiBAbout 279 KiB of JavaScript is downloaded but never used on this page.
5 third-party services on the page
5 third-party services load with your homepage (cloudflarestream.com, secureprivacy.ai and qualified.com and others), adding 429 KiB and 252 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 241 ms. During a long task the page ignores taps.
Render-blocking requests
100 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.
Improve image delivery
38 KiB5 images could be 38 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
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.
3 checks passed
Mobile performance score: 96
96/100Your mobile performance score is 96. That is in Google's “good” band (90 and up).
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 474 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 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.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
Time to Interactive: 4.0 s
4.0 sThe page becomes fully interactive after 4.0 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 157 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 170 ms
170 msReal visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 198 ms
198 msScripts block the page for only 198 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.7 s
1.7 sYour largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Leah is an enterprise agentic AI platform for contract life…”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Speed Index: 1.7 s
1.7 sVisually, the page fills in at 1.7 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
About 0.2 g of CO₂ per visit
0.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.24 g of CO₂e: 29.4 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: 884 KiB in 42 requests
884 KiBYour homepage downloads 884 KiB in 42 requests on a phone: scripts 546 KiB (17), images 181 KiB (8) and fonts 48 KiB (1). 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
Every image has alt text
All 76 images in the HTML carry an alt attribute.
SEO
Structured data has 1 problem
Structured data found (FAQPage, ImageObject, ItemList and Organization) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.
55 internal links, 4 external
The homepage links to 55 pages on contractpodai.com and 4 external pages.
7 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Leah, formerly ContractPodAi, is the agentic AI platform that runs contracting, legal, and procurement end to end. See …”.
One H1 headline
Your main headline reads: “The Agentic AI Platform for Contracting, Legal, Procurement, and Finance”.
Title: 58 characters
Your title is a healthy 58 characters: “Agentic AI for Legal, CLM, Procurement, and Finance - Leah”.
Canonical URL set
The canonical URL is https://leahai.com/.
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://leahai.com/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 (2,138 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://leahai.com/llms.txt (9 KiB, 56 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://leahai.com/solutions/chief-legal-officer is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17202940&tm=gtm002&Ver=2&mid=18f380e0-e47c-43ff-8f7d-d789e55cf905&bo=2&sid=02aaf1b0d88611f1b7f2994494672fed&vid=02ab2550d88611f1be98b5b98306abfa&vids=1&msclkid=N>m_t.
2 JavaScript errors while loading
2 errors were 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
5 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 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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,380 words of copy
The homepage carries about 1,380 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Request a Demo”, “How do I get started with Leah?” and “CONTACT”.
Social proof on the page
Social proof on the homepage: 50 testimonial or review blocks, 33 customer or partner logos and 17 trust badges.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (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.
38 other companies contacted
Loading the homepage contacts 38 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 contractpodai.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- Framework
- Next.js
- Hosting
- Cloudflare
Hiring
- Hiring
- 4 open roles
- Teams
- Sales (4)
- Job board
- bamboohr
- Careers page
- leahai.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on contractpodai.com, including 9 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.