<div style="text-align:center"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///ywAAAAAAQABAAACAUwAOw==" fifu-lazy="1" fifu-data-sizes="auto" fifu-data-srcset="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=75&resize=75&ssl=1 75w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=100&resize=100&ssl=1 100w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=150&resize=150&ssl=1 150w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=240&resize=240&ssl=1 240w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=320&resize=320&ssl=1 320w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=500&resize=500&ssl=1 500w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=640&resize=640&ssl=1 640w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=800&resize=800&ssl=1 800w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=1024&resize=1024&ssl=1 1024w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=1280&resize=1280&ssl=1 1280w, https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1&w=1600&resize=1600&ssl=1 1600w" width="1586" height="896" fifu-data-src="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Performance Chat Summary: 7 November 2023" title="Performance Chat Summary: 7 November 2023" srcset="https://i1.wp.com/www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023.png?ssl=1 1586w, https://www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023-300x169.png 300w, https://www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023-1024x579.png 1024w, https://www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023-768x434.png 768w, https://www.awordpresscommenter.com/wp-content/uploads/2023/11/performance-chat-summary-7-november-2023-1536x868.png 1536w" sizes="(max-width: 1586px) 100vw, 1586px" /></div><div>
<p><a href="https://make.wordpress.org/core/2023/11/07/performance-chat-agenda-07-november-2023/">Meeting agenda here</a> and the full chat log is available <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1699372876051099">beginning here on Slack</a>.</p>
<h2 class="wp-block-heading">Announcements</h2>
<ul>
<li>Welcome to our new members of <a href="http://wordpress.slack.com/messages/core-performance/">#core-performance</a></li>
<li>WordPress 6.4 release is <strong>today</strong></li>
</ul>
<h2 class="wp-block-heading" id="focus-group-updates">Priority Projects</h2>
<h3 class="wp-block-heading" id="images">Server Response Time</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-server-response-time">Link to roadmap projects</a> and link to the <a href="https://github.com/orgs/WordPress/projects/112/views/1">GitHub project board</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> <a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> <a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/pereirinha/" class="mention"><span class="mentions-prefix">@</span>pereirinha</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> working on <a href="https://core.trac.wordpress.org/ticket/59314">#59314</a> Research showed that there is very little benefit going ahead with <code>file_exists</code> caching and it’s not easy to cache <code>locate_block_template()</code>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I think we can probably close <a href="https://core.trac.wordpress.org/ticket/59314">#59314</a> as a <code>wontfix</code> as well, but was waiting to see what the results were of the research you were doing into replacing all of the file_exists checks in core with your PoC. Did you ever run any numbers for that?</li>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> ran into issues while doing it so stopped in between. Will try that again this week</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Sounds good. I think I’ll close that ticket regardless, and if you notice that it’s worth attempting to replace the native file_exists implementation then we can open a new ticket for that.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> also reviewing <a href="https://core.trac.wordpress.org/ticket/45601">#45601</a></li>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> For <a href="https://core.trac.wordpress.org/ticket/59315">#59315</a> I ran function benchmark, which indicated a ~3% performance improvement for the function. Given this result, we recommend closing this ticket with a <code>wontfix</code> resolution</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> Regarding i18n performance, still planning a blog post after 6.4 is out</li>
</ul>
<h3 class="wp-block-heading" id="images">Database Optimization</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-database-optimization">Link to roadmap projects</a> and link to the <a href="https://github.com/orgs/WordPress/projects/119/views/1">GitHub project board</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> for <a href="https://core.trac.wordpress.org/ticket/56912">#56912</a> we are waiting for <a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> feedback
<ul>
<li><a href="https://profiles.wordpress.org/spacedmonkey/" class="mention"><span class="mentions-prefix">@</span>spacedmonkey</a> suggest to keep it open and punt to a future release</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I’m not sure about the <code>site_icon</code> option. I reviewed that when I looked at the ticket recently, and it’s autoloaded as far as I can tell. That’s why I am thinking there is no outstanding work to do</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> This was already ready during 6.4, I feel this is ready to be merged for 6.5 given a second review.<br /> <a href="https://github.com/WordPress/wordpress-develop/pull/5295" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/wordpress-develop/pull/5295</a> It’s a small bug fix
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I can give it a fresh look and commit it if it looks good to go</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading" id="object-caching">JavaScript &#038; CSS</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-javascript-css">Link to roadmap project</a> and link to the <a href="https://github.com/orgs/WordPress/projects/114/views/1">GitHub project board</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> <a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> The project board still has this leftover effort for async/defer, which includes <a href="https://core.trac.wordpress.org/ticket/59301">#59301</a>. I assume that’s not something actively being worked on?
<ul>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> correct, not a priority</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading" id="measurement">Images</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-images">Link to roadmap projects</a> and link to the <a href="https://github.com/orgs/WordPress/projects/116/views/1">GitHub project board</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> <a href="https://profiles.wordpress.org/thekt12/" class="mention"><span class="mentions-prefix">@</span>thekt12</a> <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> <a href="https://profiles.wordpress.org/pereirinha/" class="mention"><span class="mentions-prefix">@</span>pereirinha</a> <a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> For Image Loading Optimization (<a href="https://github.com/WordPress/performance/issues/869" target="_blank" rel="noreferrer noopener">overview issue</a>), the initial <a href="https://github.com/WordPress/performance/pull/876" target="_blank" rel="noreferrer noopener">pull request</a> for LCP and lazy-loading detection (i.e. page metrics) has been merged into the feature branch (<code>feature/image-loading-optimization</code>). I’m working on the next <a href="https://github.com/WordPress/performance/pull/878" target="_blank" rel="noreferrer noopener">pull request</a> for page metrics storage which I hope to have ready for review by EOD today. With detection and storage in place, I’ll move on to applying them to actually apply the optimizations on pages.
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> One question I had about 878 is why you decided to register a separate post type for the storage, rather than post meta? Just curious, really.</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> Good question. The reason is that URLs needing to be optimized are more than just singular posts, where postmeta is not available. It’s similar to oEmbed Caches in core, where we have a custom post type for that as well</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> On a separate topic, I’ve started some initial research into ways we might be able to improve the accuracy of the algorithm we use to determine the <code>sizes</code> attribute that core adds to images. This could be an important optimization if we can be more accurate and potentially avoid serving larger than necessary images to site visitors.</li>
<li><a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a> On the previous topic…which relates to this, the detection logic is capturing the bounding rect for each image in the viewport, so this could feed into the <code>sizes</code> calculation.
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Oh sure…if we could do front-end calculation of the image dimensions, the sizes attribute could be much more accurate.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> Added Backgrounds to images got a plug by Kevin Powell <a href="https://www.youtube.com/watch?v=345V2MU3E_w&#038;ab_channel=KevinPowell" target="_blank" rel="noreferrer noopener">https://www.youtube.com/watch?v=345V2MU3E_w&#038;ab_channel=KevinPowell</a></li>
</ul>
<h3 class="wp-block-heading" id="javascript">Measurement</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-measurement">Link to roadmap projects</a> and link to the <a href="https://github.com/orgs/WordPress/projects/120">GitHub project board</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> <a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> My intro blog post about performance testing should be ready soon, just needs some final polish</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> <a href="https://github.com/WordPress/wordpress-develop/pull/5624" target="_blank" rel="noreferrer noopener">Opened a PR</a> to expand core performance tests to cover localized sites, wp-admin, and memory usage</li>
<li><a href="https://profiles.wordpress.org/adamsilverstein/" class="mention"><span class="mentions-prefix">@</span>adamsilverstein</a> One small update from Drupal land where they have been working on a similar effort to add automated performance testing… They recently landed their first test collection piece in core with data going to Grafana – <a href="https://www.drupal.org/project/drupal/issues/3391689" target="_blank" rel="noreferrer noopener">https://www.drupal.org/project/drupal/issues/3391689</a></li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I am looking at metrics (mostly field) a lot these days, for visibility I am resharing the TTFB impact analysis I conducted: <a href="https://wordpress.slack.com/archives/C02KGN5K076/p1698947714789279" target="_blank" rel="noreferrer noopener">https://wordpress.slack.com/archives/C02KGN5K076/p1698947714789279</a><br />It begs the question how much WordPress core is in a position to affect TTFB in the field, vs how much TTFB is impacted by other factors outside of our control (e.g. hosting stack, network connection etc.)</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> I’ve spent a lot of time over the past week getting into the weeds of how we’ve been benchmarking WP versions, in preparation for the 6.4 release. It’s been a helpful exploration and we’ve made improvements to the <a href="https://github.com/swissspidy/compare-wp-performance" target="_blank" rel="noreferrer noopener">https://github.com/swissspidy/compare-wp-performance</a> workflow and added the ability to add variance statistics to the benchmarks taken by our benchmark CLI tools. I’ll write up some more details and add them to the conversation in <a href="https://github.com/WordPress/performance/issues/849" target="_blank" rel="noreferrer noopener">https://github.com/WordPress/performance/issues/849</a></li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I am also researching a couple other things related to our team’s potential impact on CWV through LCP, e.g. given we have mostly spent time on improving LCP, how much would that allow us to improve <em>overall</em> CWV passing rate of WordPress sites? And the same for TTFB (which, spoiler alert, seems to be a major bottleneck for TTFB)
<ul>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> I am going to prepare some of those stats to be a bit more presentable, but from what I am seeing so far, it seems that improving TTFB by let’s say 40% (which obviously is a very ambitious goal) would improve the actual LCP passing rate from the current ~40% to ~60%, which would be huge. Note that ~60% is also the current LCP passing rate of all <em>non-WordPress</em> sites in the HTTP Archive / CrUX dataset. So is TTFB our main issue in WordPress?</li>
<li><a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> It would certainly make sense, since TTFB is the metric with the lowest passing rate for WordPress sites. So this probably isn’t even news, but I think it’s a good other angle to look at the situation from. Improving TTFB would have major impact on LCP, and that would then have major impact on CWV. But easier said than done</li>
</ul>
</li>
</ul>
<h3 class="wp-block-heading">Ecosystem Tools</h3>
<p><a href="https://make.wordpress.org/performance/roadmap-2023/#category-ecosystem-tools">Link to roadmap projects</a> and link to the <a href="https://github.com/WordPress/plugin-check">GitHub repo</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> <a href="https://profiles.wordpress.org/westonruter/" class="mention"><span class="mentions-prefix">@</span>westonruter</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> for the Plugin Checker
<ul>
<li><a href="https://github.com/WordPress/plugin-check/issues/251" target="_blank" rel="noreferrer noopener">Add link to Plugin Editor for each found issue to jump user to file and line of code</a> – Merged </li>
<li><a href="https://github.com/WordPress/plugin-check/pull/319" target="_blank" rel="noreferrer noopener">Improve behaviour for single-file plugins</a> – Ready for review </li>
<li><a href="https://github.com/WordPress/plugin-check/pull/320" target="_blank" rel="noreferrer noopener">Add missing @since annotation</a> – Ready for review</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/swissspidy/" class="mention"><span class="mentions-prefix">@</span>swissspidy</a> Regarding Plugin Check, I <a href="https://github.com/WordPress/plugin-check/pull/318" target="_blank" rel="noreferrer noopener">added support</a> for a new <code>--exclude-checks</code> CLI option, which is now already available via the <a href="https://github.com/marketplace/actions/wp-plugin-check" target="_blank" rel="noreferrer noopener">Plugin Check GitHub Action</a> as well.</li>
</ul>
<h3 class="wp-block-heading" id="infrastructure">Creating Standalone Plugins</h3>
<p><a href="https://github.com/WordPress/performance/issues/656">Link to GitHub overview issue</a></p>
<p>Contributors: <a href="https://profiles.wordpress.org/flixos90/" class="mention"><span class="mentions-prefix">@</span>flixos90</a> <a href="https://profiles.wordpress.org/mukesh27/" class="mention"><span class="mentions-prefix">@</span>mukesh27</a> <a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a></p>
<ul>
<li><a href="https://profiles.wordpress.org/10upsimon/" class="mention"><span class="mentions-prefix">@</span>10upsimon</a> I am <a href="https://github.com/WordPress/performance/pull/864/" target="_blank" rel="noreferrer noopener">iterating on the PR</a> to have it ready for re-review by end of the week</li>
</ul>
<h1 class="wp-block-heading">Open Floor</h1>
<ul>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> I was on a client site last week and noticed that there was a load of get_options calls to missing options each taking 0.002. I wonder if we could work out a way to return early
<ul>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> Do these not get picked up by the not_options cache? Or did that not apply in this case?</li>
<li><a href="https://profiles.wordpress.org/pbearne/" class="mention"><span class="mentions-prefix">@</span>pbearne</a> didn’t seem to be so, filled up the queries</li>
<li><a href="https://profiles.wordpress.org/joemcgill/" class="mention"><span class="mentions-prefix">@</span>joemcgill</a> <code>get_option</code> should add any not found option to the cache <a href="https://github.com/WordPress/wordpress-develop/blob/6.3/src/wp-includes/option.php#L210" target="_blank" rel="noreferrer noopener">here</a>, unless there is a bug that causes it to get skipped. If the site isn’t using a persistent object cache and it’s only called once, then that optimization won’t really matter, but otherwise it should.</li>
</ul>
</li>
<li><a href="https://profiles.wordpress.org/dmsnell/" class="mention"><span class="mentions-prefix">@</span>dmsnell</a> I started working with someone to work on running the Gutenberg E2E suite against the Playground with Core’s <code>trunk</code>. My schedule was a bit off because of a meetup we had a couple weeks ago and a small vacation I took afterwards.</li>
</ul>
<p><strong>Our next chat will be held on <a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231114T1600"><abbr class="date" title="2023-11-14T16:00:00+00:00">Tuesday, November 14, 2023 at 16:00 UTC</abbr></a> in the <a href="https://wordpress.slack.com/messages/core-performance/">#core-performance channel</a> in <a href="https://make.wordpress.org/chat/">Slack</a>.</strong></p>
<p class="o2-appended-tags"><a href="https://make.wordpress.org/core/tag/core-performance/" class="tag"><span class="tag-prefix">#</span>core-performance</a>, <a href="https://make.wordpress.org/core/tag/performance/" class="tag"><span class="tag-prefix">#</span>performance</a>, <a href="https://make.wordpress.org/core/tag/performance-chat/" class="tag"><span class="tag-prefix">#</span>performance-chat</a>, <a href="https://make.wordpress.org/core/tag/summary/" class="tag"><span class="tag-prefix">#</span>summary</a></p>
</div>

WordPress is moving closer to Google Docs-style collaborative editing. In an update on Phase 3…
The WordPress Foundation’s bid to trademark “Managed WordPress” and “Hosted WordPress” in the United States…
WordPress 6.9 Beta 3 is available for download and testing! This beta version of the…
WordPress co-founder Matt Mullenweg will deliver this year’s State of the Word in San Francisco…
Automattic has teamed up with the Internet Archive to launch a new plugin designed to…
The WordPress Plugins Team is now automatically scanning every plugin update on WordPress.org for security,…