How to Measure and Improve Cache Hit Ratio in VergeCloud

How to Measure and Improve Your Cache Hit Ratio in the VergeCloud Panel

A higher cache hit ratio means more eligible requests are served from VergeCloud edge cache instead of being fetched repeatedly from the origin.

In the VergeCloud panel, Traffic Statistics shows how requests are handled using Saved, Missed, Bypassed, and Total values. These counters help you understand whether caching is working efficiently and where configuration changes may be required.

Review your caching solutions regularly to understand how Cache Max Age, query strings, Page Rules, and Maximum Cache Size affect cache performance.

What Counts as a Hit, a Miss, and a Bypass

Traffic Statistic groups requests into three main cache categories:

Traffic Statistics Parameter
Meaning
Saved
The request was served from VergeCloud edge cache
Missed
The request was not served directly from cache and required retrieval or validation
Bypassed
The request intentionally skipped VergeCloud caching

At the response level:

  • HIT contributes to Saved

  • MISS contributes to Missed

  • BYPASS contributes to Bypassed

Cache hit and cache miss request flow at the edge

A common sequence for a cacheable resource is:

MISS → HIT → HIT

The first request retrieves the resource. Once the object is cached, later eligible requests can be served from the edge.

A BYPASS is different from a MISS. A MISS represents a request where a usable cached copy was not available. BYPASS means caching was intentionally skipped because of the applicable configuration.

You can check the response cache state using:

curl -sS -D - -o /dev/null "https://example.com/images/example.jpg" \
| grep -i "^x-cache-status:"

Eligible cached content is served through VergeCloud's global edge network.

Where to Read Cache Performance in the VergeCloud Panel

Use Traffic Statistic to review cache behaviour for the selected domain.

  1. Sign in to the VergeCloud dashboard.

  2. Select the required domain.

  3. From the domain menu, open Traffic Statistic.

  4. Select the required time range.

  5. Review Request Summary and Traffic Summary.

Request Summary shows:

  • Saved

  • Missed

  • Bypassed

  • Total

Traffic Summary shows the corresponding traffic volume for the same categories.

Together, these views help you understand both how requests are being handled and how much traffic falls under each cache category.

Cache hit ratio chart in the VergeCloud panel

Available time ranges include:

  • 3 hours

  • 6 hours

  • 12 hours

  • 24 hours

  • 7 days

  • 30 days

  • Custom Date Range

Request hit ratio compared with byte hit ratio

Traffic Statistic provides raw request counts and traffic volumes rather than separate calculated percentage metrics.

For request-level analysis, calculate:

Cache Hit Ratio = Saved ÷ (Saved + Missed) × 100

For example:

  • Saved: 9

  • Missed: 1

The request hit ratio is:

9 ÷ (9 + 1) × 100 = 90%

Bypassed requests are excluded because they intentionally do not participate in normal caching.

Traffic Summary can be used to calculate a similar traffic-volume view:

Saved Traffic ÷ (Saved Traffic + Missed Traffic) × 100

This helps show how much eligible traffic volume is being served from cache.

The VergeCloud panel does not display this as a separate metric labelled Byte Hit Ratio. It provides the Saved, Missed, and Bypassed traffic values that can be used for the calculation.

Choosing a useful time range

Use shorter ranges such as 3 hours when reviewing a recent configuration change.

Use 24 hours, 7 days, or 30 days when looking for broader production patterns.

Calculating Cache Hit Ratio Yourself

The formula and a worked example

Use:

Saved ÷ (Saved + Missed) × 100

For example:

  • Saved: 800

  • Missed: 200

  • Bypassed: 100

The cache hit ratio is:

800 ÷ (800 + 200) × 100 = 80%

The 100 Bypassed requests are not included because they were intentionally excluded from caching.

What a healthy ratio looks like by site type

There is no single cache hit ratio that applies to every website.

Static assets such as CSS, JavaScript, and images are generally stronger cache candidates than personalized HTML, login pages, checkout flows, or authenticated APIs.

A lower domain-wide ratio does not automatically mean the cache configuration is wrong. A large amount of dynamic or deliberately bypassed traffic can naturally reduce the overall percentage.

If repeated misses are contributing to slow website performance, review the affected paths and content types before changing the complete cache policy.

The Most Common Causes of a Low Hit Ratio

Cache Max Age values set too low

Cache Max Age controls how long eligible content can remain cached before it requires further handling.

Very short values can increase the frequency with which requests are not served directly as cache HITs.
Cache Max Age setting in the VergeCloud caching page

For content that changes infrequently, a longer Cache Max Age can allow more requests to reuse the cached object.

For frequently changing content, the value should remain appropriate to the freshness requirement.

Query string fragmentation

When query strings are included in the cache key, different parameter values can create separate cache entries.

For example:

style.css?v=1

and:

style.css?v=2

can be treated as separate variants when query strings are included.

Unnecessary or frequently changing parameters can therefore reduce cache reuse.

Responses containing Set-Cookie require careful cache handling because they may contain visitor-specific state.

Only cache cookie-bearing responses when the content is safe to serve as shared cached content.

Cache Level set to Off on high-traffic paths

When Cache Level is Off, matching requests bypass VergeCloud caching.

If this is applied to a high-traffic path, the Bypassed count can increase significantly.

Bypass Page Rules written too broadly

A broad Page Rule can unintentionally exclude more URLs from cache than intended.

Review the URL pattern and rule priority when a large number of requests unexpectedly appear as BYPASS.

Frequent full purges

A full purge removes cached objects that could otherwise continue serving HITs.

After a purge, eligible resources need to be fetched again before those objects can be served from cache.

Use selective purging when only a limited number of resources have changed.

Uncached HTML on a mostly static site

HTML is not cached by default.

Public, non-personalized HTML can be cached using a Page Rule when appropriate.

Sensitive paths such as login, checkout, account, and personalized pages should remain excluded where required.

Raising the Ratio Step by Step in the VergeCloud Panel

Tuning Cache Max Age per file type

Use longer Cache Max Age values for resources that change infrequently, such as versioned CSS, JavaScript, images, and other static files.

Use shorter values where content freshness is more important.

Avoid using the same cache duration for every content type without considering how frequently each resource changes.

Normalizing the cache key

Review whether query strings genuinely change the returned content.

Where parameters do not affect the response, unnecessary cache-key variation can reduce reuse.

Where parameters produce different content, keep them inside the cache key.

Caching HTML with a Page Rule

For public, non-personalized HTML:

  1. Open Page Rules.

  2. Create a rule matching the required URL or path.

  3. Enable caching for the matched request.

  4. Set an appropriate Cache Max Age.

  5. Save and activate the rule.

  6. Purge the affected URL.

  7. Confirm that later eligible requests can return HIT.

Do not cache personalized, authenticated, transactional, or sensitive HTML unless it is safe to serve as shared content.

Raising Maximum Cache Size for large media

Maximum Cache Size affects whether larger objects are eligible to remain in cache.

For example, when a resource is approximately 142 MB and Maximum Cache Size is set to 128 MB, repeated requests can remain:

MISS → MISS → MISS

When Maximum Cache Size is raised above the object size, the same resource can become cacheable:

MISS → HIT → HIT

Hit ratio comparison before and after tuning
This setting is particularly relevant for larger media files, downloads, and video content.

Realistic Targets for Static Assets, HTML, and Video

Different types of content naturally produce different cache behaviour.
Content type
Expected cache approach
CSS and JavaScript
Strong cache candidates when versioned or infrequently changed
Images
Strong cache candidates unless frequently replaced or personalized
Static HTML
Can be cached using a Page Rule
Personalized HTML
Often bypassed or handled carefully
APIs
Depends on response behaviour and personalization
Large video and downloads
Review Maximum Cache Size and cache duration
Login, checkout, account paths
Usually bypassed

Evaluate cache performance by content type instead of relying only on one domain-wide percentage.

Learn more about the VergeCloud CDN.

Diagnosing a Sudden Drop After a Deployment

If cache performance drops after a deployment, review recent changes before modifying the complete cache policy.

Check:

  • recent Purge All actions

  • Page Rule changes

  • Cache Max Age changes

  • new query-string parameters

  • changed asset URLs or filenames

  • large objects exceeding Maximum Cache Size

  • cookie or personalization changes

  • newly introduced bypass rules

Use Request Inspector to review individual cache states and Traffic Statistic to check whether Saved, Missed, or Bypassed values changed at the same time.

A temporary increase in Missed requests can occur while eligible resources are being cached again after a deployment or purge.

A persistent increase should be traced back to the affected URLs and cache configuration.

Turning a Higher Hit Ratio Into Measurable Savings

A higher cache hit ratio means more eligible requests are handled from VergeCloud edge cache instead of repeatedly reaching the origin.

Use Request Summary to understand how frequently requests are being served from cache.

Use Traffic Summary to understand how much data falls under Saved, Missed, and Bypassed traffic.

Both views matter. A relatively small number of large media requests can account for more transferred data than a much larger number of small static requests.

Review request counts and traffic volumes together when evaluating the impact of cache tuning.

Common Questions About Cache Hit Ratio in VergeCloud

What is a good cache hit ratio for an online store using VergeCloud?

There is no single percentage that applies to every online store.

Static assets can generally achieve stronger cache reuse, while cart, checkout, login, account, and personalized requests may intentionally bypass cache.

Why did my hit ratio fall right after a site deployment?

New asset URLs, cache purges, changed query strings, or updated content can generate additional Missed requests while eligible resources are being cached again.

Does a low hit ratio always point to a configuration mistake?

No.

Dynamic, personalized, or frequently changing responses may correctly produce Missed or Bypassed requests.

Review the affected content type and expected behaviour before changing the configuration.

Do regular purges permanently lower my cache hit ratio?

No.

A purge removes cached objects, so subsequent eligible requests must retrieve them again before they can be served from cache.

How often should I review cache performance in the panel?

Review Traffic Statistic after major deployments or cache-policy changes and periodically during normal operation.

Use shorter time ranges for immediate troubleshooting and longer ranges for trend analysis.