# Server rendering benchmarks: Fluid Compute and Cloudflare Workers By Steven Van · 2025-10-09 Independent benchmarks found Vercel's Fluid compute up to 5x faster than Cloudflare Workers on compute-bound rendering tasks. Independent developer Theo Browne ran benchmarks comparing server-side rendering performance on [Vercel]()'s Fluid compute against Cloudflare Workers, testing 100 iterations across Next.js, React, SvelteKit and other frameworks. Cloudflare ran its standard configuration (shared CPU, 128MB RAM), while Fluid compute used performance functions (2 vCPU, 4GB RAM). For compute-bound tasks, Fluid compute came out 1.2 to 5 times faster than Cloudflare Workers, averaging 2.55 times faster across the tested workloads, according to the [benchmark results](). Response times were also more consistent: on Next.js, Cloudflare's times ranged across 3.171 seconds (0.800s to 3.971s) versus 1.098 seconds for Fluid compute (0.343s to 1.442s), and roughly one in five Cloudflare requests on Next.js and SvelteKit took 10+ seconds on tasks that averaged around 1.2 seconds. - Next.js: 0.534s mean for Fluid compute vs 1.895s for Cloudflare, 3.55x faster - React SSR: 0.138s vs 0.476s, 3.45x faster - SvelteKit: 0.113s vs 0.292s, 2.59x faster - Math operations: 0.702s vs 1.469s, 2.09x faster - Vanilla JS: 0.208s vs 0.220s, 1.06x faster [![]()]() ![Vercel]() Vercel The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config. [View Vercel →]() [Original source]() [Read Server rendering benchmarks: Fluid Compute and Cloudflare Workers on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-server-rendering-benchmarks-fluid-compute-and-cloudflare-workers