Website review, no card needed
talkie-ai.com website review
Visit site (opens in a new tab)Reviewed 12 October 202639 issues · 64 checks
This review found 39 issues worth fixing on talkie-ai.com, 17 of them high impact, across 64 checks. The most urgent: reduce unused JavaScript. 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 3.8 s |
| Apr 25, 2026 | 3.4 s |
| May 2, 2026 | 3.3 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 148 ms |
| Apr 25, 2026 | 127 ms |
| May 2, 2026 | 92 ms |
| May 9, 2026 | 78 ms |
| May 16, 2026 | 72 ms |
| May 23, 2026 | 64 ms |
| May 30, 2026 | 65 ms |
| Jun 6, 2026 | 65 ms |
| Jun 13, 2026 | 66 ms |
| Jun 20, 2026 | 73 ms |
| Jun 27, 2026 | 77 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 103 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 86 ms |
| Aug 22, 2026 | 82 ms |
| Aug 29, 2026 | 85 ms |
| Sep 5, 2026 | 90 ms |
| Sep 12, 2026 | 93 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 74 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
Reduce unused JavaScript
3.5 s · 786 KiBAbout 786 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Avoid multiple page redirects
3.3 sThe page goes through 1 redirect before it starts loading, costing about 3.3 s. Link and advertise the final URL directly.
Main-thread work: 11.7 s
A phone's processor spends 11.7 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 145 ms. During a long task the page ignores taps.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 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.
Largest Contentful Paint: 13.1 s
13.1 sYour largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 24.4 s
24.4 sVisually, the page fills in at 24.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 71.9 s
71.9 sThe page becomes fully interactive after 71.9 s. Good is under 3.8 s.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Real-user INP: 213 ms
213 msReal visitors wait 213 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
22 images without width and height
22 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 242 ms
242 msScripts block taps and scrolling for 242 ms in total while the page loads. Good is under 200 ms.
7 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 725 ms
725 msReal visitors wait 725 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 41% faster for real visitors
-41%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 148 ms to 74 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.033
0.033The layout barely moves while loading (CLS 0.033, good is under 0.1).
Images and page weight
Page weight: 22.8 MB in 180 requests
22.8 MBYour homepage downloads 22.8 MB in 180 requests on a phone: images 18.6 MB (85), other files 1.8 MB (32) and scripts 1.6 MB (39). Under 2 MB keeps phones on slow connections fast.
24 images far larger than shown
2.4 MB24 images are downloaded at several times the size a phone draws them, for example 50df2281-b103-4079-95c6-05b735b18e1b_meta.jpeg at 1,024 px wide, shown at 179 px. Resized copies would save about 2.4 MB.
6 images below the first screen load straight away
6 images further down the page (879 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.5 g of CO₂ per visit
6.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.46 g of CO₂e: 774.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Images must have alternative text (52 elements)
Images must have alternative text: 52 elements on the page fail this check, rated critical by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (67 elements)
All page content should be contained by landmarks: 67 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (184 characters)
Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://talkie-ai.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at talkie-ai.com/robots.txt, the first file search crawlers ask for.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “Talkie AI | Soulful character AI”.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 3,171 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.
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://talkie-ai.com/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.
Best practices
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”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
41 of 42 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.
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 3,171 words of copy
The homepage carries about 3,171 words of visible text.
1 checks passed
Analytics in place
Analytics detected: TikTok Pixel.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
7 other companies contacted
Loading the homepage contacts 7 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 talkie-ai.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on talkie-ai.com, including 12 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.