Dev server and build process in Astro - Performance & Optimization

Performance: Dev server and build process

MEDIUM IMPACT

This concept affects the initial page load speed and developer experience by controlling how code is served and optimized before reaching the browser.

Serving Astro project code during development

Astro

astro dev

Enables HMR for instant updates to only changed modules without full reloads or rebuilds.

📈 Performance GainReduces reload time to under 100ms, improving INP and developer experience

Serving Astro project code during development

Astro

astro build && npx serve dist

Serving static production build disables HMR and live reloads, requiring full rebuilds and page reloads on changes, slowing developer feedback.

📉 Performance CostFull rebuilds block changes for 500ms+ on each change, increasing INP during development

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Dev server without HMR	N/A	N/A	Blocks rendering during reload	[X] Bad
Dev server with HMR	N/A	N/A	Instant updates, no full reload	[OK] Good
Build without minify/split	N/A	N/A	Large bundle delays paint	[X] Bad
Build with minify and split	N/A	N/A	Smaller bundle speeds paint	[OK] Good

Rendering Pipeline

The dev server serves unoptimized code with live updates, affecting interaction responsiveness. The build process optimizes code to reduce parsing, layout, and paint times in the browser.

→Network

→Parse & Compile

→Layout

→Paint

⚠️ BottleneckNetwork and Parse & Compile stages due to large unoptimized bundles

Core Web Vital Affected

LCP

This concept affects the initial page load speed and developer experience by controlling how code is served and optimized before reaching the browser.

Optimization Tips

1Use HMR and caching in dev server to speed up code updates and reduce reload delays.

2Always minify and split code in production builds to reduce bundle size and improve load speed.

3Check bundle sizes and load times in DevTools Network and Performance panels to catch slowdowns.

Performance Quiz - 3 Questions

How does enabling Hot Module Replacement (HMR) in Astro dev server affect performance?

A It disables caching causing slower reloads.

B It increases bundle size by adding extra code for updates.

C It reduces reload time by updating only changed modules without full page reload.

D It blocks rendering until the entire page reloads.

DevTools: Network and Performance panels

How to check: In Network, check bundle sizes and load times; in Performance, record page load to see parsing and scripting durations.

What to look for: Look for large JS files delaying first contentful paint and long scripting times indicating unoptimized bundles.

Practice

1. What is the main purpose of the astro dev command in Astro?

easy

A. To start a development server that shows live updates as you code

B. To create optimized production files for deployment

C. To install Astro dependencies automatically

D. To generate static HTML files without a server

Solution

1. Step 1: Understand the role of astro dev

   The astro dev command runs a local server that watches your files and reloads the browser when you make changes.

2. Step 2: Differentiate from build process

   The build process (astro build) creates optimized files for publishing, not live updates.

3. Final Answer:

   To start a development server that shows live updates as you code -> Option A

4. Quick Check:

   Dev server = live updates [OK]

Hint: Dev server shows live changes, build prepares files [OK]

Common Mistakes:

• Confusing dev server with build output
• Thinking astro dev creates production files
• Assuming astro dev installs packages

2. Which of the following is the correct command to build your Astro project for production?

easy

A. astro run

B. astro start

C. astro build

D. astro serve

Solution

1. Step 1: Recall Astro build command

   The command astro build is used to create optimized production files for deployment.

2. Step 2: Verify other commands

   astro start, astro run, and astro serve are not valid build commands in Astro.

3. Final Answer:

   astro build -> Option C

4. Quick Check:

   Build command = astro build [OK]

Hint: Build = astro build, dev = astro dev [OK]

Common Mistakes:

• Using astro start instead of astro build
• Confusing astro serve with build command
• Trying astro run which doesn't exist

3. Given the following commands run in order:

astro dev
astro build
astro dev

What will happen when you run the last astro dev command?

medium

A. It will overwrite the build files with development files

B. It will start the dev server showing live updates again

C. It will throw an error because build was already done

D. It will serve the optimized build files instead of dev server

Solution

1. Step 1: Understand astro dev behavior

   Each time you run astro dev, it starts a fresh development server with live reload, independent of previous builds.

2. Step 2: Recognize build does not block dev

   Running astro build creates production files but does not prevent running astro dev again later.

3. Final Answer:

   It will start the dev server showing live updates again -> Option B

4. Quick Check:

   Dev server always starts fresh on astro dev [OK]

Hint: Dev server can run anytime, build doesn't block it [OK]

Common Mistakes:

• Thinking build locks out dev server
• Assuming dev overwrites build files
• Expecting errors after build when running dev

4. You run astro build but the output folder is empty. What is the most likely cause?

medium

A. You forgot to run astro dev first

B. The build command only works after publishing

C. Your project folder is missing the package.json file

D. There is a syntax error in your Astro files stopping the build

Solution

1. Step 1: Check build requirements

   astro build requires valid Astro files; syntax errors prevent successful build output.

2. Step 2: Eliminate other causes

   astro dev is not required before build; build works locally before publishing; missing package.json usually causes install errors, not empty build.

3. Final Answer:

   There is a syntax error in your Astro files stopping the build -> Option D

4. Quick Check:

   Syntax errors block build output [OK]

Hint: Check syntax errors if build folder is empty [OK]

Common Mistakes:

• Thinking dev must run before build
• Assuming build only works after publishing
• Ignoring syntax errors in source files

5. You want to deploy your Astro site but notice the build output is very large and slow to load. Which combination of steps will best optimize your build process?

hard

A. Run astro build with image optimization enabled and remove unused CSS

B. Only run astro dev and deploy the dev server files

C. Skip astro build and upload source files directly

D. Run astro build without any configuration changes

Solution

1. Step 1: Identify optimization techniques

   Enabling image optimization and removing unused CSS during build reduces file size and improves load speed.

2. Step 2: Understand deployment best practices

   Deploying dev server files or source files directly is inefficient and not recommended; default build may not optimize assets fully.

3. Final Answer:

   Run astro build with image optimization enabled and remove unused CSS -> Option A

4. Quick Check:

   Optimize images + CSS during build = faster site [OK]

Hint: Optimize images and CSS during build for faster sites [OK]

Common Mistakes:

• Deploying dev server files instead of build output
• Skipping build and uploading source files
• Not enabling optimizations in build config