Deploying to Cloudflare Pages in Astro - Performance & Optimization

Performance: Deploying to Cloudflare Pages

MEDIUM IMPACT

This affects the page load speed by optimizing how quickly the site files are delivered from the edge network to the user.

Deploying a static site for fast global delivery

Astro

Deploy site on Cloudflare Pages which uses Cloudflare's global edge network.

Content is cached and served from locations near users, reducing latency.

📈 Performance GainReduces LCP significantly by cutting network travel time.

Deploying a static site for fast global delivery

Astro

Deploy site on a single distant server without CDN integration.

Users far from the server experience slow loading due to long network travel times.

📉 Performance CostIncreases LCP by hundreds of milliseconds for distant users.

Performance Comparison

Pattern	Network Latency	Cache Efficiency	Load Time Impact	Verdict
Single origin server deployment	High for distant users	Low	Slower LCP	[X] Bad
Cloudflare Pages edge deployment	Low due to edge caching	High	Faster LCP	[OK] Good

Rendering Pipeline

Cloudflare Pages serves static assets from edge servers, reducing time to first byte and speeding up resource delivery.

→Network

→Resource Loading

→First Paint

⚠️ BottleneckNetwork latency when fetching resources from origin server.

Core Web Vital Affected

LCP

This affects the page load speed by optimizing how quickly the site files are delivered from the edge network to the user.

Optimization Tips

1Deploy static sites to Cloudflare Pages to leverage global edge caching.

2Edge caching reduces network latency and improves LCP.

3Check resource timing in DevTools Network tab to verify edge delivery.

Performance Quiz - 3 Questions

How does deploying to Cloudflare Pages improve page load speed?

A By serving content from servers close to users

B By increasing the size of JavaScript bundles

C By delaying resource loading until user interaction

D By removing all images from the site

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the 'Timing' section for each resource to see time to first byte and total load time.

What to look for: Look for low 'Waiting (TTFB)' times and fast resource load times indicating edge caching.

Practice

1. What is the first step to deploy an Astro site to Cloudflare Pages?

easy

A. Push your Astro project code to a GitHub repository

B. Write a custom server script for Cloudflare

C. Install Cloudflare Pages CLI locally

D. Create a Docker container for the site

Solution

1. Step 1: Prepare your Astro project

   You need to have your Astro site code ready and pushed to a GitHub repository because Cloudflare Pages connects to GitHub to get your code.

2. Step 2: Connect GitHub repo to Cloudflare Pages

   Cloudflare Pages uses your GitHub repository to build and deploy your site automatically.

3. Final Answer:

   Push your Astro project code to a GitHub repository -> Option A

4. Quick Check:

   First step is pushing code to GitHub [OK]

Hint: Remember: Cloudflare Pages pulls from GitHub first [OK]

Common Mistakes:

• Trying to deploy without a GitHub repo
• Assuming local CLI is mandatory
• Thinking Docker is required

2. Which build command is typically used in Cloudflare Pages settings for an Astro project?

easy

A. astro dev

B. npm run start

C. npm run build

D. npm install

Solution

1. Step 1: Understand Astro build process

   Astro projects use npm run build to create the static files for deployment.

2. Step 2: Set build command in Cloudflare Pages

   Cloudflare Pages needs the build command to generate the site files; npm run build is the correct command.

3. Final Answer:

   npm run build -> Option C

4. Quick Check:

   Build command = npm run build [OK]

Hint: Build command for Astro is always npm run build [OK]

Common Mistakes:

• Using npm run start which runs a dev server
• Using astro dev which is for local development
• Confusing install with build

3. Given this Cloudflare Pages config snippet:

build:
  command: "npm run build"
  directory: "dist"

What will Cloudflare Pages do after you push your Astro site code?

medium

A. Run npm install and deploy files from node_modules

B. Run npm run build and deploy files from the dist folder

C. Ignore build and deploy all files in the repo

D. Run npm start and deploy files from the root folder

Solution

1. Step 1: Read the build command

   The config says to run npm run build, which builds the Astro site into static files.

2. Step 2: Check the output directory

   The directory dist is where Astro puts the built site files, so Cloudflare Pages deploys from there.

3. Final Answer:

   Run npm run build and deploy files from the dist folder -> Option B

4. Quick Check:

   Build command + output folder = deploy [OK]

Hint: Build command runs, output folder is deployed [OK]

Common Mistakes:

• Confusing npm start with build
• Deploying from wrong folder
• Thinking node_modules is deployed

4. You connected your GitHub repo to Cloudflare Pages but the deployment fails with "Build command not found" error. What is the likely cause?

medium

A. You pushed code to the wrong GitHub branch

B. You used the wrong Cloudflare account

C. You did not enable GitHub Actions

D. You forgot to add a build script in package.json

Solution

1. Step 1: Understand the error message

   "Build command not found" means Cloudflare tried to run the build command but it does not exist in your project.

2. Step 2: Check package.json scripts

   The build command must be defined in the scripts section of package.json, usually as "build": "astro build" or similar.

3. Final Answer:

   You forgot to add a build script in package.json -> Option D

4. Quick Check:

   Missing build script causes build command error [OK]

Hint: Check package.json scripts for build command [OK]

Common Mistakes:

• Assuming branch or account causes build command error
• Thinking GitHub Actions must be enabled manually
• Ignoring package.json scripts

5. You want to deploy an Astro site with environment variables on Cloudflare Pages. Which step is necessary to ensure your variables are available during build?

hard

A. Add environment variables in Cloudflare Pages dashboard under Settings > Environment Variables

B. Include variables in a .env file and push it to GitHub

C. Hardcode variables directly in your Astro source code

D. Set variables only in your local machine before pushing

Solution

1. Step 1: Understand environment variable usage in Cloudflare Pages

   Cloudflare Pages requires environment variables to be set in its dashboard to inject them during build securely.

2. Step 2: Avoid pushing .env files with secrets

   For security, do not push .env files with secrets to GitHub; instead, configure variables in Cloudflare Pages settings.

3. Final Answer:

   Add environment variables in Cloudflare Pages dashboard under Settings > Environment Variables -> Option A

4. Quick Check:

   Set env vars in Cloudflare dashboard for build [OK]

Hint: Set env vars in Cloudflare dashboard, not in repo [OK]

Common Mistakes:

• Pushing .env files with secrets publicly
• Hardcoding sensitive info in code
• Assuming local env vars affect cloud build