Why use SVG as a data URI instead of a PNG texture file?
Because SVG describes the dot as vector math, so the same few bytes of code scale to any screen density without blurring, while a PNG would need a separate @2x or @3x version for retina screens, each one an extra network request.
What is the maximum dot opacity that still keeps text legible?
It depends on font weight and size, but as a practical rule, opacity above 0.15 over a background the same color family as the text already reduces effective contrast enough to risk falling under the WCAG 4.5:1 minimum required for normal text.
Does changing the tile from 32px to 48px require redrawing the dot?
No: because the SVG uses a proportional viewBox, changing the background-size value in the generated CSS is enough; the dot's own drawing stays identical, only the repeat distance between one dot and the next grows.
Does this dot pattern add page weight the way a PNG image would?
No: a data URI for a single circle usually stays under 200 bytes of code, versus several kilobytes for an equivalent PNG, and because it is embedded directly in the CSS, the browser makes no additional HTTP request to load it at all.