Start your 7 Day free TrialNo credit card required
Drupal

Integration Guide

Drupal

Connect Drupal to fast.site while keeping your hosting. Review DNS, HTTPS, public caching and private routes, then validate content updates and user journeys.

Setup Steps

  1. 1

    Add your domain in fast.site

    Log in to your fast.site dashboard and add your Drupal domain.

  2. 2

    Confirm your platform

    Review the detected platform and its cache settings. Confirm the selection and test your own routes; defaults do not replace integration checks.

  3. 3

    Update your nameservers

    Switch your domain's nameservers to the ones listed in your fast.site dashboard. Your existing DNS records get imported automatically.

  4. 4

    Clear Drupal cache

    Run drush cr or clear caches from Configuration → Performance.

  5. Done!

    Check public and private journeys, content updates and cache purges. Compare performance under matching conditions and keep monitoring after launch.

Verify cache behavior

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.

  • Exclude private, account and checkout responses
  • Check public pages for the expected HIT/MISS behavior
  • Test cookies, permissions and language variants
  • Verify forms, content updates and cache purges

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

  • TTFB: 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.
  • LCP: Measure the largest visible content and transferred image bytes. Image format, dimensions, quality and frontend loading all affect the result.
  • Review responsiveness and layout stability alongside LCP in real-user data when available. TTFB and FCP help diagnosis but are not Core Web Vitals.

Tip for multilingual sites

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.

Back to Support