Website review, no card needed

3chat.ai logo

3chat.ai website review

Visit site (opens in a new tab)Reviewed 5 November 202636 issues · 77 checks

This review found 36 issues worth fixing on 3chat.ai, 12 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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.2 s3.1 sJun 27Jul 183.1 s
Show as table
DateReal-visitor load time (LCP)
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s

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 3chat.ai (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 3chat.ai at 0.7 s0.7 s
  2. 3chat.ai at 1.4 s1.4 s
  3. 3chat.ai at 2.1 s2.1 s
  4. 3chat.ai at 2.8 s2.8 s
  5. 3chat.ai at 3.5 s3.5 s
  6. 3chat.ai at 4.2 s4.2 s
  7. 3chat.ai at 4.9 s4.9 s
  8. 3chat.ai at 5.6 s5.6 s

Speed

12 to fix50
  • Use efficient cache lifetimes

    15.3 s · 4.1 MB

    9 files are served with short cache lifetimes, so returning visitors download them again (4.1 MB).

  • Reduce unused JavaScript

    10.8 s · 2.1 MB

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

  • 3,121 HTML elements

    The page has 3,121 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    8.6 MB

    7 images could be 8.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (xinheyun.com, YouTube and Google Tag Manager and others), adding 4.5 MB and 1.4 s of main-thread time.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • xinheyun.com adds 632 ms

    632 ms

    xinheyun.com costs a phone 632 ms of main-thread work and 2.9 MB 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 CSS

    590 ms · 221 KiB

    About 221 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 590 ms faster on a phone.

  • 9 long tasks on the main thread

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

  • YouTube adds 341 ms

    341 ms

    YouTube costs a phone 341 ms of main-thread work and 977 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.

  • Google Tag Manager adds 337 ms

    337 ms

    Google Tag Manager costs a phone 337 ms of main-thread work and 515 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.

  • Main-thread work: 2.8 s

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

  • Legacy JavaScript

    150 ms · 24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

1 checks passed
  • Server response: 181 ms

    181 ms

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

Core Web Vitals

5 to fix50
  • Largest Contentful Paint: 36.9 s

    36.9 s

    Your largest element takes 36.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Buying on social does not follow funnels. It happens in mes…”.

  • Time to Interactive: 37.9 s

    37.9 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • Total Blocking Time: 600 ms

    600 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

5 to fix18
  • Page weight: 15.3 MB in 72 requests

    15.3 MB

    Your homepage downloads 15.3 MB in 72 requests on a phone: images 8.7 MB (13), scripts 4.6 MB (29) and media 1.8 MB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    8c24c0ebfb1468e35de8fc7d6f9c57be9da6e450-11561x6480.png weighs 8.6 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    8.5 MB

    1 image is downloaded at several times the size a phone draws it, for example 8c24c0ebfb1468e35de8fc7d6f9c57be9da6e450-11561x6480.png at 8,192 px wide, shown at 316 px. Resized copies would save about 8.5 MB.

  • 1 image in older formats

    1 image (8.6 MB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image below the first screen load straight away

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

  • About 4.4 g of CO₂ per visit

    4.35 g

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

Accessibility

4 to fixGoogle 9294
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “3Chat.ai | Smart AI Solutions: Revenue Growth, Social Engagement & AI Agents”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 22 internal links, 10 external

    The homepage links to 22 pages on 3chat.ai and 10 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Explore 3Chat.ai’s core features: Revenue-driven sales automation, Social engagement tools for IG/FB, and advanced AI A…”.

  • One H1 headline

    Your main headline reads: “Sell more. Serve better.In every conversation.”.

  • Canonical URL set

    The canonical URL is https://www.3chat.ai/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and 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://www.3chat.ai/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.3chat.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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (6,570 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 7791
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 6,268 words of copy

    The homepage carries about 6,268 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start free with Google” and “Contact on WhatsApp”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Pricing”, “Free Trial” and “Start free with Google”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics and 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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 20 other companies contacted

    Loading the homepage contacts 20 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 3chat.ai, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on 3chat.ai, including 17 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