Tools & Wizards About Us
wati.io screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wati.io

Wati | Business Messaging Made Simple on Your Favourite App!

Page Load Speed

2 sec in total

First Response

120 ms

Resources Loaded

1.3 sec

Page Rendered

523 ms

wati.io screenshot

About Website

Click here to check amazing Wati content for India. Otherwise, check out these important facts you probably never knew about wati.io

Trusted by the fastest growing brands in over 78 countries. Wati is the #1 end-to-end WhatsApp API solution for SMBs across the globe.

Visit wati.io

Key Findings

We analyzed Wati.io page load time and found that the first response time was 120 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wati.io performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value4.5 s

71/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

www.wati.io

120 ms

css2

60 ms

style.css

96 ms

jquery.min.js

104 ms

wow.min.js

35 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 67% of them (61 requests) were addressed to the original Wati.io, 5% (5 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (418 ms) relates to the external source App.hyperise.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.6 kB (42%)

Content Size

467.4 kB

After Optimization

271.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wati.io main page is 467.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. HTML takes 231.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 187.6 kB

  • Original 231.1 kB
  • After minification 196.2 kB
  • After compression 43.5 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 34.9 kB, which is 15% 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 187.6 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 2 B

  • Original 51.9 kB
  • After minification 51.9 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. Wati images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 7.9 kB

  • Original 179.1 kB
  • After minification 179.1 kB
  • After compression 171.2 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

-1%

Potential reduce by 75 B

  • Original 5.3 kB
  • After minification 5.3 kB
  • After compression 5.2 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. Wati.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (36%)

Requests Now

85

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wati.io

www.wati.io

120 ms

css2

css2

60 ms

style.css

style.css

96 ms

jquery.min.js

jquery.min.js

104 ms

wow.min.js

wow.min.js

35 ms

lottie-player.js

lottie-player.js

56 ms

lazy_load.js

lazy_load.js

48 ms

bootstrap.min.js

bootstrap.min.js

48 ms

tapfiliate.js

tapfiliate.js

43 ms

2858726.js

2858726.js

66 ms

comment-reply.min.js

comment-reply.min.js

46 ms

gtm.js

gtm.js

247 ms

jyk0nmwqax

jyk0nmwqax

167 ms

wati-logo-1.svg

wati-logo-1.svg

45 ms

shout-whatsapp-copy-2.png

shout-whatsapp-copy-2.png

42 ms

arow-right.svg

arow-right.svg

42 ms

No-card-icon.svg

No-card-icon.svg

45 ms

wati-dashboard.webp

wati-dashboard.webp

43 ms

wati-communicate.webp

wati-communicate.webp

46 ms

gojek.svg

gojek.svg

76 ms

tiktok.svg

tiktok.svg

63 ms

dukan.svg

dukan.svg

52 ms

Welspun-logo.svg

Welspun-logo.svg

54 ms

Changi-airport.svg

Changi-airport.svg

61 ms

Za-insure-logo.svg

Za-insure-logo.svg

68 ms

fusion.svg

fusion.svg

76 ms

JP-morgan-bank.svg

JP-morgan-bank.svg

73 ms

We-lend-logo.svg

We-lend-logo.svg

110 ms

Ngong-Ping-360.svg

Ngong-Ping-360.svg

104 ms

Zoomar.svg

Zoomar.svg

128 ms

swine.svg

swine.svg

112 ms

ytt_logo.png

ytt_logo.png

104 ms

mivi.svg

mivi.svg

108 ms

Oxwhitee.svg

Oxwhitee.svg

209 ms

edureka.svg

edureka.svg

143 ms

Adventurrush.svg

Adventurrush.svg

134 ms

Emami.svg

Emami.svg

146 ms

Killer.svg

Killer.svg

138 ms

ITC.svg

ITC.svg

141 ms

Pillup.svg

Pillup.svg

210 ms

TVS-assure-1.svg

TVS-assure-1.svg

214 ms

Vedantu.svg

Vedantu.svg

211 ms

Li-ning-svg.svg

Li-ning-svg.svg

214 ms

Habuildd.png

Habuildd.png

219 ms

Vedantuhome.png

Vedantuhome.png

217 ms

inves.jpg

inves.jpg

218 ms

zellbury.svg

zellbury.svg

222 ms

Broadcasst.webp

Broadcasst.webp

225 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1C4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1C4E.ttf

79 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1C4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1C4E.ttf

124 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61C4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61C4E.ttf

143 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yC4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yC4E.ttf

130 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyC4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyC4E.ttf

129 ms

tickk.svg

tickk.svg

217 ms

2858726.js

2858726.js

123 ms

fb.js

fb.js

104 ms

web-interactives-embed.js

web-interactives-embed.js

130 ms

2858726.js

2858726.js

126 ms

Botfloow.webp

Botfloow.webp

187 ms

Team-Inbox-.webp

Team-Inbox-.webp

204 ms

sht.svg

sht.svg

191 ms

zoho.svg

zoho.svg

186 ms

shopify_logo_whitebg.svg

shopify_logo_whitebg.svg

190 ms

google-sheets-full-logo-1.svg

google-sheets-full-logo-1.svg

196 ms

Hubspot.svg

Hubspot.svg

188 ms

zapier-logo_black.svg

zapier-logo_black.svg

194 ms

Pabbly-Connect-SVG.svg

Pabbly-Connect-SVG.svg

174 ms

woocommerce-logo-color-black.svg

woocommerce-logo-color-black.svg

182 ms

clarity.js

clarity.js

43 ms

make.svg

make.svg

183 ms

brk.webp

brk.webp

176 ms

ups.webp

ups.webp

188 ms

sscale.webp

sscale.webp

186 ms

chhnl.webp

chhnl.webp

160 ms

watidot.png

watidot.png

160 ms

dro.svg

dro.svg

158 ms

js

js

93 ms

js

js

160 ms

destination

destination

154 ms

ibwit25i2x

ibwit25i2x

56 ms

insight.min.js

insight.min.js

242 ms

tfa.js

tfa.js

139 ms

fbevents.js

fbevents.js

137 ms

dreamdata.min.js

dreamdata.min.js

247 ms

identify-form.min.js

identify-form.min.js

246 ms

crypto-js.min.js

crypto-js.min.js

111 ms

jo9ZpCEiO.js

jo9ZpCEiO.js

418 ms

c.gif

c.gif

45 ms

insight.old.min.js

insight.old.min.js

44 ms

p

p

97 ms

insight_tag_errors.gif

insight_tag_errors.gif

156 ms

Accessibility Review

wati.io accessibility score

91

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

Best Practices

wati.io 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

wati.io SEO score

93

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

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

    PT

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wati.io can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Wati.io 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

wati.io

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