botpower.ca

Readiness by lane

Green: botpower.ca. Thin bar: Data & Analytics peer median.

Priority fixes for botpower.ca

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

1. Priority 1 · Harden

   HSTS kept for at least a year

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

   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.

   34% of Data & Analytics 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: No DMARC record was found at _dmarc.botpower.ca.

   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.

   38% of Data & Analytics peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   54% of Data & Analytics peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   65% of Data & Analytics peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What botpower.ca already does well

Practices fewer than half of Data & Analytics peers use.

• Structured data presentJSON-LD structured data found.43% of peers
• Reachable over IPv6IPv6 address published.49% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.49% of peers

What we saw

Homepage checked

https://botpower.ca/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-09

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Cloudflare

Homepage HTML

91 KB, br

Images on homepage

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 Data & Analytics sites

• asiakastieto.fi62
• bullions.co.in62
• canlidoviz.com62
• statcounter.com63
• wolframalpha.com63

Data & Analytics readiness benchmark