Skip to main content
sus.botdocs
  • SEO
  • AI
  • QA
  • Privacy
  • Accessibility
  • Security
  1. Docs
  2. SEO
  3. Delivery and caching
  4. No content delivery network was detected

SEO finding

No content delivery network was detected

SEO Info Severity: Low

Part of the audit Delivery and caching. Finding id: seo.noCdnDetected.

What it costs you

Every visitor is served by one location. Visitors far away wait longer for each file, and a traffic peak hits your server directly.

What to do

If you have visitors in several countries, or slow server response times, put a CDN in front of the site.

What it checks

  • No content delivery network

How to fix it

Decide whether a CDN is worth it

  1. Look at where your visitors are and at the time to first byte from those places.
  2. If the distance shows, put a CDN in front of the static files first, then the pages.
  3. If you already use a CDN, tell us which one so this finding is closed.

How to check: Run this rule again: a CDN is detected.

What this relies on

A site may have visitors far from its server. Used only until the owner has answered the question above.

  • All audits
  • About sus.bot
  • Open the app
  • Contact support