# Why Extensions Should Minimize Page Impact Slug: why-extensions-should-minimize-page-impact. Canonical: https://tradingtune.com/blog/why-extensions-should-minimize-page-impact ## Summary Shows why tools should avoid unnecessary work on pages they support. ## Key facts - An extension supporting a charting page should read only what it needs, act only when something changes, and never block the main thread for work the user did not ask for. - An extension that polls the DOM on a tight timer competes with the chart for CPU time exactly when the trader is panning or zooming. - A setting that looks fine on one light chart has only been observed once, and a busier page can expose problems the light test never showed. - The cost of skipping this discipline is quiet: a chart that stutters slightly or a redraw that lags a beat, with no crash or error to point to. ## Outline - What Minimizing Page Impact Actually Means for a Trading Extension (#what-minimizing-page-impact-actually-means-for-a-trading-extension) - Setting Up a Low-Impact Sweep: Parameters, Ranges, and a Walk-Forward Window (#setting-up-a-low-impact-sweep-parameters-ranges-and-a-walk-forward-window) - What Changes as You Move Across the Settings (#what-changes-as-you-move-across-the-settings) - Illustrative Data: Reading a Page-Impact Sweep (#illustrative-data-reading-a-page-impact-sweep) - An Edge Case: A Debounce Setting That Looked Fine In-Sample (#an-edge-case-a-debounce-setting-that-looked-fine-in-sample) - Applying This to Your Own Extension or Workflow (#applying-this-to-your-own-extension-or-workflow) - Conclusion: Extensions Earn Their Place by Doing Less, Not More (#conclusion-extensions-earn-their-place-by-doing-less-not-more) - Sources (#sources) ## Code snippets - Anchor: #pine-snippet-1