Website review, no card needed

akhandjyoti.com logo

akhandjyoti.com website review

Visit site (opens in a new tab)Reviewed 20 November 202652 issues · 96 checks

This review found 52 issues worth fixing on akhandjyoti.com, 15 of them high impact, across 96 checks. The most urgent: font display. 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
4.5 s3.5 sMay 30Nov 144.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.6 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.8 s
Jun 27, 20263.8 s
Jul 4, 20263.9 s
Jul 11, 20263.9 s
Jul 18, 20264.0 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.1 s
Aug 15, 20264.1 s
Aug 22, 20264.2 s
Aug 29, 20264.2 s
Sep 5, 20264.2 s
Sep 12, 20264.3 s
Sep 19, 20264.3 s
Sep 26, 20264.3 s
Oct 3, 20264.3 s
Oct 10, 20264.3 s
Oct 17, 20264.3 s
Oct 24, 20264.3 s
Oct 31, 20264.3 s
Nov 7, 20264.4 s
Nov 14, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
312 ms189 msMay 30Nov 14203 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026294 ms
Jun 6, 2026290 ms
Jun 13, 2026291 ms
Jun 20, 2026295 ms
Jun 27, 2026298 ms
Jul 4, 2026288 ms
Jul 11, 2026275 ms
Jul 18, 2026249 ms
Jul 25, 2026223 ms
Aug 1, 2026218 ms
Aug 8, 2026216 ms
Aug 15, 2026209 ms
Aug 22, 2026203 ms
Aug 29, 2026203 ms
Sep 5, 2026205 ms
Sep 12, 2026207 ms
Sep 19, 2026209 ms
Sep 26, 2026209 ms
Oct 3, 2026206 ms
Oct 10, 2026207 ms
Oct 17, 2026207 ms
Oct 24, 2026208 ms
Oct 31, 2026207 ms
Nov 7, 2026205 ms
Nov 14, 2026203 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

Full-page screenshot of akhandjyoti.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. akhandjyoti.com at 2.6 s2.6 s
  2. akhandjyoti.com at 5.2 s5.2 s
  3. akhandjyoti.com at 7.8 s7.8 s
  4. akhandjyoti.com at 10.4 s10.4 s
  5. akhandjyoti.com at 13.0 s13.0 s
  6. akhandjyoti.com at 15.7 s15.7 s
  7. akhandjyoti.com at 18.3 s18.3 s
  8. akhandjyoti.com at 20.9 s20.9 s

Speed

12 to fix60
  • Font display

    3.0 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).

  • Render-blocking requests

    1.8 s

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

  • Use efficient cache lifetimes

    550 ms · 5.4 MB

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

  • Reduce unused JavaScript

    410 ms · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 410 ms faster on a phone.

  • 8 third-party services on the page

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

  • Mobile performance score: 60

    60/100

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

  • Reduce unused CSS

    450 ms · 203 KiB

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

  • YouTube adds 385 ms

    385 ms

    YouTube costs a phone 385 ms of main-thread work and 1,003 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.

  • Freshchat adds 354 ms

    354 ms

    Freshchat costs a phone 354 ms of main-thread work and 854 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 367 ms

    367 ms

    Google Tag Manager costs a phone 367 ms of main-thread work and 529 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: 3.2 s

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

  • 2,534 HTML elements

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

  • 16 long tasks on the main thread

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

  • Minify CSS

    150 ms · 11 KiB

    11 KiB could be saved by minifying CSS.

  • Improve image delivery

    150 KiB

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

1 checks passed
  • Server response: 496 ms

    496 ms

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

Core Web Vitals

10 to fix33
  • 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.

  • Time to Interactive: 42.3 s

    42.3 s

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

  • Speed Index: 15.0 s

    15.0 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user INP: 218 ms

    218 ms

    Real visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.4 s

    2.4 s

    Real visitors see the first content after 2.4 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.

  • Largest Contentful Paint: 4.0 s

    4.0 s

    Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Super Speciality Eye Hospital Network”. Most of its time is element render delay (4.3 s).

  • Total Blocking Time: 418 ms

    418 ms

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

  • Largest content (LCP) got 19% slower for real visitors

    +19%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 30% faster for real visitors

    -30%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

5 to fix28
  • Page weight: 7.9 MB in 233 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 233 requests on a phone: images 4.8 MB (149), scripts 2.6 MB (36) and stylesheets 230 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    blog_30ab3e3e6e4131f28b896096d82dea81.png weighs 591 KiB. On a phone connection a single image that size takes seconds.

  • 38 images below the first screen load straight away

    38 images further down the page (3.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images in older formats

    5 images (1.1 MB) are 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 far larger than shown

    75 KiB

    1 image is downloaded at several times the size a phone draws it, for example AJEH - Logo - 2000x2000px-English_croped.png at 2,000 px wide, shown at 120 px. Resized copies would save about 75 KiB.

  • About 2.2 g of CO₂ per visit

    2.24 g

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

Accessibility

12 to fixGoogle 7184
  • 20 buttons without a name

    20 buttons have no accessible name, so screen readers announce just “button”.

  • 23 text elements with low contrast

    23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Orphan list items

    Some list items are not inside a list.

  • All page content should be contained by landmarks (38 elements)

    All page content should be contained by landmarks: 38 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.

  • 14 form fields without a label

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

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (10 elements)

    ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (10 elements)

    Elements marked as presentational should be consistently ignored: 10 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h6, h2 → h6 and h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 156 images in the HTML carry an alt attribute.

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

SEO

4 to fixGoogle 8588
  • 3 H1 headlines

    There are 3 <h1> headlines (“Welcome to Akhand Jyoti Eye Hospital”, “Welcome to Akhand Jyoti Eye Hospital” and “Our Hospital Network”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 12 links crawlers can't follow

    12 links have no real href, so search engines can't follow them.

  • 12 links with vague text

    12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 276 internal links, 20 external

    The homepage links to 276 pages on akhandjyoti.com and 20 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Searching for ‘eye hospital near me?’ Click here for Akhand Jyoti Eye Hospital – best eye hospital in Bihar and largest…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Best Eye Hospital In Bihar | Akhand Jyoti Eye Hospital”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: MedicalOrganization.

  • 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.akhandjyoti.com/sitemap.xml.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    58%

    The HTML your server sends has 4,521 of the 7,775 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

  • Organization data: 6 of 6 facts

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

Other pages

2 to fix70
  • 3 linked pages are broken

    Your homepage links to https://www.akhandjyoti.com/cataract-surgery-preparation-planning, https://www.akhandjyoti.com/types-of-cataract-lenses and https://www.akhandjyoti.com/about-us, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 3 pages without an H1

    https://www.akhandjyoti.com/our-locations, https://www.akhandjyoti.com/privacy-policy and https://www.akhandjyoti.com/terms-of-use have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • 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.

  • 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 12 pages that loaded have a <title>.

Best practices

5 to fixGoogle 6969
  • 4 broken images

    4 images failed to load on a phone, for example https://www.akhandjyoti.com/storage/blog/list/blog_7eb86d2fe359f592bf69324182d9267b.webp.

  • 18 small tap targets

    18 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR”.

  • 9 distorted images

    9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 7,775 words of copy

    The homepage carries about 7,775 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call Back” and “Register / Login”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Call Back”, “BOOK DOCTOR APPOINTMENT” and “CONTACT US”.

  • 5 short forms

    5 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 25 testimonial or review blocks, 2 trust badges and “24,59,500+ Happy Patients”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 2 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 2 of them by other companies (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.

  • 26 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
AWS

Hiring

Hiring
1 open role
Job board
careers page

Company

Founded
2005
Headquarters
Saran District

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on akhandjyoti.com, including 22 speed issues and 4 SEO issues. 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