During replay, requests and responses that are captured by Tealeaf are reassembled by RTV and displayed in the sequential order in which the user experienced them. When you display the response, RTV can identify other content in the page that must be acquired. Typically, this referenced content is static and is not captured by Tealeaf.

Each item that is referenced in the response may or may not finish loading successfully. How these elements run on a visitor's browser and on the desktop of the user that runs RTV can vary based on the different systems that render the user impression. For example, if the visitor's computer was able to successfully fetch a Cascading Style Sheet (.css), and the RTV computer cannot fetch it, then the pages differ in rendering those styles that are defined in the .css.

• If the visitor's computer can fetch an image while the RTV computer cannot, then the page renderings differ. Security issues may play a role in reproducing the user impression.
• If the user must log in to a site before the site delivers binary files, then the user that runs RTV must be able to log in to the site, too.