Cloudflare Workers Performance

This covers the core performance bottlenecks you'll hit with Cloudflare Workers: CPU limits, cold starts, memory pressure, and caching. It's packed with before/after code showing what actually slows things down (unnecessary cloning, buffering entire responses, missing cache layers) and how to fix it. The profiling middleware is genuinely useful for finding hot paths, and the multi-layer caching strategy (memory, Cache API, KV) is solid. Best part is the table mapping errors to fixes, because "CPU limit exceeded" is useless without knowing whether to stream, batch, or optimize your JSON parsing. Aimed at people already hitting performance walls rather than premature optimization.

skills.sh installs: 329
GitHub stars: 248
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add secondsky/claude-skills --skill cloudflare-workers-performance --agent claude-code

Installs into .claude/skills of the current project.

Files

Cloudflare Workers Performance Optimization

Techniques for maximizing Worker performance and minimizing latency.

Quick Wins

// 1. Avoid unnecessary cloning
// ❌ Bad: Clones entire request
const body = await request.clone().json();

// ✅ Good: Parse directly when not re-using body
const body = await request.json();

// 2. Use streaming instead of buffering
// ❌ Bad: Buffers entire response
const text = await response.text();
return new Response(transform(text));

// ✅ Good: Stream transformation
return new Response(response.body.pipeThrough(new TransformStream({
  transform(chunk, controller) {
    controller.enqueue(process(chunk));
  }
})));

// 3. Cache expensive operations
const cache = caches.default;
const cached = await cache.match(request);
if (cached) return cached;