InstantOn Caching
Yottaa uses caching to speed up site performance. InstantOn includes caching of partial HTML documents. With InstantOn configured, when Yottaa receives a request for an HTML document, we check the cache to determine how to process the request.
| Cache miss |
If we get a cache miss, we process it like an ordinary HTML document with optimizations. In post-processing, we store the beginning portion of the document in cache. The stored cache defaults to the start of the <body> element in the HTML page, meaning the entire <head> section is cached. The bounds for stored elements are configurable. |
| Cache hit |
If we get a cache hit, we process the cached portion of the HTML page, apply optimizations, and return it to the browser as the start of a response. To obtain the remainder of the response, we forward the request to the origin server and use that response to determine the rest of the processed response. This processing includes the ordinary optimizations performed for an HTML page as well as several additional optimizations. This functionality allows Yottaa to serve some content to the browser without needing to wait for slow generating dynamic content. You can configure placeholders for the dynamic content. As a result, certain dynamic cached content may be initially rendered one way by the browser and then updated when the dynamic updating takes place. For example, a shopping cart image could render initially as empty, but after the origin server receives the request the updated content may render showing the number of items in the cart. |