# Using Your CDN for Dynamic Page Caching _Last updated: 2024-06-18_ A standard Content Delivery Network (CDN) configuration often underperforms because it caches only static files (images, stylesheets, JavaScript), leaving dynamic page generation to your origin server. Dynamic Page Caching caches entire pages on the CDN, serving 100% of content from edge servers. One documented case reduced average load time from 10 seconds to 2 seconds (an 80% improvement) after enabling Dynamic Page Caching. ## How CDNs Distribute Static Content A CDN is a network of geographically distributed servers designed to locally serve static files—files that change infrequently, such as images, style sheets, and JavaScript files. This reduces latency for remote visitors. For example, if your origin server is in California, a visitor in London accessing your site through a standard CDN would retrieve static files from a European edge server rather than California, improving load time for that visitor. However, a standard CDN implementation has a critical limitation: it does not cache dynamically generated page content. ## The WordPress and CMS Limitation WordPress and most Content Management Systems (CMS) generate pages on-the-fly rather than serving pre-built static files. When a visitor requests a page, the CMS queries the database, renders HTML, and serves the complete response from the origin server. With a standard CDN, a London visitor still waits for the origin server in California to generate and send the page HTML, even though static assets arrive from the European edge server. This negates much of the CDN's performance benefit. ## Dynamic Page Caching: Full-Page Edge Serving Dynamic Page Caching extends CDN caching to entire pages. Instead of caching only static assets, the system stores the complete rendered page on edge servers. Every visitor receives 100% of page content—HTML, assets, and all—from the nearest edge server, bypassing the origin server entirely. One documented deployment reduced a site's average load time from approximately 10 seconds to 2 seconds after enabling Dynamic Page Caching, representing an 80% improvement. ## Website Performance and Business Impact Site speed affects Google search ranking, visitor conversion rates, and social sharing. Facebook's news feed algorithm may deprioritize content from slow-loading pages, potentially reducing organic reach and engagement. ## Suitable and Unsuitable Use Cases Dynamic Page Caching introduces a trade-off: cached pages do not reflect changes to layout, content, or design until the CDN cache is cleared and the update propagates across the network. **Suitable for:** - Promotional and marketing websites - Blogs posting new content once or twice per week - Sites with static or infrequently changing content **Not recommended for:** - E-commerce platforms - Forums - Blogs posting daily - Web applications (web-apps) - Software-as-a-Service (SaaS) products - Sites requiring real-time content updates ## Getting Started with Dynamic Page Caching Implementation varies significantly based on your CMS configuration, CDN provider, and content delivery requirements. Consult the person maintaining your website to determine whether Dynamic Page Caching is appropriate for your site's content update frequency and user expectations.