prezi.com

Readiness by lane

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

Priority fixes for prezi.com

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   94% of Design & Content Creation peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

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

   On Next.js: The next/image component serves optimized formats automatically.

   56% of Design & Content Creation peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

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

   49% of Design & Content Creation peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Next.js: Add it in next.config.js headers().

   48% of Design & Content Creation peers do this.

   Guide: A Practical Website Health Check for Owners

What prezi.com already does well

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

• Referrer-Policy setReferrer-Policy present.26% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.37% of peers
• X-Content-Type-Options: nosniffnosniff header present.39% of peers

What we saw

Homepage checked

https://prezi.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-02-23

Platform or framework

Next.js

DNS operators

Amazon Route 53

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

474 KB, gzip

Images on homepage

43 (png 37, svg 6)

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

• digen.ai64
• font.download64
• m4editor.com64
• ronytica.com64
• vizard.ai64

Design & Content Creation readiness benchmark