Cacheability Assessment
Two weeks of our engineers on your traffic and your pages. You get the number your site would actually reach, and the plan to get there — before you commit to a subscription or an implementation.
fewer origin renders on our own benchmark — a replay of 100,000 production requests. Over that site’s full log the hit ratio was about 66.7%. The Assessment measures yours. How it was measured
Tell us about the site. We reply within one business day to schedule a scoping call.
What You Get
Measured on your traffic, not a generic benchmark — with the arithmetic shown, so your finance team can check it.
Your recorded traffic replayed against a FrontCache node in front of your app. The hit ratio you would actually reach, the share of renders that leave your origin, and the app-tier capacity that frees.
Which pages to split, where the fragment boundaries go, which TTL and which invalidation tags each fragment gets — including a separate lifetime for crawlers where that pays.
The origin compute you would no longer run, priced at your rates, next to what FrontCache would cost. If the saving does not cover it, the report says so.
How It Runs
Why Measure First
A 6× throughput gain means roughly one sixth of the app tier — and the database, search tier and third-party API calls behind it see the same cut. But the multiplier depends on your pages, your TTLs and your traffic. Our own benchmark shows 98.7% on a hot working set and about 66.7% over the full log of the same site.
You can measure it yourself: the engine is free, and the Docker quickstart takes five minutes. The Assessment is for when you want the number on your own traffic, a plan to reach it, and someone accountable for both.
Details
You keep the report either way — your hit ratio, your fragment plan, and your projected saving. If you do subscribe, the full $9,500 is credited against your first year.
A sample of recent traffic (an access log is the usual starting point), a staging environment we can put a FrontCache node in front of, and a few hours from someone who knows how the pages are built.
Only what you choose to send us, and it is used for the Assessment alone. If logs cannot leave, we run the replay inside your environment instead.
No. In front of your app, FrontCache is a reverse proxy, and anything that can set a response header can tell it what to cache. In-process mode is the Java-only option.
Yes — send us an access log for a free first look: what share of your traffic is crawlers, which URLs dominate, and a first estimate of what is cacheable.
Walkthrough
Next Step
Book the Assessment, or send an access log for the free first look. We respond within one business day.