WordPress 7.1 Mary Lou: What Matters for Speed and Search

WordPress 7.1 “Mary Lou” was released on 19 August 2026, and the current release per the core version API is now 7.1.2. Most release write-ups run through every feature in order, which is useful once and then never again. The more practical question for anyone maintaining a site is narrower: which of these changes alter page weight, layout stability or the markup that reaches a crawler, and which are editor conveniences that change nothing downstream.

Three changes with a measurable performance effect

The first is image handling. The 7.1 release announcement states that image compression, resizing and thumbnail generation now happen in the browser, reducing server load and producing smaller files — without hitting PHP memory limits or upload timeouts. That moves a whole class of shared-hosting failure out of the stack, and it changes the size of what gets stored rather than only what gets served.

The second is format support. Core now natively supports AVIF, HEIC and HDR gain maps, described in the announcement as native support for the image formats modern cameras and phones already produce. For a site whose contributors upload straight from a phone, that removes a conversion step that used to be a plugin’s job.

The third is speculative loading. Its defaults can now be set through environment variables or constants, so hosts and site owners can configure how WordPress prefetches pages without writing a plugin. The significance is not the prefetching, which shipped earlier; it is that the aggressiveness of it is now an environment-level decision, so staging and production can behave differently without a code branch.

The editor changes that alter what reaches the page

The post editor is now fully iframed for all themes, matching the Site Editor. That is an editing-surface change rather than a front-end one, but it has a front-end consequence worth checking: styles and scripts that a theme or plugin previously injected into the editor document on the assumption it shared the page context need to be enqueued for the iframe instead. Where that has not been done, the symptom is an editor that no longer looks like the front end, which sends people hunting in the wrong place.

The new Tabs block is the release’s other markup change. Content organised into tabbed panels is content that is present in the document but not visible on load, which is fine for indexing and unhelpful for Largest Contentful Paint if the panel holds your hero image. Use it for genuinely secondary material rather than as a way to shorten a long page.

Responsive styling without custom CSS

Block themes can now define their own mobile and tablet breakpoints in theme.json, overriding the defaults for responsive styles. Anyone who has spent an afternoon fighting a theme’s fixed breakpoint with a stylesheet loaded after it will recognise what that saves. The search-relevant part is layout stability: the viewport widths at which a layout reflows are the widths at which reserved space either holds or does not, and getting them under deliberate control is the prerequisite for fixing mobile layout shift properly rather than patching it.

What developers got

The SVG Icon API is now public, with registration functions including wp_register_icon_collection(), wp_register_icon() and wp_get_icon(). It replaces the pattern of every plugin shipping its own inline SVG sprite, which on a page running half a dozen plugins was a measurable chunk of duplicated markup.

The Abilities API, introduced in 7.0, was extended in this release with a filterable execution lifecycle, custom validation and shared discovery. Other items in the release: opt-in GIF-to-video conversion that produces typically smaller files, and a Media Library that now uses infinite scrolling by default with a per-user option to return to pagination. For a fuller picture of how the block editor arrived here, the run of releases covered in what was new for site builders in 6.7 through 6.9 is the backstory, and the question of whether Gutenberg is ready looks different once theme.json carries breakpoints.

What to actually do this month

Update to 7.1.2 rather than 7.1, since two maintenance releases have already landed. Then run four checks. Open a post in the editor and confirm your theme’s editor styles still apply inside the iframe. Upload a photograph straight from a phone and confirm what format is stored and what is served. Decide the speculative loading setting for each environment deliberately instead of accepting the default everywhere. And re-measure a template you know is image-heavy, because the compression change alters stored file sizes for new uploads only — existing media is untouched, which is exactly where WordPress sites lose speed quietly. Dev notes for each change are published on the core development blog, which is the place to check before assuming a plugin conflict is a core regression.