STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

gsfcarparts.com

gsfcarparts.com's public homepage, certificate and DNS checked against 31 practices and compared with 703 Cars & Automotive sites.

Readiness index
80/100

Cars & Automotive median 66

Ahead of
89%

of measured Cars & Automotive sites

Practices observed
24/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:11:39 UTC from one location. How we measure

Readiness by lane

Green: gsfcarparts.com. Thin bar: Cars & Automotive peer median.

Enable

100/100

Peers 84

Harden

83/100

Peers 57

Accelerate

60/100

Peers 65

Recover

0/100

Peers 14

Priority fixes for gsfcarparts.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.

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

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

    45% of Cars & Automotive peers do this.

  3. Priority 3 · Accelerate

    HTTP/3 advertised

    Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

    What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

    On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

    30% of Cars & Automotive peers do this.

  4. Priority 4 · Harden

    security.txt published

    Observed: No valid /.well-known/security.txt with a Contact field was returned.

    What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

    On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

    8.9% of Cars & Automotive peers do this.

What gsfcarparts.com already does well

Practices fewer than half of Cars & Automotive peers use.

  • Referrer-Policy setReferrer-Policy present.26% of peers
  • Content Security Policy presentContent-Security-Policy present.31% of peers
  • HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.41% of peers

What we saw

Homepage checked
https://www.gsfcarparts.com/
Homepage response
HTTP 200
TLS
TLSv1.3, http/1.1
Certificate
Google Trust Services, 90-day validity, expiring 2026-12-02
CDN or edge
Cloudflare
Platform or framework
Next.js
DNS operators
Cloudflare
HSTS
max-age 365 days, includeSubDomains
DMARC policy
p=quarantine
Homepage HTML
785 KB, br
Images on homepage
87 (svg 64, jpg 55, png 10, webp 3)

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 24

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTML compressed
  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own gsfcarparts.com?

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

Compare with other Cars & Automotive sites