SEO
WordPress Proposes Performance Team For Core Web Vitals
A WordPress proposal admits it is falling behind Wix and similar platforms and suggests they need to create a performance team to coordinate speed improvements.
While some may find it controversial for someone at WordPress to admit they were falling behind in the race to improve speed scores, it’s a fact that platforms that manage the technical side of publishing are pulling ahead of WordPress in terms of speed.
Objective speed metrics from Chrome users, reported in Google’s monthly CrUX (Chrome User Experience Report) unquestionably shows that WordPress is slowly being left behind by platforms that are better able to control software development so that it conforms to best practices for speed.
Because the WordPress platform is relatively decentralized compared to platforms like Wix and Squarespace they are less able to influence best practices for speed performance across the entire WordPress ecosystem.
WordPress Admits Falling Behind Wix, Shopify and Squarespace
The proposal was blunt in its assessment that WordPress was falling behind:
“Compared to other platforms (e.g., Wix, Shopify, Squarespace), WordPress is falling behind.
Other platforms are on average faster – and becoming increasingly faster – than WordPress websites…”
That’s not an opinion, it’s a statement of fact that WordPress is falling behind Wix.
The Core Web Vitals Scores revealed from the Chrome User Experience Report 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 that situation.
Being open-minded to the possibility that things need to improve is a positive sign because the first step to becoming the best often involves identifying areas of improvement.
The proposal is being spearheaded by WordPress developers from Google and Yoast.
WordPress Needs a Performance Team
The proposal states that it needs an official team to coordinate the performance side of WordPress core development.
So instead of performance being almost an afterthought to improvements to other areas of WordPress, speed performance can move to the front because of advocates who can now help coordinate improvements.
The proposal states:
“We believe that WordPress needs an official Performance Team responsible for coordinating efforts to increase the performance (speed) of WordPress.”
Why WordPress Needs a Performance Team
The next section of the proposal outlines why they feel a Performance Team is necessary.
The statement references user experience, user expectations, SEO and also economic and ecological benefits.
That last part is a reference to the little known fact that websites that are difficult to render are said to be “expensive.”
That means that devices need to expend more resources to build web pages that are complex and have multiple resources necessary for rendering the web page.
This in turn impacts energy consumption of the mobile device downloading the web page.
The impact is not only to the battery but also influences how much energy society needs to generate to keep on downloading inefficiently coded websites.
The proposal notes:
“Users expect and prefer fast experiences (consciously or otherwise). Research shows that fast websites can provide a better user experience, increase engagement, benefit SEO, increase conversion, and be more economically and ecologically friendly.”
WordPress Speed Should Not be the Job of a Plugin
The proposal says that the job of optimizing WordPress should not fall to third party plugins and that it should not be the burden of those who use WordPress to fix it and make it better.
It states:
“Average end-users can’t be expected to be performance experts.”
This is something that I suggested in February 2021 in the article:
Core Web Vitals Not Really Your Problem?
Google is burdening the USERS of software like WordPress and not the developers to fix it for Core Web Vitals. Is that fair?
Software publishers have created plugins to help WordPress cache files in order to serve the faster, plugins that shrink CSS files and some plugins that remove JavaScript so that it is only downloaded when it is needed.
WordPress is proposing that this job of optimizing WordPress should be performed natively by WordPress itself instead of relying on third party plugins.
The proposal introduces the concept of “performance by default” as a way to internalize a focus on speed throughout the development ecosystem.
“Achieving reasonable performance levels shouldn’t be plugin territory, but part of core (aka, “performance by default”)
Highlights of the proposal:
- Average end-users can’t be expected to be performance experts.
- Achieving high levels of performance requires technical considerations to be ‘built-in’ across the whole stack;
- The plugin ecosystem doesn’t help users who don’t know that they need help, or who are poorly served by the plugin ecosystem.
- Users determining which CMS to choose are / will be increasingly influenced by performance (and the associated UX/SEO/conversion factors), and we’ll lose ground to faster platforms.
- Democratizing publishing’ requires that published content be discoverable; which will be less likely to occur via search engines (which influence or account for the majority of new content discovery) for slow(er) sites”
WordPress Proposes Reconsidering Role of Plugins for Optimization
The proposal also suggests a reconsideration of dependence on third party plugins for optimization issues while also stating that there are some areas where plugins are better suited.
The WordPress proposal offered examples of where plugins were the preferred solution:
- “Integrations with specific CDNs
- Template transformation processes (e.g., AMP)
- Any non-standardized performance technology
- Any experimental standards (e.g., browser APIs / capabilities with limited adoption)
These distinctions will need exploring and lines will need drawing (and maintaining) as part of the team’s activity.”
How WordPress Performance Team May Proceed
If the proposal is accepted the proposal suggests steps to get the project organized:
- “Set up Slack channel and meeting schedule, and make.wordpress.org infrastructure.
- Benchmark performance and define ongoing/future measurement & success criteria
- Identify priority projects for CWV improvements with high-level timelines
- Assign responsibilities for the projects identified”
Response to the Proposal by the WordPress Community
Joost de Valk, founder of Yoast SEO Plugin underlined that this is a proposal and not a done-deal.
“This isn’t saying “we’re going to do this, just so you know”, it is: “we want to do this, will you join us?””
The response to the proposal was overwhelmingly positive.
Typical responses:
“This is a great initiative. It might finally get the attention it deserves.
I am deeply excited by this proposal! Looking forward to the discussion here and being able to pitch in as things…
Excellent proposal! In the past year(s) WordPress has been making a lot of steps to tackle some front-end performance problems: lazy loading, WebP support, Gutenberg (yes, I will put this here). But overall there is much more potential and opportunities here. Sign me up”
A non-developer member of the WordPress community noted all the plugins they currently used and expressed how it would be an improvement to not have to rely on so many third party plugins:
“As someone who is not a developer but uses an array of plugins (Autoptimize, ASYNC CriticalCSS, Page Speed Booster, CAOS, OMFG, and ShortPixel – all in combination with WP Engine hosting and Cloudflare CDN, as well as now native Lazy Load feature of WordPress) to optimize my sites and those of my clients, I would like not to have to depend on this suite of tools all the time to increase performance.”
WordPress Performance Team is a Great Idea
The formation of a WordPress Performance Team is not just a good idea, it’s a great idea.
It’s arguable that WordPress should have had a performance team since day one. Nevertheless it’s super exciting to see this initiative given a breath of life.
Citation
Read the WordPress Proposal
Proposal for a Performance Team
SEO
8% Of Automattic Employees Choose To Resign
WordPress co-founder and Automattic CEO announced today that he offered Automattic employees the chance to resign with a severance pay and a total of 8.4 percent. Mullenweg offered $30,000 or six months of salary, whichever one is higher, with a total of 159 people taking his offer.
Reactions Of Automattic Employees
Given the recent controversies created by Mullenweg, one might be tempted to view the walkout as a vote of no-confidence in Mullenweg. But that would be a mistake because some of the employees announcing their resignations either praised Mullenweg or simply announced their resignation while many others tweeted how happy they are to stay at Automattic.
One former employee tweeted that he was sad about recent developments but also praised Mullenweg and Automattic as an employer.
He shared:
“Today was my last day at Automattic. I spent the last 2 years building large scale ML and generative AI infra and products, and a lot of time on robotics at night and on weekends.
I’m going to spend the next month taking a break, getting married, and visiting family in Australia.
I have some really fun ideas of things to build that I’ve been storing up for a while. Now I get to build them. Get in touch if you’d like to build AI products together.”
Another former employee, Naoko Takano, is a 14 year employee, an organizer of WordCamp conferences in Asia, a full-time WordPress contributor and Open Source Project Manager at Automattic announced on X (formerly Twitter) that today was her last day at Automattic with no additional comment.
She tweeted:
“Today was my last day at Automattic.
I’m actively exploring new career opportunities. If you know of any positions that align with my skills and experience!”
Naoko’s role at at WordPress was working with the global WordPress community to improve contributor experiences through the Five for the Future and Mentorship programs. Five for the Future is an important WordPress program that encourages organizations to donate 5% of their resources back into WordPress. Five for the Future is one of the issues Mullenweg had against WP Engine, asserting that they didn’t donate enough back into the community.
Mullenweg himself was bittersweet to see those employees go, writing in a blog post:
“It was an emotional roller coaster of a week. The day you hire someone you aren’t expecting them to resign or be fired, you’re hoping for a long and mutually beneficial relationship. Every resignation stings a bit.
However now, I feel much lighter. I’m grateful and thankful for all the people who took the offer, and even more excited to work with those who turned down $126M to stay. As the kids say, LFG!”
Read the entire announcement on Mullenweg’s blog:
Featured Image by Shutterstock/sdx15
SEO
YouTube Extends Shorts To 3 Minutes, Adds New Features
YouTube expands Shorts to 3 minutes, adds templates, AI tools, and the option to show fewer Shorts on the homepage.
- YouTube Shorts will allow 3-minute videos.
- New features include templates, enhanced remixing, and AI-generated video backgrounds.
- YouTube is adding a Shorts trends page and comment previews.
SEO
How To Stop Filter Results From Eating Crawl Budget
Today’s Ask An SEO question comes from Michal in Bratislava, who asks:
“I have a client who has a website with filters based on a map locations. When the visitor makes a move on the map, a new URL with filters is created. They are not in the sitemap. However, there are over 700,000 URLs in the Search Console (not indexed) and eating crawl budget.
What would be the best way to get rid of these URLs? My idea is keep the base location ‘index, follow’ and newly created URLs of surrounded area with filters switch to ‘noindex, no follow’. Also mark surrounded areas with canonicals to the base location + disavow the unwanted links.”
Great question, Michal, and good news! The answer is an easy one to implement.
First, let’s look at what you’re trying and apply it to other situations like ecommerce and publishers. This way, more people can benefit. Then, go into your strategies above and end with the solution.
What Crawl Budget Is And How Parameters Are Created That Waste It
If you’re not sure what Michal is referring to with crawl budget, this is a term some SEO pros use to explain that Google and other search engines will only crawl so many pages on your website before it stops.
If your crawl budget is used on low-value, thin, or non-indexable pages, your good pages and new pages may not be found in a crawl.
If they’re not found, they may not get indexed or refreshed. If they’re not indexed, they cannot bring you SEO traffic.
This is why optimizing a crawl budget for efficiency is important.
Michal shared an example of how “thin” URLs from an SEO point of view are created as customers use filters.
The experience for the user is value-adding, but from an SEO standpoint, a location-based page would be better. This applies to ecommerce and publishers, too.
Ecommerce stores will have searches for colors like red or green and products like t-shirts and potato chips.
These create URLs with parameters just like a filter search for locations. They could also be created by using filters for size, gender, color, price, variation, compatibility, etc. in the shopping process.
The filtered results help the end user but compete directly with the collection page, and the collection would be the “non-thin” version.
Publishers have the same. Someone might be on SEJ looking for SEO or PPC in the search box and get a filtered result. The filtered result will have articles, but the category of the publication is likely the best result for a search engine.
These filtered results can be indexed because they get shared on social media or someone adds them as a comment on a blog or forum, creating a crawlable backlink. It might also be an employee in customer service responded to a question on the company blog or any other number of ways.
The goal now is to make sure search engines don’t spend time crawling the “thin” versions so you can get the most from your crawl budget.
The Difference Between Indexing And Crawling
There’s one more thing to learn before we go into the proposed ideas and solutions – the difference between indexing and crawling.
- Crawling is the discovery of new pages within a website.
- Indexing is adding the pages that are worthy of showing to a person using the search engine to the database of pages.
Pages can get crawled but not indexed. Indexed pages have likely been crawled and will likely get crawled again to look for updates and server responses.
But not all indexed pages will bring in traffic or hit the first page because they may not be the best possible answer for queries being searched.
Now, let’s go into making efficient use of crawl budgets for these types of solutions.
Using Meta Robots Or X Robots
The first solution Michal pointed out was an “index,follow” directive. This tells a search engine to index the page and follow the links on it. This is a good idea, but only if the filtered result is the ideal experience.
From what I can see, this would not be the case, so I would recommend making it “noindex,follow.”
Noindex would say, “This is not an official page, but hey, keep crawling my site, you’ll find good pages in here.”
And if you have your main menu and navigational internal links done correctly, the spider will hopefully keep crawling them.
Canonicals To Solve Wasted Crawl Budget
Canonical links are used to help search engines know what the official page to index is.
If a product exists in three categories on three separate URLs, only one should be “the official” version, so the two duplicates should have a canonical pointing to the official version. The official one should have a canonical link that points to itself. This applies to the filtered locations.
If the location search would result in multiple city or neighborhood pages, the result would likely be a duplicate of the official one you have in your sitemap.
Have the filtered results point a canonical back to the main page of filtering instead of being self-referencing if the content on the page stays the same as the original category.
If the content pulls in your localized page with the same locations, point the canonical to that page instead.
In most cases, the filtered version inherits the page you searched or filtered from, so that is where the canonical should point to.
If you do both noindex and have a self-referencing canonical, which is overkill, it becomes a conflicting signal.
The same applies to when someone searches for a product by name on your website. The search result may compete with the actual product or service page.
With this solution, you’re telling the spider not to index this page because it isn’t worth indexing, but it is also the official version. It doesn’t make sense to do this.
Instead, use a canonical link, as I mentioned above, or noindex the result and point the canonical to the official version.
Disavow To Increase Crawl Efficiency
Disavowing doesn’t have anything to do with crawl efficiency unless the search engine spiders are finding your “thin” pages through spammy backlinks.
The disavow tool from Google is a way to say, “Hey, these backlinks are spammy, and we don’t want them to hurt us. Please don’t count them towards our site’s authority.”
In most cases, it doesn’t matter, as Google is good at detecting spammy links and ignoring them.
You do not want to add your own site and your own URLs to the disavow tool. You’re telling Google your own site is spammy and not worth anything.
Plus, submitting backlinks to disavow won’t prevent a spider from seeing what you want and do not want to be crawled, as it is only for saying a link from another site is spammy.
Disavowing won’t help with crawl efficiency or saving crawl budget.
How To Make Crawl Budgets More Efficient
The answer is robots.txt. This is how you tell specific search engines and spiders what to crawl.
You can include the folders you want them to crawl by marketing them as “allow,” and you can say “disallow” on filtered results by disallowing the “?” or “&” symbol or whichever you use.
If some of those parameters should be crawled, add the main word like “?filter=location” or a specific parameter.
Robots.txt is how you define crawl paths and work on crawl efficiency. Once you’ve optimized that, look at your internal links. A link from one page on your site to another.
These help spiders find your most important pages while learning what each is about.
Internal links include:
- Breadcrumbs.
- Menu navigation.
- Links within content to other pages.
- Sub-category menus.
- Footer links.
You can also use a sitemap if you have a large site, and the spiders are not finding the pages you want with priority.
I hope this helps answer your question. It is one I get a lot – you’re not the only one stuck in that situation.
More resources:
Featured Image: Paulo Bobita/Search Engine Journal
-
WORDPRESS2 days ago
WordPress biz Automattic details WP Engine deal demands • The Register
-
SEARCHENGINES4 days ago
Daily Search Forum Recap: September 30, 2024
-
SEO6 days ago
Yoast Co-Founder Suggests A WordPress Contributor Board
-
SEO5 days ago
6 Things You Can Do to Compete With Big Sites
-
SEARCHENGINES6 days ago
Google’s 26th Birthday Doodle Is Missing
-
SEARCHENGINES5 days ago
Google Volatility With Gains & Losses, Updated Web Spam Policies, Cache Gone & More Search News
-
SEARCHENGINES3 days ago
Daily Search Forum Recap: October 1, 2024
-
SEO5 days ago
An In-Depth Guide For Businesses