This is a known issue for software-rendered windows that update rapidly. There are several reasons for it so also several possible solutions...
* GTK 3.x is software-rendered, so rapid window redraws that require uploading new frames to the GPU from the CPU may be slow. This is mostly fixable by changing GTK to hardware rendering (coming in GTK 4.0).
* Wayland lacks 2D acceleration options that Xorg has. However those could plausibly be emulated by modifying the GTK 3.x code in theory.
* The EGLNative platform (that used by "Wayland" sessions) in Mutter/Gnome-Shell is generally slower than the X11 platform. It doesn't have to be. It's just a younger less mature platform, which we're trying to improve. Fixes for this would come in the 'mutter' project.
This is a known issue for software-rendered windows that update rapidly. There are several reasons for it so also several possible solutions...
* GTK 3.x is software-rendered, so rapid window redraws that require uploading new frames to the GPU from the CPU may be slow. This is mostly fixable by changing GTK to hardware rendering (coming in GTK 4.0).
* Wayland lacks 2D acceleration options that Xorg has. However those could plausibly be emulated by modifying the GTK 3.x code in theory.
* The EGLNative platform (that used by "Wayland" sessions) in Mutter/Gnome-Shell is generally slower than the X11 platform. It doesn't have to be. It's just a younger less mature platform, which we're trying to improve. Fixes for this would come in the 'mutter' project.