Serving static files in Deno - Performance & Optimization

Performance: Serving static files

MEDIUM IMPACT

Serving static files impacts the page load speed by affecting how quickly resources like images, CSS, and JavaScript are delivered to the browser.

Delivering static assets like images and stylesheets to users

Deno

import { serveFile } from "https://deno.land/std/http/file_server.ts";
import { serve } from "https://deno.land/std/http/server.ts";

serve(async (req) => {
  const url = new URL(req.url);
  if (url.pathname.startsWith('/static/')) {
    try {
      return await serveFile(req, `./public${url.pathname.replace('/static', '')}`);
    } catch {
      return new Response('Not Found', { status: 404 });
    }
  }
  return new Response('Hello World');
});

Uses built-in serveFile which handles caching headers, content-type detection, and efficient streaming to reduce CPU and latency.

📈 Performance GainReduces CPU load, supports browser caching, and streams files efficiently, improving LCP.

Delivering static assets like images and stylesheets to users

Deno

import { serve } from "https://deno.land/std/http/server.ts";

serve(async (req) => {
  const url = new URL(req.url);
  if (url.pathname.startsWith('/static/')) {
    const filePath = `./public${url.pathname.replace('/static', '')}`;
    try {
      const file = await Deno.readFile(filePath);
      return new Response(file, { headers: { 'content-type': 'application/octet-stream' } });
    } catch {
      return new Response('Not Found', { status: 404 });
    }
  }
  return new Response('Hello World');
});

Reads files from disk on every request without caching or proper content-type headers, causing slow response and high CPU usage.

📉 Performance CostBlocks event loop per request, adds latency, increases CPU usage, and triggers multiple disk reads.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Reading files on every request without caching	N/A	N/A	High due to delayed resource load	[X] Bad
Using serveFile with caching and streaming	N/A	N/A	Low due to fast resource delivery	[OK] Good

Rendering Pipeline

Serving static files efficiently reduces the time the browser waits for resources, speeding up the critical rendering path by delivering assets faster.

→Network

→Resource Loading

→Rendering

⚠️ BottleneckNetwork latency and server file I/O

Core Web Vital Affected

LCP

Serving static files impacts the page load speed by affecting how quickly resources like images, CSS, and JavaScript are delivered to the browser.

Optimization Tips

1Use built-in file serving utilities that handle caching and streaming.

2Avoid reading files from disk on every request synchronously.

3Check caching headers and response times in browser DevTools Network tab.

Performance Quiz - 3 Questions

What is a key benefit of using Deno's serveFile for static files?

A It disables browser caching for fresh content every time.

B It automatically sets caching headers and streams files efficiently.

C It reads files synchronously blocking the event loop.

D It compresses files on the fly without configuration.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and inspect static file requests for status, size, and caching headers.

What to look for: Look for 200 status with cache-control headers and fast response times indicating efficient static file serving.

Practice

1. What is the main purpose of serving static files in a Deno web server?

easy

A. To send images, styles, and scripts to the user's browser

B. To execute server-side scripts dynamically

C. To connect to a database and fetch data

D. To compile TypeScript files on the server

Solution

1. Step 1: Understand what static files are

   Static files include images, CSS stylesheets, and JavaScript files that do not change dynamically.

2. Step 2: Identify the purpose of serving static files

   Serving static files means sending these files from the server to the user's browser so the webpage looks and works correctly.

3. Final Answer:

   To send images, styles, and scripts to the user's browser -> Option A

4. Quick Check:

   Static files = images, styles, scripts [OK]

Hint: Static files are fixed resources sent to browsers [OK]

Common Mistakes:

• Confusing static files with dynamic server code
• Thinking static files run on the server
• Mixing static files with database operations

2. Which of the following is the correct way to import the function to serve static files in Deno?

easy

A. import { serveFile } from "https://deno.land/std/fs/mod.ts";

B. import { serveFile } from "https://deno.land/std/http/server.ts";

C. import { serveFile } from "https://deno.land/std/http/file.ts";

D. import { serveFile } from "https://deno.land/std/http/file_server.ts";

Solution

1. Step 1: Identify the correct module for serving static files

   The function serveFile is provided by the file.ts module in Deno's standard HTTP library.

2. Step 2: Match the import path

   The correct import path is "https://deno.land/std/http/file.ts" for serveFile.

3. Final Answer:

   import { serveFile } from "https://deno.land/std/http/file.ts"; -> Option C

4. Quick Check:

   serveFile import = file.ts [OK]

Hint: serveFile comes from file.ts in std/http [OK]

Common Mistakes:

• Using server.ts instead of file.ts
• Importing from fs module incorrectly
• Wrong URL path for the import

3. Given this Deno server code snippet, what will be the response when a user requests /image.png?

import { serve } from "https://deno.land/std/http/server.ts";
import { serveFile } from "https://deno.land/std/http/file_server.ts";

serve(async (req) => {
  const url = new URL(req.url);
  if (url.pathname === "/image.png") {
    return await serveFile(req, "./static/image.png");
  }
  return new Response("Not Found", { status: 404 });
});

medium

A. The server throws a runtime error because serveFile is used incorrectly

B. The server sends the file located at ./static/image.png to the user

C. The server returns a 404 Not Found response

D. The server sends an empty response with status 200

Solution

1. Step 1: Check the URL path condition

   The code checks if the requested path is exactly "/image.png".

2. Step 2: Understand serveFile usage

   If the path matches, serveFile sends the file "./static/image.png" as the response.

3. Final Answer:

   The server sends the file located at ./static/image.png to the user -> Option B

4. Quick Check:

   Path matches "/image.png" so serveFile sends file [OK]

Hint: Check URL path then serveFile sends matching file [OK]

Common Mistakes:

• Assuming 404 is returned for existing path
• Thinking serveFile causes error here
• Ignoring the URL pathname check

4. Identify the error in this Deno code snippet for serving a static CSS file:

import { serve } from "https://deno.land/std/http/server.ts";
import { serveFile } from "https://deno.land/std/http/file_server.ts";

serve(async (req) => {
  const url = new URL(req.url);
  if (url.pathname = "/style.css") {
    return await serveFile(req, "./static/style.css");
  }
  return new Response("Not Found", { status: 404 });
});

medium

A. The server function is not awaited

B. serveFile is missing an await keyword

C. The import path for serveFile is incorrect

D. The assignment operator (=) is used instead of comparison (===) in the if condition

Solution

1. Step 1: Check the if condition syntax

   The condition uses a single equals sign (=), which assigns instead of compares.

2. Step 2: Understand the impact of assignment in if

   Using = in if always evaluates to true, causing incorrect logic and possible bugs.

3. Final Answer:

   The assignment operator (=) is used instead of comparison (===) in the if condition -> Option D

4. Quick Check:

   Use === for comparison, not = [OK]

Hint: Use === for comparison, not = assignment in conditions [OK]

Common Mistakes:

• Confusing = with === in if statements
• Forgetting to await serveFile (though it is awaited here)
• Incorrect import paths

5. You want to serve multiple static files (HTML, CSS, JS) from a folder named public in Deno. Which approach correctly serves any requested file from that folder, falling back to a 404 if the file doesn't exist?

import { serve } from "https://deno.land/std/http/server.ts";
import { serveFile } from "https://deno.land/std/http/file_server.ts";

serve(async (req) => {
  const url = new URL(req.url);
  try {
    // Which line correctly serves the file?
    return await ???;
  } catch {
    return new Response("Not Found", { status: 404 });
  }
});

hard

A. serveFile(req, `./public${url.pathname}`)

B. serveFile(req, `./public/index.html`)

C. serveFile(req, `./public/style.css`)

D. serveFile(req, `./public/${url.searchParams.get('file')}`)

Solution

1. Step 1: Understand dynamic file serving

   To serve any file requested, the server must use the URL path to build the file path inside the public folder.

2. Step 2: Match the URL pathname to the file path

   Using `./public${url.pathname}` correctly maps the request path to the file location.

3. Final Answer:

   serveFile(req, `./public${url.pathname}`) -> Option A

4. Quick Check:

   Dynamic path = ./public + url.pathname [OK]

Hint: Use url.pathname appended to folder path for dynamic files [OK]

Common Mistakes:

• Serving only a fixed file like index.html
• Using query parameters instead of pathname
• Hardcoding a single file path