Tools & Wizards About Us
kaya.in screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 0

    Best Practices

  • 75

    SEO

    Google-friendlier than
    32% of websites

kaya.in

Kaya - Skin and Hair Care Services, Treatments & Products in India

Page Load Speed

5.4 sec in total

First Response

467 ms

Resources Loaded

4.6 sec

Page Rendered

291 ms

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

Kaya - Skin Care & Hair Care Services, Treatments & Dermatologically tested Products Range. Visit website for treatment details for concerns such as Acne, Anti-aging, Hair loss

Visit kaya.in

Key Findings

We analyzed Kaya.in page load time and found that the first response time was 467 ms and then it took 4.9 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

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value1,470 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value1.134

1/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

kaya.in

467 ms

www.kaya.in

647 ms

system.base.css

199 ms

system.menus.css

393 ms

system.messages.css

394 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 97% of them (74 requests) were addressed to the original Kaya.in, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Kaya.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 478.1 kB (30%)

Content Size

1.6 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kaya.in main page is 1.6 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. 50% of websites need less resources to load. Images take 963.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 62.1 kB

  • Original 71.2 kB
  • After minification 55.4 kB
  • After compression 9.1 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 15.9 kB, which is 22% 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 62.1 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 7.2 kB

  • Original 963.4 kB
  • After minification 956.3 kB

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

-66%

Potential reduce by 159.2 kB

  • Original 241.5 kB
  • After minification 210.1 kB
  • After compression 82.4 kB

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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 159.2 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 249.6 kB

  • Original 295.6 kB
  • After minification 247.7 kB
  • After compression 46.0 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 249.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (64%)

Requests Now

70

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 70 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 14 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

kaya.in

kaya.in

467 ms

www.kaya.in

www.kaya.in

647 ms

system.base.css

system.base.css

199 ms

system.menus.css

system.menus.css

393 ms

system.messages.css

system.messages.css

394 ms

system.theme.css

system.theme.css

395 ms

field.css

field.css

397 ms

node.css

node.css

396 ms

search.css

search.css

398 ms

user.css

user.css

585 ms

views.css

views.css

586 ms

ckeditor.css

ckeditor.css

587 ms

ctools.css

ctools.css

588 ms

slick.css

slick.css

588 ms

bootstrap.min.css

bootstrap.min.css

797 ms

style.css

style.css

975 ms

media_query.css

media_query.css

785 ms

gcse.css

gcse.css

780 ms

print.css

print.css

784 ms

jquery.min.js

jquery.min.js

1033 ms

jquery.once.js

jquery.once.js

1030 ms

drupal.js

drupal.js

1032 ms

modernizr.custom.79639.js

modernizr.custom.79639.js

1030 ms

slick.js

slick.js

1099 ms

jquery.masonry.min.js

jquery.masonry.min.js

1166 ms

hover_intent.js

hover_intent.js

1168 ms

main.js

main.js

1171 ms

home.js

home.js

1175 ms

testimonial.js

testimonial.js

1177 ms

book_appoinment.js

book_appoinment.js

1191 ms

video.js

video.js

1359 ms

small_menu.js

small_menu.js

1362 ms

analytics.js

analytics.js

117 ms

small_logo.jpg

small_logo.jpg

464 ms

meet_icon.png

meet_icon.png

464 ms

dropdown_img.png

dropdown_img.png

465 ms

search.png

search.png

466 ms

close_search.png

close_search.png

558 ms

logo.png

logo.png

561 ms

banner2.jpg

banner2.jpg

953 ms

mob_banner2.jpg

mob_banner2.jpg

759 ms

banner1.jpg

banner1.jpg

959 ms

mob_banner1.jpg

mob_banner1.jpg

989 ms

banner4.jpg

banner4.jpg

1532 ms

mob_banner4.jpg

mob_banner4.jpg

1146 ms

banner3.jpg

banner3.jpg

1540 ms

mob_banner3.jpg

mob_banner3.jpg

1150 ms

left_quotes.png

left_quotes.png

1156 ms

right_quotes.png

right_quotes.png

1189 ms

DrSangeeta.jpg

DrSangeeta.jpg

1344 ms

small_video.png

small_video.png

1345 ms

unnamed_0.jpg

unnamed_0.jpg

1351 ms

close_light.png

close_light.png

1387 ms

blog_rounded.png

blog_rounded.png

1539 ms

kaya_blog3.png

kaya_blog3.png

1930 ms

blog_icon.png

blog_icon.png

1523 ms

kaya_blog4.png

kaya_blog4.png

1957 ms

kaya_blog1.png

kaya_blog1.png

1892 ms

kaya_blog2.png

kaya_blog2.png

2038 ms

product1.jpg

product1.jpg

1639 ms

OpenSans-Semibold.woff

OpenSans-Semibold.woff

1845 ms

collect

collect

13 ms

OpenSans.woff

OpenSans.woff

1969 ms

CantataOne-Regular.woff

CantataOne-Regular.woff

1952 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

2148 ms

product2.jpg

product2.jpg

1980 ms

product3.jpg

product3.jpg

2008 ms

product4.jpg

product4.jpg

2123 ms

social_sprite.png

social_sprite.png

1978 ms

webmaffia_logo.png

webmaffia_logo.png

1880 ms

book_appointment.png

book_appointment.png

1879 ms

sign_sprite.png

sign_sprite.png

1922 ms

select_arrow.png

select_arrow.png

2047 ms

scroll_arrow.png

scroll_arrow.png

2055 ms

prev_arrow.png

prev_arrow.png

1966 ms

next_arrow.png

next_arrow.png

1964 ms

Accessibility Review

kaya.in accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

SEO Factors

kaya.in SEO score

75

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • 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 neither this language nor any other was claimed in <html> or <meta> tags. 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: