Tools & Wizards About Us
kaya.in screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

kaya.in

Kaya Clinic: Best Clinic for Skin, Hair & Weight Loss Treatments by Top Doctors in India

Page Load Speed

4.8 sec in total

First Response

385 ms

Resources Loaded

3.2 sec

Page Rendered

1.3 sec

kaya.in screenshot

About Website

Click here to check amazing Kaya content for India. Otherwise, check out these important facts you probably never knew about kaya.in

Discover Kaya Clinic, the best skin clinic in India for top skin, hair, and weight loss treatments by leading dermatologists. Achieve your beauty goals today!

Visit kaya.in

Key Findings

We analyzed Kaya.in page load time and found that the first response time was 385 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

kaya.in performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.9 s

0/100

25%

SI (Speed Index)

Value45.5 s

0/100

10%

TBT (Total Blocking Time)

Value37,190 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.385

27/100

15%

TTI (Time to Interactive)

Value76.7 s

0/100

10%

Network Requests Diagram

kaya.in

385 ms

www.kaya.in

29 ms

cae8bfad0f72443600e86c16daf2d1fd.min.css

19 ms

styles-l.min.css

59 ms

bd69b8176d9fd1d0a5963ccb2866c698.min.js

113 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 71% of them (65 requests) were addressed to the original Kaya.in, 8% (7 requests) were made to Cdnjs.cloudflare.com and 7% (6 requests) were made to Mcstaging.kaya.in. The less responsive or slowest element that took the longest time to load (864 ms) relates to the external source Inzd3a49ba7.in.webengage.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 409.9 kB (10%)

Content Size

4.1 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kaya.in main page is 4.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 242.3 kB

  • Original 294.2 kB
  • After minification 237.0 kB
  • After compression 51.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 57.2 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 242.3 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 25.8 kB

  • Original 2.3 MB
  • After minification 2.2 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Kaya images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 123 B

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-65%

Potential reduce by 141.7 kB

  • Original 217.3 kB
  • After minification 75.7 kB
  • After compression 75.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Kaya.in needs all CSS files to be minified and compressed as it can save up to 141.7 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (27%)

Requests Now

73

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kaya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

kaya.in

kaya.in

385 ms

www.kaya.in

www.kaya.in

29 ms

cae8bfad0f72443600e86c16daf2d1fd.min.css

cae8bfad0f72443600e86c16daf2d1fd.min.css

19 ms

styles-l.min.css

styles-l.min.css

59 ms

bd69b8176d9fd1d0a5963ccb2866c698.min.js

bd69b8176d9fd1d0a5963ccb2866c698.min.js

113 ms

chatbot.js

chatbot.js

682 ms

all.css

all.css

109 ms

all.min.css

all.min.css

96 ms

font-awesome.min.css

font-awesome.min.css

112 ms

js

js

241 ms

js

js

242 ms

font-awesome.min.css

font-awesome.min.css

91 ms

css

css

92 ms

print.min.css

print.min.css

127 ms

js-translation.json

js-translation.json

19 ms

gtm.js

gtm.js

112 ms

bat.js

bat.js

184 ms

Kaya_SHB_Black_Logo.jpg

Kaya_SHB_Black_Logo.jpg

72 ms

icons8-phone-24.png

icons8-phone-24.png

250 ms

Header-1.jpg

Header-1.jpg

170 ms

Header-2.jpg

Header-2.jpg

169 ms

header-3.jpg

header-3.jpg

170 ms

Header-4.jpg

Header-4.jpg

171 ms

StripsDesktop2024.jpg

StripsDesktop2024.jpg

251 ms

desktop_1__5.jpg

desktop_1__5.jpg

217 ms

mobile_6_.jpg

mobile_6_.jpg

203 ms

desktop_1__3.jpg

desktop_1__3.jpg

204 ms

mobile1.jpg

mobile1.jpg

204 ms

desktop_75.jpg

desktop_75.jpg

204 ms

mobile_78.jpg

mobile_78.jpg

244 ms

customer_satisfaction_score_desktop.jpg

customer_satisfaction_score_desktop.jpg

245 ms

customer_satisfaction_score_mobile.jpg

customer_satisfaction_score_mobile.jpg

566 ms

pune_banner-now_open.jpg

pune_banner-now_open.jpg

247 ms

pune_banner-now_open_mobile.jpg

pune_banner-now_open_mobile.jpg

250 ms

Hair_Care_Product_Desktop.jpg

Hair_Care_Product_Desktop.jpg

564 ms

Hair_Care_Product_Mobile.jpg

Hair_Care_Product_Mobile.jpg

255 ms

Anti-Ageing_Desktop.jpg

Anti-Ageing_Desktop.jpg

251 ms

Anti-Ageing_Mobile.jpg

Anti-Ageing_Mobile.jpg

252 ms

Body_Care_Desktop.jpg

Body_Care_Desktop.jpg

253 ms

Body_Care_Mobile.jpg

Body_Care_Mobile.jpg

256 ms

LHR_Desktop.jpg

LHR_Desktop.jpg

255 ms

LHR_Mobile.jpg

LHR_Mobile.jpg

257 ms

Skin_Care_Desktop.jpg

Skin_Care_Desktop.jpg

258 ms

Skin_Care_Mobile.jpg

Skin_Care_Mobile.jpg

257 ms

Hair_Care_Desktop.jpg

Hair_Care_Desktop.jpg

257 ms

Hair_Care_Mobile.jpg

Hair_Care_Mobile.jpg

259 ms

Desktop_31.jpg

Desktop_31.jpg

261 ms

Mobile_31.jpg

Mobile_31.jpg

260 ms

Creams_Moisturizers_1.jpg

Creams_Moisturizers_1.jpg

259 ms

Face_Wash_1.jpg

Face_Wash_1.jpg

260 ms

Hair_Masque_1.jpg

Hair_Masque_1.jpg

261 ms

Serum_2.jpg

Serum_2.jpg

261 ms

Toner_3.jpg

Toner_3.jpg

314 ms

Dullness_2.jpg

Dullness_2.jpg

315 ms

webengage-min-v-6.0.js

webengage-min-v-6.0.js

219 ms

Acne_4.jpg

Acne_4.jpg

250 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

136 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

136 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

312 ms

fa-regular-400.ttf

fa-regular-400.ttf

176 ms

fa-brands-400.ttf

fa-brands-400.ttf

177 ms

fa-solid-900.ttf

fa-solid-900.ttf

178 ms

Poppins-Bold.ttf

Poppins-Bold.ttf

152 ms

Poppins-Medium.ttf

Poppins-Medium.ttf

152 ms

Poppins-Regular.ttf

Poppins-Regular.ttf

152 ms

Poppins-Light.ttf

Poppins-Light.ttf

151 ms

97061101.js

97061101.js

68 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

364 ms

Pigmentation_1.jpg

Pigmentation_1.jpg

119 ms

Anti_Ageing_5.jpg

Anti_Ageing_5.jpg

120 ms

Dryness_2.jpg

Dryness_2.jpg

119 ms

Luma-Icons.woff

Luma-Icons.woff

323 ms

Indian_Skin.png.jpg

Indian_Skin.png.jpg

79 ms

100_Safe.png.jpg

100_Safe.png.jpg

81 ms

Dermat_Tested.png.jpg

Dermat_Tested.png.jpg

79 ms

Twitter_1.png

Twitter_1.png

78 ms

Facebook_1_.png

Facebook_1_.png

77 ms

Linkedin_1.png

Linkedin_1.png

77 ms

Instagram.png

Instagram.png

76 ms

shopping-bag.png

shopping-bag.png

310 ms

MD-Icon.ttf

MD-Icon.ttf

61 ms

kaya-icons.woff

kaya-icons.woff

287 ms

kaya-icon.woff

kaya-icon.woff

288 ms

storage-frame-1.13.htm

storage-frame-1.13.htm

864 ms

User.png

User.png

279 ms

Phone_receiver_silhouette.png

Phone_receiver_silhouette.png

310 ms

_1.png

_1.png

401 ms

data1.png

data1.png

420 ms

Place.png

Place.png

420 ms

FaunaOne-Regular.ttf

FaunaOne-Regular.ttf

30 ms

v4.js

v4.js

847 ms

Accessibility Review

kaya.in accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kaya.in best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

kaya.in SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kaya.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Kaya.in main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

kaya.in

Open Graph description is not detected on the main page of Kaya. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: