impo.app

Readiness by lane

Green: impo.app. Thin bar: Fitness & Health peer median.

Priority fixes for impo.app

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://impo.app/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   96% of Fitness & Health peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from Let's Encrypt was due to expire on 2026-11-04 (11 days after the check).

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

   99% of Fitness & Health peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   43% of Fitness & Health peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 58 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 Next.js: The next/image component serves optimized formats automatically.

   45% of Fitness & Health peers do this.

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

What we saw

Homepage checked

https://impo.app/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-04

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

Homepage HTML

248 KB, gzip

Images on homepage

58 (svg 8)

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 Fitness & Health sites

• afyayangu.go.ke48
• haisha-yoyaku.jp46
• juno-beauty-pe.com48
• medic-service.by48
• myhealthatvanderbilt.com47

Fitness & Health readiness benchmark