---
title: "Caching in Transaction Tests"
slug: "caching-in-transaction-tests"
updated: 2025-06-11T14:34:07Z
published: 2025-06-11T14:34:07Z
canonical: "docs.catchpoint.com/caching-in-transaction-tests"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Caching in Transaction Tests

When running transaction tests on sites where most users are return visitors, it may be necessary to measure the performance when the page is ***cached*** vs ***not cached***.

For a multi-step transaction, the agent stores items in its cache from step to step. In cases where you simply want to compare **cached** vs **not cached** performance for a given URL, you can write a transaction script that has two steps, both of which go to the same page. The second step will be handled from the cache, and will show an HTTP code of "200 (Cached)". Note that cached requests do not impact our billing and account activity; they are ignored.

For example:

```
//step 1
open(http://www.example.com)
//step 2
open(http://www.example.com)
```

---

**Note:** Transaction tests do not cache test data or results across test runs. You will see caching only within a single test run.

If a step/request is cached, zones will not be applied to that element of the waterfall and data categorization under that zone will be impacted with caching.