Website readiness profile · Snapshot 23 October 2026
greasyfork.org
greasyfork.org's public homepage, certificate and DNS checked against 31 practices and compared with 231 Programming & Software sites.
- Readiness index
- 80/100
- Ahead of
- 86%
- Practices observed
- 22/30
- Popularity band
- Top 50K
Programming & Software median 68
of measured Programming & Software sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: greasyfork.org. Thin bar: Programming & Software peer median.
Enable
62/100
Peers 81
Harden
82/100
Peers 59
Accelerate
100/100
Peers 65
Recover
0/100
Peers 7
Priority fixes for greasyfork.org
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
69% of Programming & Software peers do this. Limit: Only the standard location was requested, once, at the time of the check.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
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 Programming & Software peers do this.
Guide: Meta Titles and Descriptions That Match Search Intent
Priority 3 · Enable
Social preview image set
Observed: The homepage had no og:image, so shared links may show without a preview image.
What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.
60% of Programming & Software peers do this.
Priority 4 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
32% of Programming & Software peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
What greasyfork.org already does well
Practices fewer than half of Programming & Software peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.12% of peers
- Referrer-Policy setReferrer-Policy present.24% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age.40% of peers
What we saw
- Homepage checked
- https://greasyfork.org/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-09
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- HSTS
- max-age 365 days
- DMARC policy
- p=reject
- Homepage HTML
- 28 KB, br
- Images on homepage
- 3 (webp 2, 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
Not observed 8
Observed 22
- 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
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- No render-blocking scripts in <head>
- robots.txt published
- Reachable over IPv6
- Canonical URL declared
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 1
- Offscreen images lazy-loaded
Own greasyfork.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: greasyfork.org. This profile covers configuration only.