Website review, no card needed
32dentalcare.org website review
Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 81 checks
This review found 43 issues worth fixing on 32dentalcare.org, 19 of them high impact, across 81 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
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 4.8 s |
| May 30, 2026 | 5.1 s |
| Jun 6, 2026 | 5.3 s |
| Jun 13, 2026 | 5.4 s |
| Jun 20, 2026 | 5.5 s |
| Jun 27, 2026 | 5.4 s |
| Jul 4, 2026 | 5.5 s |
| Jul 11, 2026 | 5.5 s |
| Jul 18, 2026 | 5.4 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.4 s |
| Aug 8, 2026 | 5.3 s |
| Aug 15, 2026 | 5.2 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 5.3 s |
| Sep 12, 2026 | 5.8 s |
| Sep 19, 2026 | 6.4 s |
| Sep 26, 2026 | 6.4 s |
| Oct 3, 2026 | 6.3 s |
| Oct 10, 2026 | 6.2 s |
| Oct 17, 2026 | 6.2 s |
| Oct 24, 2026 | 6.1 s |
| Oct 31, 2026 | 6.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 130 ms |
| May 23, 2026 | 133 ms |
| May 30, 2026 | 150 ms |
| Jun 6, 2026 | 158 ms |
| Jun 13, 2026 | 161 ms |
| Jun 20, 2026 | 167 ms |
| Jun 27, 2026 | 166 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 160 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 157 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 166 ms |
| Aug 15, 2026 | 172 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 163 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 164 ms |
| Sep 19, 2026 | 151 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 167 ms |
| Oct 17, 2026 | 177 ms |
| Oct 24, 2026 | 151 ms |
| Oct 31, 2026 | 164 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
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.2 s
4.8 s
5.5 s
Speed
Reduce unused JavaScript
8.4 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.4 s faster on a phone.
Render-blocking requests
6.0 s66 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.0 s.
Use efficient cache lifetimes
3.9 s · 1.1 MB159 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Improve image delivery
3.0 s · 681 KiB1 image could be 681 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Google CDN adds 1.3 s
1.3 sGoogle CDN costs a phone 1.3 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.2 s
A phone's processor spends 6.2 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Maps and others), adding 3.0 MB and 2.3 s of main-thread time.
Google Tag Manager adds 687 ms
687 msGoogle Tag Manager costs a phone 687 ms of main-thread work and 516 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.
Reduce unused CSS
600 ms · 115 KiBAbout 115 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 305 ms. During a long task the page ignores taps.
Google Maps adds 191 ms
191 msGoogle Maps costs a phone 191 ms of main-thread work and 406 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.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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: 262 ms
262 msYour server sent the HTML in 262 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 LCP: 6.9 s
6.9 sReal visitors wait 6.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.8 s
4.8 sReal visitors see the first content after 4.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.4 s
3.4 sReal visitors wait 3.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 27.5 s
27.5 sYour largest element takes 27.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 29.2 s
29.2 sThe page becomes fully interactive after 29.2 s. Good is under 3.8 s.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.6 s to 6.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.167
0.167The layout shifts by 0.167 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
1 checks passed
Real-user INP: 174 ms
174 msReal visitors wait 174 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 7.9 MB in 217 requests
7.9 MBYour homepage downloads 7.9 MB in 217 requests on a phone: scripts 3.0 MB (78), images 2.9 MB (28) and fonts 919 KiB (12). Under 2 MB keeps phones on slow connections fast.
12 images below the first screen load straight away
12 images further down the page (463 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
119 KiB2 images are downloaded at several times the size a phone draws them, for example infection-control.png at 1,000 px wide, shown at 29 px. Resized copies would save about 119 KiB.
11 images in older formats
11 images (443 KiB) 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.
About 2.3 g of CO₂ per visit
2.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.25 g of CO₂e: 270.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 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.
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
18 form fields without a label
18 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 36 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 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
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
84 internal links, 4 external
The homepage links to 84 pages on 32dentalcare.org and 4 external pages.
8 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “32 Dental Care is the best dental clinic in Chennai. Our team provides exceptional dental care while keeping your comfo…”.
One H1 headline
Your main headline reads: “best dental care in chennai”.
Title: 30 characters
Your title is a healthy 30 characters: “Best 32 Dental Care in Chennai”.
Canonical URL set
The canonical URL is https://www.32dentalcare.org/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.32dentalcare.org/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. 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.32dentalcare.org/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.
1 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.
Other pages
7 pages without a meta description
https://www.32dentalcare.org/management-team, https://www.32dentalcare.org/membership-plans, https://www.32dentalcare.org/individual-membership-plan, https://www.32dentalcare.org/students-membership-plan, https://www.32dentalcare.org/family-membership-plan and https://www.32dentalcare.org/senior-citizen-membership-plan and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 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.
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 broken images
2 images failed to load on a phone, for example https://omnia-digital.com/demo/32-dental/wp-content/uploads/2022/12/logo-1.png.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “ECS_add_action is not defined”.
2 checks passed
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Only about 143 words
The homepage has only about 143 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT” and “CALL NOW”.
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Call Now” and “Talk to dentist”.
3 short forms
3 short forms (6 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 97 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 5 phone links and 2 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
17 other companies contacted
Loading the homepage contacts 17 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 32dentalcare.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Tier 4 Cloud Services
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on 32dentalcare.org, including 26 speed issues, 1 SEO issue and 1 conversion gap. 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.