1. Deferred Script Injection
   Tracking scripts such as inject-clicks.js, tracking-core.js, and preview-injector.js are not hard-coded into every page. Instead, they are injected only when tracking is enabled and for the post types selected in Settings. This avoids unnecessary script execution on pages where analytics is not needed .
2. Asynchronous Loading
   The plugin uses wp_enqueue_script with dependencies and proper hooks (wp_footer / wp_head), ensuring JavaScript is loaded asynchronously and doesn’t block initial rendering. For example, the heatmap loader files (heatmap-loader.php, heatmap-loader-mobile.php) prepare script injection without delaying core page resources .
3. Lightweight Tracking Payloads
   Tracking requests (e.g., in tracking.php, user-id-sync.js) are minimal AJAX/REST calls that send only necessary information (click position, user ID, session data). They run in the background, meaning they don’t block page interactions .
4. Conditional Components
   Heavy components such as iframes (iframe-render.php, iframe-render-mobile.php) and overlays (panel-above-iframe.php) are loaded only inside the admin visualization panel — not on the live frontend for visitors. This separation ensures that end-users don’t experience slowdown from heatmap rendering .
5. Database Writes Optimized
   Tracking data is batched into dedicated tables (e.g., clicks, mouse moves, referrers). Each event is logged with minimal overhead, avoiding the default wp_postmeta bloat and keeping frontend requests fast .

📊 Impact on PageSpeed:

• The plugin has negligible effect on initial load time because scripts are injected after content and don’t block rendering.
• Real-time tracking calls are lightweight and non-blocking.
• Largest Contentful Paint (LCP) and First Input Delay (FID) remain unaffected since recording happens in the background.
• Additional overhead is only measurable on high-traffic sites with tens of thousands of tracked events per minute, but this can be mitigated via the Cleaning tab to purge old data and by selective tracking in Settings.

👉 In short: the plugin is frontend-lightweight. Visitors won’t notice a slowdown, and page speed scores remain stable, since all heavy rendering is restricted to the admin dashboard.