@anthony That's interesting; I'll toy around with that!

What prompted this was noticing a huge amount of time Chromium is spending in "ResourceFetcher::requestResource" (visible if you turn on "show all events"). I had a hunch that this was related to the `<img>`s, so I removed the `src` and suddenly all the costs went away. I'll need to dig to see if it's `loading=lazy`-related…

As for IntersectionObserver, yes, I messed around with that too. It's definitely the better cross-browser choice.