Drupal · CDN
Make your Drupal site faster
Pages and images load faster for your visitors. Keep your hosting and your Drupal setup.
7 days free · No credit card required
Where fast.site fits into Drupal
Deliver reusable content from the edge
Anonymous content pages, articles and public listings can benefit from an edge cache in front of Drupal. Drupal’s internal caching still matters; expensive Views queries and frontend code also need their own performance review.
Keep personal content personal
Permissions, language and user state affect what can be reused. Review cache contexts and max-age, and exclude private responses. Drupal cache tags require a working invalidation integration; do not assume they reach the CDN automatically.
Check the whole journey, not just the homepage
Compare anonymous and authenticated views, language variants, forms and editorial previews. Update an article and check related listings at the edge. Confirm the purge behavior with your Drupal modules and reverse-proxy configuration.
Drupal caching documentationMeasure your site. Not a generic promise.
Record a baseline, then repeat the same pages, device, location and network after activation. Separate cold-cache and warm-cache results. A lab score is a snapshot, not a forecast of rankings or revenue.
Check the response
Compare Time to First Byte and cache HIT/MISS behavior. A faster cached response does not describe checkout, logged-in pages or every request to your origin.
Check what visitors see
Measure the largest visible content and transferred image bytes. Image format, dimensions, quality and frontend loading all affect the result.
Check the real experience
Review responsiveness and layout stability alongside LCP in real-user data when available. TTFB and FCP help diagnosis but are not Core Web Vitals.
A considered setup, from DNS to your first comparison
Prepare your domain
Review existing DNS records, including email and subdomains. Check origin access and choose cache rules that fit your application before changing nameservers.
Verify DNS and HTTPS
Use the nameservers assigned in your dashboard. Wait for propagation and certificate readiness, then confirm that traffic reaches the edge. Timing depends on DNS and your origin.
Test and measure
Check public and private journeys, content updates and cache purges. Compare performance under matching conditions and keep monitoring after launch.
Protection starts after DNS, SSL and domain activation are ready. Setup time does not count towards your 7 days.
Plan your next step
Explore the setup, check the plan limits and ask us about anything specific to your website.
See what edge delivery can do for Drupal.
Keep your hosting. Connect your domain, validate your setup and compare the results on your own website.