Website review, no card needed

clinikally.com logo

clinikally.com website review

Visit site (opens in a new tab)Reviewed 4 November 202637 issues · 81 checks

This review found 37 issues worth fixing on clinikally.com, 8 of them high impact, across 81 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

Real-visitor load time (LCP)75th percentile, phones
2.4 s2.1 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
206 ms180 msMay 16Oct 31203 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026184 ms
May 23, 2026185 ms
May 30, 2026186 ms
Jun 6, 2026187 ms
Jun 13, 2026187 ms
Jun 20, 2026186 ms
Jun 27, 2026186 ms
Jul 4, 2026185 ms
Jul 11, 2026185 ms
Jul 18, 2026185 ms
Jul 25, 2026184 ms
Aug 1, 2026184 ms
Aug 8, 2026183 ms
Aug 15, 2026183 ms
Aug 22, 2026183 ms
Aug 29, 2026183 ms
Sep 5, 2026183 ms
Sep 12, 2026184 ms
Sep 19, 2026186 ms
Sep 26, 2026187 ms
Oct 3, 2026191 ms
Oct 10, 2026196 ms
Oct 17, 2026201 ms
Oct 24, 2026203 ms
Oct 31, 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 clinikally.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. clinikally.com at 1.1 s1.1 s
  2. clinikally.com at 2.1 s2.1 s
  3. clinikally.com at 3.2 s3.2 s
  4. clinikally.com at 4.3 s4.3 s
  5. clinikally.com at 5.4 s5.4 s
  6. clinikally.com at 6.4 s6.4 s
  7. clinikally.com at 7.5 s7.5 s
  8. clinikally.com at 8.6 s8.6 s

Speed

9 to fix75
  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 75

    75/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and unbxdapi.com and others), adding 844 KiB and 735 ms of main-thread time.

  • Improve image delivery

    582 KiB

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

  • Google Tag Manager adds 492 ms

    492 ms

    Google Tag Manager costs a phone 492 ms of main-thread work and 586 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 JavaScript

    382 KiB

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

  • Main-thread work: 3.2 s

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

  • 14 long tasks on the main thread

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

  • 2,429 HTML elements

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

  • Use efficient cache lifetimes

    203 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (203 KiB).

  • Legacy JavaScript

    35 KiB

    Polyfills for old browsers add 35 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: 232 ms

    232 ms

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

Core Web Vitals

11 to fix0
  • 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: 15.0 s

    15.0 s

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

  • Total Blocking Time: 712 ms

    712 ms

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 243 ms

    243 ms

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

  • Real-user CLS: 0.15

    0.15

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Speed Index: 4.9 s

    4.9 s

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

  • 20 images without width and height

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fallback Image”. Most of its time is resource load delay (2.3 s).

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

3 checks passed
  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

3 to fix69
  • Page weight: 2.8 MB in 126 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 126 requests on a phone: images 1.3 MB (64), scripts 1.3 MB (35) and other files 102 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Diwali_Compresed_Strip_cb438790a0.gif is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 5 images far larger than shown

    198 KiB

    5 images are downloaded at several times the size a phone draws them, for example App_redirection_mweb_c2a4740eb4.webp at 1,440 px wide, shown at 358 px. Resized copies would save about 198 KiB.

  • 1 image in older formats

    1 image (46 KiB) 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.

  • About 0.8 g of CO₂ per visit

    0.80 g

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

Accessibility

5 to fixGoogle 7991
  • 5 text elements with low contrast

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

  • 3 buttons without a name

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

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

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

2 checks passed
  • Every image has alt text

    All 79 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 3 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 9287
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Clinikally | India's Digital Clinic for Skin & Hair Care That Works!”.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, FAQPage, Organization and SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 101 internal links, 3 external

    The homepage links to 101 pages on clinikally.com and 3 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Find the right treatment that works for your skin & hair type. Consult dermatologists online or get free delivery of th…”.

  • One H1 headline

    Your main headline reads: “How Clinikally Simplifies Your Skin & Hair Care”.

  • Canonical URL set

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

  • 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.clinikally.com/sitemaps/sitemap-index.xml.

AI search readiness

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.clinikally.com/llms.txt (15 KiB, 64 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 83 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

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,219 words of copy

    The homepage carries about 1,219 words of visible text.

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Download our app”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 clinikally.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
Next.js
E-commerce
Shopify;Shopify Plus
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on clinikally.com, including 20 speed issues, 3 SEO issues and 5 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