Website review, no card needed
emochi.com website review
Visit site (opens in a new tab)Reviewed 11 October 202634 issues · 82 checks
This review found 34 issues worth fixing on emochi.com, 13 of them high impact, across 82 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 7.9 s |
| Apr 25, 2026 | 7.8 s |
| May 2, 2026 | 7.9 s |
| May 9, 2026 | 8.2 s |
| May 16, 2026 | 8.5 s |
| May 23, 2026 | 8.8 s |
| May 30, 2026 | 9.1 s |
| Jun 6, 2026 | 9.2 s |
| Jun 13, 2026 | 9.5 s |
| Jun 20, 2026 | 9.5 s |
| Jun 27, 2026 | 9.3 s |
| Jul 4, 2026 | 9.1 s |
| Jul 11, 2026 | 8.7 s |
| Jul 18, 2026 | 8.6 s |
| Jul 25, 2026 | 8.5 s |
| Aug 1, 2026 | 8.5 s |
| Aug 8, 2026 | 8.1 s |
| Aug 15, 2026 | 7.4 s |
| Aug 22, 2026 | 6.6 s |
| Aug 29, 2026 | 5.7 s |
| Sep 5, 2026 | 5.2 s |
| Sep 12, 2026 | 5.2 s |
| Sep 19, 2026 | 5.2 s |
| Sep 26, 2026 | 5.2 s |
| Oct 3, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 720 ms |
| Apr 25, 2026 | 686 ms |
| May 2, 2026 | 678 ms |
| May 9, 2026 | 666 ms |
| May 16, 2026 | 653 ms |
| May 23, 2026 | 636 ms |
| May 30, 2026 | 626 ms |
| Jun 6, 2026 | 621 ms |
| Jun 13, 2026 | 623 ms |
| Jun 20, 2026 | 618 ms |
| Jun 27, 2026 | 606 ms |
| Jul 4, 2026 | 596 ms |
| Jul 11, 2026 | 581 ms |
| Jul 18, 2026 | 573 ms |
| Jul 25, 2026 | 571 ms |
| Aug 1, 2026 | 568 ms |
| Aug 8, 2026 | 551 ms |
| Aug 15, 2026 | 513 ms |
| Aug 22, 2026 | 474 ms |
| Aug 29, 2026 | 442 ms |
| Sep 5, 2026 | 427 ms |
| Sep 12, 2026 | 430 ms |
| Sep 19, 2026 | 432 ms |
| Sep 26, 2026 | 430 ms |
| Oct 3, 2026 | 426 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
1.8 s · 461 KiBAbout 461 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 50
50/100Your mobile performance score is 50 (desktop: 65). Pages that score under 90 lose visitors before the first paint.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,996 HTML elements
The page has 2,996 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google/Doubleclick Ads, Google FundingChoices and Other Google APIs/SDKs and others), adding 714 KiB and 219 ms of main-thread time.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 246 ms. During a long task the page ignores taps.
Improve image delivery
180 KiB3 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
150 ms · 28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
113 KiB5 files are served with short cache lifetimes, so returning visitors download them again (113 KiB).
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
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: 23 ms
23 msYour server sent the HTML in 23 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 TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.0 s
10.0 sYour largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Zoey thumbnail”.
Time to Interactive: 15.1 s
15.1 sThe page becomes fully interactive after 15.1 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 389 ms
389 msReal visitors wait 389 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 446 ms
446 msScripts block taps and scrolling for 446 ms in total while the page loads. Good is under 200 ms.
4 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Tap response (INP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 720 ms to 426 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 7.9 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 133 requests
2.1 MBYour homepage downloads 2.1 MB in 133 requests on a phone: scripts 1.4 MB (59), images 407 KiB (20) and other files 145 KiB (41). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 72.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (62 elements).
2 checks passed
Every image has alt text
All 61 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 5 failed. 1 more 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 social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
72 internal links, 2 external
The homepage links to 72 pages on emochi.com and 2 external pages.
6 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Immersive Roleplay with AI characters for free on Emochi! More than 1 million characters and bots to chat with, AI boyf…”.
Title: 55 characters
Your title is a healthy 55 characters: “Roleplay with unlimited AI Characters for free | Emochi”.
Canonical URL set
The canonical URL is https://emochi.com/.
Structured data in place
Structured data found: WebSite.
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://sitemap.emochi.com/sitemap.xml.
AI search readiness
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://emochi.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,536 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without an H1
https://emochi.com/subscribe and https://emochi.com/flux have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages with very little text
https://emochi.com/flux, https://emochi.com/character/zoey-73ae71aa/chat, https://emochi.com/character/bella-55b58e8d/chat, https://emochi.com/character/annika-37a834e4/chat, https://emochi.com/character/maya-a15792ee/chat and https://emochi.com/character/shayna-bfa3b657/chat and 7 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 66 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://emochi-backend-k8s.flowgpt.com/country' from origin 'https://emochi.com' has been …”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
42 of 49 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.
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 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 380 words of copy
The homepage carries about 380 words of visible text.
1 checks passed
3 short forms
3 short forms (0 fields at most) are right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Ads (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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
13 other companies contacted
Loading the homepage contacts 13 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 emochi.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 34 issues on emochi.com, including 15 speed issues, 2 SEO issues and 7 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.