slidesgo.com

Readiness by lane

Green: slidesgo.com. Thin bar: Design & Content Creation peer median.

Priority fixes for slidesgo.com

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

1. 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.

   84% of Design & Content Creation 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

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 hours, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   57% of Design & Content Creation peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 30 days, below the one-year benchmark.

   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.

   37% of Design & Content Creation peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. 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.

   29% of Design & Content Creation peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What slidesgo.com already does well

Practices fewer than half of Design & Content Creation peers use.

• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.17% of peers
• Referrer-Policy setReferrer-Policy present.26% of peers
• X-Content-Type-Options: nosniffnosniff header present.39% of peers

What we saw

Homepage checked

https://slidesgo.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-07

CDN or edge

Cloudflare, Google edge

DNS operators

Cloudflare

HSTS

max-age 30 days, preload

DMARC policy

p=reject

Homepage HTML

871 KB, br

Images on homepage

148 (jpg 401, png 30, svg 18, 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

Compare with other Design & Content Creation sites

• pixai.art79
• runway.com79
• slidescarnival.com79
• template.net79
• vistaprint.ca79

Design & Content Creation readiness benchmark