-
econsor
Hi there,
we have been analysing some backend performance issues that occur after working for a while in the WordPress admin.
While this might not be the main cause, we noticed that Gutenberg’s block previews (shown when hovering over blocks in the left sidebar) send multiple requests (wp-json, AJAX, etc.) per hover.When users move the cursor quickly over many blocks, the backend triggers numerous requests, which seems to add noticeable load and contribute to the slowdown, since the serverload (cpu workload) increases noticeably.
Is there a way to disable these previews or prevent them from loading on hover?
We couldn’t find any setting or filter to stop this behaviour or to remove the hover event entirely.Any insights or workarounds would be appreciated.
Thanks in advance!
-
Hi there,
Does the issue only happen to GB blocks or all blocks?
-
econsor
Hi Ying,
the issue happens with all blocks, but Gutenberg does not have the option to prevent this preview, so I hoped you guys would have a solution to this! 🙂
-
Can you take a screen record of the issue? I don’t quite understand what it is.
Let me know 🙂
-
econsor
Hi Ying,
sorry for the delay – here is the screen recording: https://streamable.com/qgtt7f
(its only available 2 days, keep in mind please. If its not available anymore, I will upload it again)As you can see on the right side of the video in the network tab, each hover action on these blocks triggers multiple requests for the preview rendering on the right of the left sidebar. This gradually slows down the site while editing, since the server and WordPress both have to process all those requests. On this particular website, we have several editors working simultaneously, so you can imagine how tedious it becomes when ten or more people are triggering all these requests at once.
I’m aware this is part of WordPress core behaviour, but I was hoping there might be a workaround or optimization on your side. 🙂
-
Thanks for the video, but unfortunately, I don’t think there’s anything we can do.
I would recommend checking with WP’s support in this case!.
- You must be logged in to reply to this topic.