Report Summary

  • 15

    Performance

    Renders faster than
    28% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

haptik.ai

Haptik: Accelerating the World’s Transition to Conversational Commerce

Page Load Speed

6.9 sec in total

First Response

489 ms

Resources Loaded

4.8 sec

Page Rendered

1.6 sec

haptik.ai screenshot

About Website

Click here to check amazing Haptik content for India. Otherwise, check out these important facts you probably never knew about haptik.ai

Haptik helps brands acquire, convert, engage, & delight users with AI-driven, personalized, conversational experiences across 20 channels & 100+ languages.

Visit haptik.ai

Key Findings

We analyzed Haptik.ai page load time and found that the first response time was 489 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

haptik.ai performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value33.4 s

0/100

25%

SI (Speed Index)

Value31.3 s

0/100

10%

TBT (Total Blocking Time)

Value35,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.124

83/100

15%

TTI (Time to Interactive)

Value47.3 s

0/100

10%

Network Requests Diagram

www.haptik.ai

489 ms

module_82307007328_Announcement.min.css

327 ms

module_81084098708_HP_New_Mega_Menu_2022.min.css

705 ms

module_35276266267_HP_GIF_and_Image_Two_Column_Module.min.css

703 ms

module_34344905173_Haptik_Heading_Module.min.css

687 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 59% of them (71 requests) were addressed to the original Haptik.ai, 6% (7 requests) were made to Use.typekit.net and 5% (6 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Haptik.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 219.3 kB (18%)

Content Size

1.2 MB

After Optimization

1.0 MB

In fact, the total size of Haptik.ai main page is 1.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 923.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 140.3 kB

  • Original 168.2 kB
  • After minification 139.5 kB
  • After compression 27.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 28.7 kB, which is 17% 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 140.3 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 46.4 kB

  • Original 923.8 kB
  • After minification 877.4 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. Haptik images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 24.5 kB

  • Original 67.3 kB
  • After minification 67.3 kB
  • After compression 42.7 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 24.5 kB or 36% of the original size.

CSS Optimization

-11%

Potential reduce by 8.1 kB

  • Original 72.4 kB
  • After minification 72.4 kB
  • After compression 64.3 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. Haptik.ai needs all CSS files to be minified and compressed as it can save up to 8.1 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (55%)

Requests Now

109

After Optimization

49

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

Accessibility Review

haptik.ai accessibility score

95

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

haptik.ai best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

haptik.ai SEO score

79

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 Haptik.ai 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 Haptik.ai 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 Haptik. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: