A performance audit can start with a cheap question: which image loading instructions did the server actually send? That question is narrower than asking whether a page is fast. Keeping the two separate makes the first script useful without turning it into an invented benchmark.

I captured five public RadarMakers pages over HTTPS on October 30, 2026, at about 11:49 UTC. The sample includes the free maker tools collection , a press kit, an about page, a launch checklist, and a sale catalog. This is a convenience sample from one site, not a representative survey of the web.

Count the literal attributes

Route loading lazy loading eager Attribute absent Total img elements

/press 16 0 0 16

/about 1 0 0 1

/tools 3 0 0 3

/launch-checklist 6 0 1 7

/for-sale 2 0 2 4

Source: retained RadarMakers production responses captured October 30, 2026. Chart: RadarMakers.

Source: retained RadarMakers production responses captured October 30, 2026.…