Table of Contents
According to Google Martin Splitt, the company will not give publishers a break on Core Web Vitals since third-party apps provide must-have functionality. In response to a question by Loren Baker, he discussed the issue of publishers who want marketing and sales related functionality on their pages, which slows down the website and contributes to a poor score on web vitals.As an example, a Shopify site with email list, review, and chatbox functionality had extremely poor core web vitals performance. But the question was applicable to all WordPress plugins, themes and third-party apps, regardless of platform. Publishers are generally not at fault for performance issues resulting from Core Web Vitals, which makes this a difficult issue to address. Apps, themes, and plugins are to blame for the poor performance. It’s unfair for Google to penalize a site for using a third-party plugin or app that provides users or publishers with a necessary function.
“Is the Core Web Vitals Update going to give people a break, so to speak, if they’re using a third party app which is leading to their site having lower scores than if they would if they had no apps on the page?” The answer from Martin Splitt focused first on Google’s goals for Core Web Vitals, trying to get the publisher to understand it from that perspective. “I understand where they’re coming from. The answer for all of these questions is pretty much the same.
As developers we’d like to speak of that as technical depth. So if they make things slower, that reflects in the core web vitals and that’s what matters in the end.”
Martin talked about reviewing the core web vitals and summarized his thoughts by saying: Apps and functionality should also be reviewed to ensure that they meet a must-have user experience. If it’s somewhat superfluous, consider getting rid of it. Implement site functionality in a way that does not interfere with the page’s rendering. Editing the code may involve adding extra elements attributes (like the lazy load image attribute or link rel=”preload”). The site publisher is unfortunately responsible for fixing this until template and plugin makers take action, whether they like it or not. Ask the app, plugin, and theme developers to create better implementations.