Cloudflare Workers performance optimization with CPU, memory, caching, bundle size. Use for slow workers, high latency, cold starts, or encountering CPU limits, memory issues, timeout errors.
87
88%
Does it follow best practices?
Impact
75%
1.31xAverage score across 3 eval scenarios
Passed
No known issues
Multi-layer caching with Cache API
Cache API usage
100%
90%
Non-blocking cache write
100%
50%
Cache key normalization
62%
100%
Tracking param removal
100%
100%
In-memory layer
0%
100%
Multi-layer ordering
37%
100%
s-maxage header
0%
0%
stale-while-revalidate
0%
0%
stale-if-error
57%
100%
Cache clone for storage
100%
50%
KV as fallback layer
100%
100%
No request.clone() misuse
100%
100%
Streaming and CPU-efficient data processing
No response buffering
0%
100%
Streaming JSON parser
0%
0%
No clone() misuse
100%
100%
D1 batch pagination
30%
0%
Parallel batch processing
0%
33%
Filter before transform
71%
100%
Server-Timing header
0%
100%
performance.now() timing
0%
100%
TransformStream usage
0%
0%
Batch KV/D1 ops
60%
100%
Array join over concat
100%
100%
Bundle optimization and cold start reduction
No wildcard lodash import
100%
100%
Lightweight date library
100%
100%
Native UUID generation
100%
100%
Native fetch over axios
100%
100%
Named exports
100%
100%
sideEffects false
0%
0%
esbuild minify
100%
100%
esbuild treeShaking
100%
100%
Drop console in build
0%
100%
Dynamic imports for heavy routes
100%
100%
Lazy initialization
100%
100%
Lazy singleton for connections
75%
100%
ctx.waitUntil for background work
100%
100%
90d6bd7
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.