The reason I want to see a compositor comparison is because on Wayland the implementation really matters. This isn’t actually a x vs Wayland comparison, it’s actually x vs 1 Wayland compositor.

For all we know there’s a KWin perf issue that has nothing to do with Wayland itself.

I’ve been a paying Kagi user for years and I don’t see why I would use this browser. The only selling point to me is WebKit and there are only projects that support that on Linux

Hmm it looks like they only tested KDE (KWin) compositor. I’d love to see how various Wayland server implementations impact performance since the compositor controls when it commits frames to the display controller.