| 2 | | |
| 3 | | It's a bit tricky at the moment as you need to stack more than one thing at once in order for Google to move the needle. This is a way for Google to protect their ranking factors and people doing split testing, but we have a process where we have enough participants and testers in order to isolate parts of the ranking factors apart from that whole stack of factors. |
| 4 | | |
| 5 | | For their speed ranking factor Google is using field data from Chrome that comes from the Chrome UX field data - e.g. real life speed and the Lighthouse score and loading benchmarks. |
| 6 | | |
| 7 | | One of the biggest bottlenecks for the WordPress core that is left if not the biggest is this one. It penalizes the speed score significantly. |
| 8 | | |
| 9 | | If this thing is fixed, it would solve by default a large bottleneck from the scoring which otherwise could be solved by paying like 200 USD to Cloudflare and use specific type of an optimization. |
| 10 | | |
| 11 | | Put a site with 1000K+ articles there and you can achieve drastically better search engine visibility from that alone. |
| 12 | | |
| 13 | | Fixing that score for all of the WordPress users that would make the update would give them better visibility for those that rely heavily on Gutenberg and not plugins in the search engines without them having to pay Ezoic or Cloudflare's premium to fix that score there. |
| 14 | | |
| 15 | | There is even more to that - especially on posts that have large amount of comments. |
| 16 | | |
| 17 | | I drive science-based SEO isolated tests and this is one of my primary business in the past year. We've been discussing that for a long period of time and this is the first time I am saying these conclusions in public. |