Simplify command removes too many nodes on closed paths

When preparing SVG assets for low‑traffic web use, designers often rely on Inkscape’s Simplify command (Ctrl+L) to lower node counts and reduce file size. The command applies the Douglas‑Peucker algorithm with a distance threshold that is not exposed as a precise numeric setting in the current UI, making the amount of simplification dependent on the selection state and the underlying path complexity. This opacity creates uncertainty about how much geometric detail will be lost before the simplified path deviates perceptibly from the original artwork.

Given the need to balance file‑size savings with visual fidelity, what level of node reduction is acceptable for typical icon‑scale graphics? How can a user determine or set an effective simplification threshold without resorting to trial‑and‑error? Is there a reliable method to preview the impact of Simplify on a path before committing the change?