STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

mocospace.com

mocospace.com's public homepage, certificate and DNS checked against 31 practices and compared with 193 Social Media & Networking sites.

Readiness index
40/100

Social Media & Networking median 63

Ahead of
3.6%

of measured Social Media & Networking sites

Practices observed
12/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:18:34 UTC from one location. How we measure

Readiness by lane

Green: mocospace.com. Thin bar: Social Media & Networking peer median.

Enable

54/100

Peers 76

Harden

40/100

Peers 56

Accelerate

28/100

Peers 62

Recover

0/100

Peers 5

Priority fixes for mocospace.com

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://www.mocospace.com/ 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.

    93% of Social Media & Networking peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

  2. Priority 2 · Accelerate

    HTML compressed

    Observed: The homepage HTML (8 KB) was delivered without gzip, Brotli or zstd compression.

    What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

    94% of Social Media & Networking peers do this.

  3. Priority 3 · Enable

    Mobile viewport configured

    Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

    What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

    92% of Social Media & Networking peers do this.

  4. Priority 4 · Accelerate

    HTTP/2 negotiated

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

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

    88% of Social Media & Networking peers do this.

What mocospace.com already does well

Practices fewer than half of Social Media & Networking peers use.

  • Content Security Policy presentContent-Security-Policy present.28% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers
  • X-Content-Type-Options: nosniffnosniff header present.42% of peers

What we saw

Homepage checked
https://www.mocospace.com/
Homepage response
HTTP 200
TLS
TLSv1.2
Certificate
GoDaddy, 198-day validity, expiring 2027-01-30
DNS operators
1 self-run or other nameserver domain
DMARC policy
p=quarantine
Homepage HTML
8 KB, uncompressed
Images on homepage
10 (gif 9, png 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

Observed 12

  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Static files cached for 30 days or more
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • At most one redirect to the homepage

Own mocospace.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: mocospace.com. This profile covers configuration only.

Compare with other Social Media & Networking sites