Programmable

Website review, no card needed

joshtalks.com logo

joshtalks.com website review

Visit site (opens in a new tab)Reviewed 1 November 202621 issues · 72 checks

This review found 21 issues worth fixing on joshtalks.com, 10 of them high impact, across 72 checks. The most urgent: render-blocking requests. 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

Site score

85B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.9 s2.0 sMay 9Oct 102.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.4 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
130 ms115 msMay 9Oct 10127 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026123 ms
May 16, 2026122 ms
May 23, 2026121 ms
May 30, 2026120 ms
Jun 6, 2026119 ms
Jun 13, 2026117 ms
Jun 20, 2026117 ms
Jun 27, 2026119 ms
Jul 4, 2026119 ms
Jul 11, 2026122 ms
Jul 18, 2026122 ms
Jul 25, 2026124 ms
Aug 1, 2026125 ms
Aug 8, 2026127 ms
Aug 15, 2026128 ms
Aug 22, 2026128 ms
Aug 29, 2026127 ms
Sep 5, 2026125 ms
Sep 12, 2026127 ms
Sep 19, 2026126 ms
Sep 26, 2026127 ms
Oct 3, 2026127 ms
Oct 10, 2026127 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

www.joshtalks.com (opens in a new tab)
Full-page screenshot of joshtalks.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. joshtalks.com at 0.6 s0.6 s
  2. joshtalks.com at 1.2 s1.2 s
  3. joshtalks.com at 1.8 s1.8 s
  4. joshtalks.com at 2.3 s2.3 s
  5. joshtalks.com at 2.9 s2.9 s
  6. joshtalks.com at 3.5 s3.5 s
  7. joshtalks.com at 4.1 s4.1 s
  8. joshtalks.com at 4.7 s4.7 s

Speed

1 to fix96

  • Render-blocking requests

    1.1 s

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Improve image delivery

    166 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 80 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    54 KiB

    About 54 KiB of CSS is downloaded but never applied on this page.

  • Reduce unused JavaScript

    30 KiB

    About 30 KiB of JavaScript is downloaded but never used on this page.

  • Legacy JavaScript

    14 KiB

    Polyfills 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/100

    Your mobile performance score is 96. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 179 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

5 to fix100

  • 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: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Time to Interactive: 6.9 s

    6.9 s

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

  • Speed Index: 5.4 s

    5.4 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

8 checks passed

  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 126 ms

    126 ms

    Real visitors wait 126 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 15% faster for real visitors

    -15%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.4 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).

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.9 s

    0.9 s

    Your largest element renders in 0.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Josh is on a mission to unlock human potential by creating …”.

  • Total Blocking Time: 15 ms

    15 ms

    Scripts block the page for only 15 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90

  • 1 image far larger than shown

    47 KiB

    1 image is downloaded at several times the size a phone draws it, for example 20105c5a3af9-Screenshot-2022-07-28-at-4.57.57-PM.webp at 1,917 px wide, shown at 350 px. Resized copies would save about 47 KiB.

  • About 0.4 g of CO₂ per visit

    0.42 g

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

3 checks passed

  • Page weight: 1.5 MB in 38 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 38 requests on a phone: fonts 968 KiB (8), images 290 KiB (11) and scripts 152 KiB (7). 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.

Accessibility

2 to fixGoogle 9196

  • Certain ARIA roles must be contained by particular parents (3 elements)

    Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.

  • 20 text elements with low contrast

    20 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. (1 element).

2 checks passed

  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 6960

  • Page is set to noindex

    The robots meta tag says “noindex, follow”: Google is told not to list this page at all.

  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • 21 internal links, 15 external

    The homepage links to 21 pages on joshtalks.com and 15 external pages.

7 checks passed

  • Meta description: 152 characters

    Your meta description is 152 characters: “Inspiring, informing and upskilling India in 10 regional languages. Discover inspiring stories, learn English and unloc…”.

  • One H1 headline

    Your main headline reads: “All you need is जोश”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Josh Talks | Inspiring, Informing, Upskilling India”.

  • Canonical URL set

    The canonical URL is https://www.joshtalks.com/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.joshtalks.com/sitemap.xml.

AI search readiness

1 to fix65

  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

2 checks passed

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

4 to fix79

  • 10 linked pages hidden from search

    https://www.joshtalks.com/partners, https://www.joshtalks.com/about-josh, https://www.joshtalks.com/careers, https://www.joshtalks.com/contact-us, https://www.joshtalks.com/privacy-policy and https://www.joshtalks.com/josh-talks and 4 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.joshtalks.com/english-speaking and https://www.joshtalks.com/josh-skills all use the title “Josh Talks English Speaking App - Step by Step English Learning, Admi…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.joshtalks.com/english-speaking and https://www.joshtalks.com/josh-skills use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.joshtalks.com/english-speaking and https://www.joshtalks.com/josh-skills have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 internal pages checked

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

4 checks passed

  • Linked pages load

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

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50

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

  • About 629 words of copy

    The homepage carries about 629 words of visible text.

2 checks passed

  • 1 call to action

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

  • 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

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 joshtalks.com, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on joshtalks.com, including 6 speed issues, 3 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