Cutting origin bandwidth by two-thirds with caching at the edge.

The work at a glance

The account was approaching a move to a larger WP Engine tier, needed as the business added sites, at a significant cost increase. On shared infrastructure, one site's resource draw affects its neighbors, so the work applied noisy neighbor best practices and reduced how much traffic reached the origin at all.

• Implemented server-side caching with Cloudflare in front of the WP Engine origin.
• Repeat page views and asset requests are served from cache instead of the origin.
• Average daily bandwidth fell from 8 GB to 2.5 GB (-69%).
• Roughly 165 GB of origin traffic is removed every month.
• The bandwidth case for the larger, more expensive hosting tier no longer applies.
• Bandwidth and cache performance monitoring continues, with further tuning as usage changes.

Want to explore a similar project?

Tell me about the workflow or website you want to improve. Discuss your project →