Tools & Wizards About Us

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

keka.com

Complete HR & Payroll Software | Keka

Page Load Speed

7.1 sec in total

First Response

466 ms

Resources Loaded

5.4 sec

Page Rendered

1.2 sec

About Website

Visit keka.com now to see the best up-to-date Keka content for India and also check out these interesting facts you probably never knew about keka.com

Keka is the complete HR and Payroll Software, offering a best HRMS for businesses of all sizes and industries. Sign up for 7-day free trial!

Visit keka.com

Key Findings

We analyzed Keka.com page load time and found that the first response time was 466 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

keka.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value2,730 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.251

49/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

Network Requests Diagram

keka.com

466 ms

keka.com

941 ms

www.keka.com

1568 ms

new2024.css

455 ms

bootstrap.min.css

18 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 39% of them (24 requests) were addressed to the original Keka.com, 53% (33 requests) were made to D2w2i7rp1a0wob.cloudfront.net and 6% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Keka.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 216.5 kB (7%)

Content Size

3.1 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Keka.com main page is 3.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.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 108.4 kB

  • Original 129.8 kB
  • After minification 92.5 kB
  • After compression 21.4 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 37.3 kB, which is 29% 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 108.4 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 101.2 kB

  • Original 2.8 MB
  • After minification 2.7 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. Keka images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 2.5 kB

  • Original 68.1 kB
  • After minification 68.1 kB
  • After compression 65.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 4.4 kB

  • Original 75.8 kB
  • After minification 75.8 kB
  • After compression 71.4 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. Keka.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (29%)

Requests Now

58

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

keka.com accessibility score

87

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Best Practices

keka.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

keka.com SEO score

93

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

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

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 Keka.com 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 Keka.com 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

Open Graph data is detected on the main page of Keka. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: