Website review, no card needed

rx360.in logo

rx360.in website review

Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 83 checks

This review found 38 issues worth fixing on rx360.in, 15 of them high impact, across 83 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

Full-page screenshot of rx360.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rx360.in at 0.6 s0.6 s
  2. rx360.in at 1.3 s1.3 s
  3. rx360.in at 1.9 s1.9 s
  4. rx360.in at 2.5 s2.5 s
  5. rx360.in at 3.1 s3.1 s
  6. rx360.in at 3.8 s3.8 s
  7. rx360.in at 4.4 s4.4 s
  8. rx360.in at 5.0 s5.0 s

Speed

9 to fix54
  • Render-blocking requests

    10.8 s

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

  • Reduce unused JavaScript

    4.2 s · 827 KiB

    About 827 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

  • Reduce unused CSS

    3.6 s · 738 KiB

    About 738 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.6 s faster on a phone.

  • Use efficient cache lifetimes

    2.9 s · 1.1 MB

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

  • Minify JavaScript

    900 ms · 166 KiB

    166 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 54

    54/100

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

  • Font display

    500 ms

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

  • Improve image delivery

    345 KiB

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

  • Google Maps adds 97 ms

    97 ms

    Google Maps costs a phone 97 ms of main-thread work and 397 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google Maps and YouTube and others), adding 799 KiB and 235 ms of main-thread time.

  • Minify CSS

    150 ms · 37 KiB

    37 KiB could be saved by minifying CSS.

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    9 KiB

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 256 ms

    256 ms

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

Core Web Vitals

5 to fix66
  • First Contentful Paint: 9.0 s

    9.0 s

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

  • Largest Contentful Paint: 17.0 s

    17.0 s

    Your largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Discover Dental Clinics Near You”.

  • Speed Index: 11.7 s

    11.7 s

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

  • Time to Interactive: 17.0 s

    17.0 s

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

  • 18 images without width and height

    18 images have no width and height attributes, so the layout jumps as each one loads.

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

2 checks passed
  • Total Blocking Time: 124 ms

    124 ms

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

  • Cumulative Layout Shift: 0.01

    0.01

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

Images and page weight

1 to fix70
  • Page weight: 8.1 MB in 136 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 136 requests on a phone: media 4.5 MB (1), scripts 1.5 MB (57) and stylesheets 824 KiB (41). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (145 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.30 g

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

2 checks passed
  • 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

8 to fixGoogle 7389
  • 48 text elements with low contrast

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

  • 13 tap targets too small

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

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

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

  • 16 links without text

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

  • 3 form fields without a label

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

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

4 to fixGoogle 8586
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Doctor Nearby: Find Best Dentist, Doctor, Hostpital, Clinic Near You”.

  • No social preview image

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

  • 5 links crawlers can't follow

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

  • 4 links with vague text

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

  • 76 internal links, 3 external

    The homepage links to 76 pages on rx360.in and 3 external pages.

6 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Find the best Dentist, Doctors, Hospitals, and Clinics near you effortlessly. Our user-friendly platform simplifies the…”.

  • One H1 headline

    Your main headline reads: “Find Best Dentist Online for Your Oral Health”.

  • Canonical URL set

    The canonical URL is https://rx360.in/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage 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://rx360.in/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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://rx360.in/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 (977 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 3 linked pages are broken

    Your homepage links to https://rx360.in/category/dental-clinic, https://rx360.in/listing/dr-namrata-patil-shiwalkar-dent-o-fit-total-dental-fitness-centre and https://rx360.in/listing/chopade-dental-clinic, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 8 pages without a meta description

    https://rx360.in/category/aesthetic-dentistry, https://rx360.in/category/crown-bridge, https://rx360.in/category/prosthodontist, https://rx360.in/category/implantology, https://rx360.in/category/laser-dentistry and https://rx360.in/category/endodontics and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://rx360.in/location/delhi, https://rx360.in/location/mumbai, https://rx360.in/location/nagpur, https://rx360.in/location/pune, https://rx360.in/category/aesthetic-dentistry and https://rx360.in/category/crown-bridge and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://rx360.in/category/aesthetic-dentistry, https://rx360.in/category/crown-bridge, https://rx360.in/category/prosthodontist, https://rx360.in/category/implantology, https://rx360.in/category/laser-dentistry and https://rx360.in/category/endodontics and 1 other 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 32 found) and read each the way a search engine does.

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

  • 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

4 to fixGoogle 9270
  • 2 broken images

    2 images failed to load on a phone, for example https://rx360.in/.

  • 2 small tap targets

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

  • 3 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 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 632 words of copy

    The homepage carries about 632 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies, 1 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.

  • 7 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Oracle Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on rx360.in, including 14 speed issues, 4 SEO issues and 2 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