tawk.to

Readiness by lane

Green: tawk.to. Thin bar: Workplace Productivity peer median.

Priority fixes for tawk.to

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   59% of Workplace Productivity peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for tawk.to was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   63% of Workplace Productivity peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   80% of Workplace Productivity peers do this.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 75 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   49% of Workplace Productivity peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

What tawk.to already does well

Practices fewer than half of Workplace Productivity peers use.

• HTTP/3 advertisedHTTP/3 advertised.27% of peers
• Reachable over IPv6IPv6 address published.38% of peers
• Referrer-Policy setReferrer-Policy present.40% of peers

What we saw

Homepage checked

https://tawk.to/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-11-28

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 0 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

598 KB, br

Images on homepage

75 (jpg 28, png 27, svg 20)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Workplace Productivity sites

• easydoct.com60
• kaikatsu.jp55
• machicomi.jp58
• podio.com55
• tricare.jp59

Workplace Productivity readiness benchmark