kpay.com.kw

Readiness by lane

Green: kpay.com.kw. Thin bar: Online Payment & Wallets peer median.

Priority fixes for kpay.com.kw

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 180 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.

   60% of Online Payment & Wallets 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 · 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.

   73% of Online Payment & Wallets peers do this.

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

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 19 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.

   47% of Online Payment & Wallets peers do this.

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

4. Priority 4 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   62% of Online Payment & Wallets peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

What kpay.com.kw already does well

Practices fewer than half of Online Payment & Wallets peers use.

• HTTP/3 advertisedHTTP/3 advertised.35% of peers
• Referrer-Policy setReferrer-Policy present.37% of peers
• Certificate lifetime of 100 days or lessShort-lived 90-day certificate from Google Trust Services, already inside the 2027 limit.44% of peers

What we saw

Homepage checked

https://www.kpay.com.kw/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 180 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

15 KB, gzip

Images on homepage

19 (jpg 17, png 2)

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 Online Payment & Wallets sites

• 168-mrt.com51
• avalpaycenter.com54
• mycard520.com55
• supergiros.com.co55
• ukubwancamp.store52

Online Payment & Wallets readiness benchmark