> ## Documentation Index > Fetch the complete documentation index at: https://www.adora.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Performance FAQ ## How does Adora capture data? Adora uses the [`rrweb`](https://github.com/rrweb-io/rrweb) package for session recording, the same package used by Sentry and Datadog. `rrweb` relies on the [MutationObserver](https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver) API, which monitors changes to the DOM tree. `MutationObserver` is a high-performance web API, designed as a more efficient successor to `DOM Mutation Events`. *** ## Where are screenshots captured? Most of Adora’s processing occurs on our servers. Screenshots are captured server-side, and `canvas` content is excluded from recordings. Additionally, events are compressed to minimize the amount of data sent to our servers. *** ## Does Adora impact website performance? While no integration is entirely without performance cost, the impact of our script on the client is minimal and unnoticeable to end users. Independent reviews by engineers confirm that the performance overhead of session recording is negligible: * [Highlight.io: Session Replay Performance](https://www.highlight.io/blog/session-replay-performance) * [PostHog: Session Recording Performance](https://posthog.com/blog/session-recording-performance) For instance, testing Adora's capture script on our product, which handles numerous elements and SVGs, showed no measurable impact on memory usage. On a reference page with 67 MB (67,000,000 bytes) of total heap memory, performance remained unaffected. Performance screenshot