STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

rulai.org

rulai.org's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.

Readiness index
46/100

Uncategorized median 62

Ahead of
11%

of measured Uncategorized sites

Practices observed
11/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:13:41 UTC from one location. How we measure

Readiness by lane

Green: rulai.org. Thin bar: Uncategorized peer median.

Enable

56/100

Peers 80

Harden

48/100

Peers 54

Accelerate

35/100

Peers 58

Recover

0/100

Peers 12

Priority fixes for rulai.org

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

  1. Priority 1 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

    Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    87% of Uncategorized peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · 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.

    75% of Uncategorized peers do this.

  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.

    34% of Uncategorized peers do this.

  4. Priority 4 · Accelerate

    Modern image formats in use

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

    33% of Uncategorized peers do this.

What rulai.org already does well

Practices fewer than half of Uncategorized peers use.

  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
  • Static files cached for 30 days or moreLong-lived caching on static files.44% of peers

What we saw

Homepage checked
https://www.rulai.org/
Homepage response
HTTP 200
TLS
TLSv1.3, http/1.1
Certificate
GoDaddy, 397-day validity, expiring 2027-01-28
DNS operators
GoDaddy DNS
DMARC policy
p=reject
Homepage HTML
40 KB, gzip
Images on homepage
44 (jpg 35, png 8, gif 1)

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

Own rulai.org?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: rulai.org. This profile covers configuration only.

Compare with other Uncategorized sites