A WordPress proposal admits it lags behind Wix and similar platforms and suggests that they need to create a performance team to coordinate speed improvements.
While some may find this controversial for someone on WordPress to admit they were falling behind in the race for improvement speed scores, it's a fact that the platforms that handle the technical side of the post are ahead of WordPress in terms of speed.
Objective speed metrics of Chrome users, reported in the Google's monthly CrUX (Chrome User Experience Report) indisputably shows that WordPress is slowly being left behind.pte by platforms that are better able to control software development so that it conforms to best practices in speed.
Because WordPress p latform is relatively decentralized compared to platforms- Forms like Wix and Squarespace, they are less able to influence speed performance best practices across the WordPress ecosystem.
Related: WordPress vs Wix: Core winner Web Vitals
WordPress admits to lagging behind Wix, Shopify and Squarespace
The proposal was blunt in its assessment that WordPress was lagging behind:
This is not an opinion, it is a statement of fact that WordPress is lagging behind Wix.
Core Web Vitals scores revealed from Chr Some user experience reports show that it is a fact that WordPress is gradually falling behind Wix in terms of Core Web Vitals .
This proposal aims to take action to change this situation.
Being open to the possibility that things need to improve is a positive sign, as the first step to becoming the best often involves identifying areas for improvement.
The proposal is led by WordPress developers Google and Yoast.
WordPress needs a performance team
The proposal states that it needs an official team to coordinate the performance side of core WordPress development.
So instead of performance being almost a reflection after the fact about improvements in other areasWordPress speed performance can come to the fore thanks to advocates who can now help coordinate improvements.
Why WordPress needs a performance team
The following section of the proposal explains why they feel a performance team is needed.
The statement refers to the 'user experience, user expectations, SEO as well as economic and ecological benefits.
This last part refers to the little-known fact that difficult-to-view websites are said to be "expensive" .
This means that devices have to spend more resources to create complex web pages. and have multiple resources required for rendering the web page.
This in turn impacts the power consumption of the mobile device downloading the web page.
The impact is not onlynot only on battery but also influences the amount of power the company needs to generate to continue downloading inefficiently coded websites.
The proposal notes:
Related: Core Web Vitals: A Complete Guide
WordPress speed shouldn't be a plugin 's job
The proposal says that WordPress optimization work shouldn't fall to third-party plugins and it shouldn't be the burden of those who use WordPress to fix and improve it.
It says :
This is something I suggested in February 2021 in the article:
The essentials of the web are not not really your problem?
Google is overloading USERS of software like WordPress and not developers to fix it forCore Web Vitals. Is that fair?
WordPress suggests that this WordPress optimization work be done natively by WordPress itself instead of rely on third-party plugins.
The proposal introduces the concept of 'performance by default' as a way to internalize a target on speed across the development ecosystem .
"Achieving reasonable performance levels shouldn't be a tory, but part of the kernel (aka, " default performance ")
- Average end users may not be expected to be performance experts.
- PTo achieve high performance levels, technical considerations need to be 'built in' across the stack;
- The plugin ecosystem does not help users who do not know what to expect. They need help, or are poorly served by the plugin ecosystem.
- Users who determine which CMS to choose are / will increasingly be influenced by performance (and the associated UX / SEO / conversion factors), and we will lose ground in favor of faster platforms.
- The democratization of publishing requires that published content be visible; which will be less likely to occur via search engines (which influence or account for the majority of new content discovery) for (slower) sites "
WordPress suggests reconsidering the role of plugins for optimization
The proposal also suggests a reconsideration of the dependency on third-party plugins foroptimization issues while also indicating that there are some areas where plugins are better suited.
The WordPress proposal offered examples of where plugins were the preferred solution:
Related: WordPress SEO Guide: Everything You Need to Know
How the WordPress Performance Team Can Do It
If the proposal is accepted, the proposal suggests steps to organize the project:
- "Configure the Slack channel and the meeting calendar, and the infrastructure make.wordpress.org.
- Compare performance and define criteria for current / future measurement and success
- Identify priority projects for CWV improvements with high deadlines level
- Assign responsibilities for identified projectss "
Response to the proposal by the WordPress community
Joost de Valk, founder of Yoast SEO Plugin underlined that this is a proposition and not a solved fact l.
The response to the proposal has been overwhelmingly positive.
A member non-developer WordPress community noted all the plugins they were currently using and expressed how much an improvement it would be to not have to rely on so many third-party plugins:
The WordPress performance team is a great idea
Forming a WordP The performance team is not just a good idea, it is a great idea .
Arguably WordPress should have had a performance team from day one. Nonetheless, it's super exciting to see this initiative breathe life into.
Read the WordPress proposal
Proposal for a performance team