How I fixed my brutal TTFB

The author of this text improved their homepage's Time to First Byte (TTFB) by concentrating on improving just one metric, reducing the p75 TTFB from 3.46s to 704ms. They achieved this by removing two separate middleware functions that fetched data from third-party APIs, and instead fetching the data at build time and generating it statically. This approach reduced the p75 TTFB greatly, but also introduced some tradeoffs, such as loading extra client-side JavaScript when the Twitch API is live. The author had to make compromises, like showing inaccurate data for a few hours per week, to achieve significant performance gains. After removing both Edge Functions and returning to a completely static build, they reduced the p75 TTFB by 80%. They still have further optimizations to make on the homepage, but are happy with the progress so far.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.