diff --git a/docs/storefront/stencil/start/index.mdx b/docs/storefront/stencil/start/index.mdx
index 402c4991a..ca1d65ba9 100644
--- a/docs/storefront/stencil/start/index.mdx
+++ b/docs/storefront/stencil/start/index.mdx
@@ -52,6 +52,21 @@ Stencil's use of **YAML Front Matter** allows developers to request only the obj
 
 Stencil themes can access remote objects through event hook and use the hooks to trigger defined events based on shopper behavior. This will allow you to collect product data and optimize a shopper's experience. To facilitate theme-building, BigCommerce provides [stencil-utils](/docs/storefront/stencil/utils/reference) -- a client-side library for managing event hooks.
 
+## Pre-rendered Checkout pages
+
+All stencil themes utilize the [Speculation Rules API](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API) to pre-render checkout pages, improving performance and user experience.
+
+**Pre-rendering** means the browser begins loading a page in the background (for example, when a shopper hovers over or is likely to click a checkout link) so that it appears almost instantly when opened.  
+
+### Limitations
+
+- Currently only works if the shopper is using the Google Chrome browser.  Check [browser compatibility](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API#browser_compatibility) to see latest browser support.
+- The checkout won't pre-render if the shopper updates their cart on the cart page.
+
+<Callout type="info">
+  If you are hosting your own analytics you'll need to make changes to your implementation to ensure compatibility.  See our [hosted analytics documentation](https://developer.bigcommerce.com/docs/integrations/hosted-analytics) for more information.
+</Callout>
+
 ## Blueprint (Legacy framework)