![\"WordPress](\"https:\/\/marketingnewsbox.com\/wp-content\/uploads\/2022\/10\/wordpress-6-1-is-jam-packed-with-performance-upgrades-via-sejournal-martinibuster.png\")
<\/p>\nWordPress 6.1, arriving November 2022, is jam-packed with performance improvements, signaling that this may be the update that many have been waiting for.<\/p>\n
WordPress performance scores from the beginning of 2022 until the end of September have been relatively stable, going up a few percentage points in the spring then dropping in the summer, ending September roughly 3 percentage points higher than from the start of the year.<\/p>\n
<\/p>\n
<\/p>\n
Most other platforms have enjoyed more substantial performance improvements month after month in 2022:<\/strong><\/p>\n WordPress publishers hoping for performance improvements had little good news this year.<\/p>\n But that\u2019s about to change in a big way.<\/p>\n WordPress 6.1 comes packed with substantial improvements, some of which are referred to as \u201cmassive.\u201d<\/p>\n An important performance boost is the addition of caching to WP_Query<\/a> in the database.<\/p>\n What that means is that every time a visitor requests a webpage that request will remain in a cache, a memory of what was retrieved from the database.<\/p>\n When another visitor requests the same webpage, instead of making another request to the database WordPress will instead retrieve the webpage data from the cache (memory) instead of retrieving (making a query) from the database. That results in faster performance.<\/p>\n The WordPress core contributor who worked on this improvement recently tweeted<\/a>:<\/p>\n \u201cIn WordPress 6.1, there is a massive improvement to database performance.<\/p>\n Database queries in WP_Query are now cached.<\/p>\n A ticket I have been working on for 5+ years was merged.<\/p>\n This should result in billions of less repeated database queries\u201d<\/p>\n<\/blockquote>\n When a webpage is requested, the webpage will make different requests for various components of the page. This improvement streamlines that process by reducing the number of database queries (requests for parts of a webpage).<\/p>\n WordPress explains<\/a>:<\/p>\n \u201cWhen running profiling tools against the responses of REST API requests, it was discovered that post controllers request a lot of linked data to each post.<\/p>\n For example, when returning a post in a REST API response, linked data such as author (user), featured image, and parent post were all requested.<\/p>\n As these linked items were not primed in caches, it could mean that for each post in the REST API response there would be 3 separate database queries: one for the user, one for the featured image, and another for the parent post.<\/p>\n In WordPress 6.1 all the caches are primed in a single database query \u201c<\/p>\n<\/blockquote>\n There are other cache related improvements that speed up the delivery of webpages.<\/p>\n These are a couple of improvements.<\/p>\n In simple terms, one improvement that is called \u201cCheck cache key types<\/a>\u201d addresses a problem created by plugins.<\/p>\n This fixes an issue that causes a failure that can result in slightly weird behavior or outright failure.<\/p>\n This improvement makes it easier for plugin developers to notice the problem.<\/p>\n The developer notes on this fix states:<\/strong><\/p>\n \u201cThis commit introduces a quick type check on the given cache keys and adds a _doing_it_wrong() message that should help plugin developers to notice these issues quicker.\u201d<\/p>\n<\/blockquote>\n The second improvement is called, Remove `@access private` from cache priming functions<\/a>.<\/p>\n A plain English explanation for this improvement is that it provides theme and plugin developers the opportunity to access and use certain functions that will result in less database queries which in turn will speed up site performance.<\/p>\n Improves performance for websites with a large amount of custom taxonomies (like tags and categories).<\/p>\n Reduces database queries in multisite environments.<\/p>\n This is a performance boost from how images are deferred in order to keep them from slowing webpage retrieval and display, resulting in performance boosts.<\/p>\n WordPress describes it like this<\/a>:<\/p>\n \u201cRecently I have been playing around with another special attribute to the img tag which is basically decoding=\u201dasync\u201d.<\/p>\n After implementing async decoding to the images in a page, the page load became, even more, faster and images are decoded asynchronously by the browser, loading the contents almost instantly and also reducing page render time. This is a huge performance booster to any webpages which has a lot of images (so basically most sites).\u201d<\/p>\n<\/blockquote>\n This improves how \u201cblock registration\u201d is handled. This is an improvement to how block are identified and handled.<\/p>\n WordPress describes it<\/a>:<\/p>\n \u201c\u2026reduce filesystem reads and processing of block.json files, which should benefit all WordPress sites and improve performance\u2026\u201d<\/p>\n<\/blockquote>\n WordPress 6.1 comes with two new site health checks. While this isn\u2019t a performance improvement itself, it does help publishers identify whether they can improve their site peformance with the use of a Persistent Object Cache and\/or a Full Page Cache.<\/p>\n The Persistent Object Cache holds frequently requested webpage parts in a cache (in memory), speeding up the display of a webpage and reducing server load.<\/p>\n A Full Page Cache is a cache of the entire webpage, essentially making a webpage behave more like a static HTML page. A full page cache is generally not useful on a site that is dynamic and contains personalization.<\/p>\n This seems like kind of a bug fix but it\u2019s also an improvement to wp-cron.php, which is a task scheduler for things like backups, scheduled posts or updates.<\/p>\n The update will speed up performance by making it compatible (again) with LiteSpeed Web Server plus LSAPI. Technical details here<\/a>.<\/p>\n There are many more performance improvements but the above listed updates are the most notable.<\/p>\n I addition to performance improvements, WordPress 6.1 will also arrive with improvements to accessibility, the block editor, more flexibility and options for theme developers, updated external libraries to latest versions, new functions, new filters and even a new oEmbed provider for podcasts.<\/p>\n Updates are generally incremental but WordPress 6.1 is shaping up to be a fairly substantial one, look for it to be released on November 1, 2022.<\/p>\n\n
\u201cMassive Improvement\u201d To WP_Query Performance<\/h2>\n
\n
Improvement to REST API Database Queries<\/h2>\n
\n
Additional Caching Improvements<\/h2>\n
Improvements to Cache API<\/h3>\n
\n
Post, Post Types Improvements<\/h2>\n
Multisite improvements<\/h2>\n
Media Handling Improvement<\/h2>\n
\n
Improved PHP performance for Core Blocks Registration<\/h2>\n
\n
New Site Health Checks<\/h2>\n
Persistent Object Cache<\/h3>\n
Full Page Cache<\/h3>\n
Cron API<\/h2>\n
Many More Performance Improvements<\/h2>\n
Citation<\/h2>\n