STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

boxofficemojo.com

boxofficemojo.com's public homepage, certificate and DNS checked against 31 practices and compared with 233 Data & Analytics sites.

Readiness index
52/100

Data & Analytics median 63

Ahead of
15%

of measured Data & Analytics sites

Practices observed
12/29

2 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 11:26:54 UTC from one location. How we measure

Readiness by lane

Green: boxofficemojo.com. Thin bar: Data & Analytics peer median.

Enable

50/100

Peers 78

Harden

58/100

Peers 56

Accelerate

38/100

Peers 63

Recover

100/100

Peers 8

Priority fixes for boxofficemojo.com

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.

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

  2. Priority 2 · Enable

    Meta description written

    Observed: The homepage had no meta description.

    What to do: Write a short, specific description of the page for people, not a list of keywords.

    92% of Data & Analytics peers do this.

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

    63% of Data & Analytics peers do this.

  4. Priority 4 · Accelerate

    Modern image formats in use

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

    31% of Data & Analytics peers do this.

What boxofficemojo.com already does well

Practices fewer than half of Data & Analytics peers use.

  • Nameservers spread across providersNameservers spread across more than one operator.7.8% of peers
  • HSTS kept for at least a yearHSTS with a 549-day max-age covering subdomains.34% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.38% of peers

What we saw

Homepage checked
https://www.boxofficemojo.com/
Homepage response
HTTP 200
TLS
TLSv1.3, http/1.1
Certificate
Amazon, 197-day validity, expiring 2027-04-27
DNS operators
4 self-run or other nameserver domains
HSTS
max-age 549 days, includeSubDomains, preload
DMARC policy
p=quarantine
Homepage HTML
182 KB, gzip
Images on homepage
18 (jpg 16)

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

Observed 12

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • HTML compressed
  • No render-blocking scripts in <head>
  • Canonical URL declared
  • Mobile viewport configured
  • Social preview image set
  • At most one redirect to the homepage
  • Nameservers spread across providers

Not measured 2

  • Static files cached for 30 days or more
  • robots.txt published

Own boxofficemojo.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: boxofficemojo.com. This profile covers configuration only.

Compare with other Data & Analytics sites