Preload by Agence Web Performance

Preload #02 ·

CrUX finally sees SPAs, UpdraftPlus and Rank Math hacked

Chrome is done with unload, Next.js needs patching, and Webflow and Git are called into question.

Preload just passed 100 subscribers, which is a lovely surprise for a second issue: thank you, every one of you. Two threads cross this week. Tools we took for granted are becoming choices again: Anthropic replaced Git on its monorepo, Bootstrap built its own tool on top of GitHub, and Webflow's MCP server turns out to be a way out of Webflow. And the supply chain is still the way in: a plugin poisoned at the source, stolen remote management keys, while GitHub finally lets you lock the actions in your workflows.

Enjoy the read, and happy patching.

The essentials

  • UpdraftPlus: remove UpdraftCentral keys from your sites, backdoors have been installed since October 18.
  • Next.js 16.4.1 and 15.5.28 fix two critical remote code execution flaws: update now.
  • CrUX now measures soft navigations in single-page apps, ahead of a planned Search Console switch in May 2027.

Web platform

Chrome no longer runs unload handlers at all

What Edge shipped last week is now done in Chrome too: since version 155, unload handlers no longer run on any page load, wrapping up a gradual rollout that began in March 2025. Only the unload Permissions-Policy and an enterprise policy remain as escape hatches, and Chromium is about to make this the default for every browser built on it. Google says unload usage dropped from 18% to under 4% of navigations, and about 5% more navigations are now eligible for the back/forward cache.

Next step

Hunt down any remaining unload listeners, third-party scripts included, and move them to pagehide or visibilitychange. Remove any Permissions-Policy: unload=(self) header, which brings the listener back and excludes the page from the cache again. Firefox still drops pages that listen for unload, so the cleanup pays off there too.

Read the source

Topics:PerformanceChrome

:buffering, :playing, :paused: Chrome plans media pseudo-classes for version 158

Safari since 15.4 and Firefox since 150 let you style a <video> or <audio> element by its state: :playing, :paused, :seeking, :buffering, :stalled, :muted and :volume-locked. Chrome has published its intent to ship them and targets version 158, due in stable on November 17, with Edge to follow. If the schedule holds, the group will then become Baseline.

Partial support: Safari 15.4, Firefox 150, Chrome 158 planned

Next step

Show a video player's loading indicator with video:buffering instead of JavaScript waiting and playing listeners, and keep the script as a fallback for Chrome until 158.

Less JavaScript for a state the browser already knows. You can ship this as a progressive enhancement today, without waiting for Chrome.

Read the source

Topics:CSSChromeFirefoxSafari

Performance

CrUX finally measures soft navigations in single-page apps

Starting with the September dataset, released on October 13, CrUX adds three experimental variants of LCP, INP and CLS that count each route change in a single-page app as a navigation. They are available in BigQuery, the API, the History API and CrUX Vis, with FCP coming in November. Google aims to take them out of experimental status in May 2027, at which point Search Console would switch to this data. Across all origins, the share of good LCP goes from 68.3% to 72.1%.

Next step

On a single-page app, track both series side by side and note which dashboards and alerts only read the stable one. On a multi-page site, such as WordPress or PrestaShop without a decoupled front end, nothing changes.

A gap between the two series mostly reflects a change in what is measured, not a faster site: follow-up views reuse code that is already loaded. The JavaScript that runs on every route change still weighs on INP.

Read the source

Topics:Field dataPerformanceINPLCP

WebPerf Snippets: from console copy-paste to a complete toolkit

Joan León's diagnostic scripts, which you used to paste one by one into the console, became a toolkit with structured results in a single week (versions 2.0 and 2.0.1, October 13 to 15). A beta DevTools extension gathers them in a panel, even when the CSP blocks pasting, and CLI 1.0 also audits logged-in pages and compares them against CrUX data. In CI, a GitHub Action fails the build when a page goes over the performance budget you set. The same scripts are also packaged for AI agents, so they can run these diagnostics themselves.

Next step

Install the extension for live diagnosis and the GitHub Action to catch regressions, but always start from field data (CrUX, RUM) to decide what to fix.

An effective but clunky tool becomes easy to use, which means measuring more often.

Read the source

Topics:Developer toolsPerformanceINP

CMS

GenerateBlocks grows into a full site builder for WordPress

With GenerateBlocks 2.5, released October 13, and GenerateBlocks Pro 2.8, GeneratePress's block plugin gets redesigned dashboards and a reworked Styles Builder, built around the Pro version's Design Tokens, Global Styles and Design Systems. The shift caps eighteen months of additions that each replace a third-party plugin: overlay panels, display conditions, forms, editor access control.

Under the hood, 2.5 now always inlines the page's block CSS and removes the setting that let you serve it as a file.

Next step

Set up tokens and global styles first, then use local styles for the exceptions. After updating, check how much inline CSS your heaviest templates now carry.

This is how Unblock, the competing editor released in beta this spring, already works: selectors, queries and variables saved once for the whole site, then reused everywhere. We think it's the right approach: each value changes in one place only, shared styles live in a shared stylesheet instead of being repeated block by block, and GenerateBlocks gets there by building on its existing behavior, with nothing for existing sites to relearn.

Read the source

Topics:CSSWordPress

Webflow's MCP server, a way out of the ecosystem

Webflow's MCP server lets an AI agent, with the user's permissions, read and write elements, styles and classes, components, variables, pages and SEO settings, CMS collections and items, assets and forms. On October 15 it gained read access to Analyze, Optimize and AEO Analytics data. Webflow pitches it as a building tool; some users report using it the other way round, to inventory a site and rebuild it elsewhere.

Next step

Before moving a site off Webflow, have an agent inventory the page structure, styles and CMS collections, then rebuild the dynamic parts on the new platform. The official export only gives you the CMS as data and leaves forms broken.

With no complete export, the tool designed for building in Webflow becomes the most serious way out of it. For a client who wants to stay in control of their site, it's one more point in favor of reversibility.

Read the source

Topics:AIMCP

Shop MCP: Shopify opens its catalog and Shop Pay to any agent

Since October 13, the mcp.shop.com MCP server lets an AI agent search over a billion products in the Shopify catalog, build a cart and pay with Shop Pay, using the UCP protocol. Search needs no key; a purchase only goes through once the buyer confirms the total and payment method. Orders land in the store's admin like any other, and there are no webhooks yet.

Next step

If you're building a shopping agent, start from this server rather than store-by-store integrations. On the merchant side, make product pages, variants and attributes complete: that's all the agent will read from your store.

A huge opportunity for the platform's merchants: their products become buyable from any agent, with no integration to build, nothing to sign up for, and no announced extra cost. The only work required is the same work that already helps search: complete, accurate product pages.

Read the source

Topics:AIMCP

Languages and frameworks

Next.js 16.4.1 and 15.5.28 fix two remote code execution flaws

The update announced for October 14 is out. It fixes an unauthenticated remote code execution when a use cache function returns several typed arrays (App Router with Cache Components), with no workaround, and another in SVG image optimization on Linux glibc. A third, high-severity flaw lets attackers max out the CPU through Server Actions; the Pages Router is not affected.

Next step

Upgrade to 16.4.1 or 15.5.28 right away, starting with apps that use Cache Components. If you can't upgrade today, at least bump sharp to 0.35.5 to close the image flaw.

Read the source

Topics:Security

Node.js: security releases on October 21, Node 26 goes LTS on the 28th

The 26.x, 24.x and 22.x lines get security fixes on Wednesday, October 21, with a highest severity of high; details will be published with the releases. The schedule moves at the same time: Node 24 enters maintenance on October 20 and Node 26 becomes Active LTS on the 28th, while Node 22 stays supported until April 30, 2027.

Next step

Book a slot on October 21 to update servers, Docker images and CI, then plan the move to Node 26 for projects still on 22.

Read the source

Topics:JavaScriptSecurity

AI and dev tools

Anthropic replaced Git on its monorepo, and advises you not to

At Anthropic, daily merges went from about 2,500 in May to more than 30,000 in September, according to the company, driven by coding agents. Git couldn't keep up on a monorepo with nearly 100 GB of history: seven people replaced it in five months with Scion, an unreleased in-house system built on server-side changesets and partial working copies.

The post makes clear that Scion is no replacement for Git in general use, and that the team hopes to bring some of its ideas into Git. Not to be confused with Google Cloud's Scion project.

Next step

If a tool in your stack can't keep up with how you work, measure where it breaks before working around it, then ask the question plainly: keep it, extend it or replace it. With AI, building a custom tool is no longer reserved for very large teams.

Git is still the right choice for nearly every project, and Anthropic is the first to say so. The real lesson is elsewhere: when volumes jump by an order of magnitude, tools we took for granted become choices again.

Read the source

Topics:AIDeveloper tools

Bootstrap triages its backlog with agents, but keeps the decisions

Two active maintainers, and more than 500 open issues and PRs a few months ago: for Bootstrap, Julien Déramond built a triage tool, twbs/triage, with Claude Code. It reads the repository without writing to it, analyzes each item (thread, related work, v5 and v6 branches, reproduction), drafts a reply, prepares fix branches and scores how easy each one is. The first pass over more than 200 items added 410 labels and got a contributor PR, forgotten since July, merged; about 230 items remain open. Every decision and every post stays human.

Next step

If you hand triage to an agent, borrow its guardrails: treat external content as data, never as instructions; never run contributor code; never open links from issues; allow no write access beyond a closed list of labels.

This is the flip side of Anthropic replacing Git: when the tool holds up but a working view is missing, you add to it rather than replace it. This is issue triage, not version control.

Read the source

Topics:AIDeveloper tools

GitHub Actions finally locks your actions in a lockfile

In public preview since October 14, a .github/workflows/actions.lock file pins every action you use to an exact commit, including the actions it calls, along with reusable workflows. The gh actions-lock extension generates it, and a “Require lockfile” policy can enforce it on the Free, Team and Enterprise Cloud plans.

Next step

Generate the file in repositories that deploy and turn on the policy: a compromised upstream action can no longer slip in without a visible lockfile change in a PR.

This week shows it twice: the supply chain is the way in. We used to pin SHAs by hand; the lockfile finally makes that good practice sustainable.

Read the source

Topics:Developer toolsSecurity

Security

UpdraftPlus: stolen UpdraftCentral keys used to install backdoors

Since October 18, an attacker holding valid UpdraftCentral keys has been sending signed commands to WordPress sites and installing a backdoor plugin. It creates an account that shows up as an Editor but can install plugins, and logs in through a cookie, bypassing the login form and two-factor authentication. Every version of UpdraftPlus is affected, free and premium; as of October 19, the vendor had published neither a fix nor an explanation.

A box checked by default when connecting a TeamUpdraft account creates a key: a site can be exposed without ever having used UpdraftCentral.

Next step

Run wp option get updraft_central_localkeys: any output means the site is exposed. Delete the keys (wp option delete updraft_central_localkeys) and don't reconnect until the vendor explains what happened. Then look for an unknown plugin described as “Small maintenance toolkit”, an option ending in _sync_token and an Editor who can install plugins. At the slightest trace, treat the site as compromised.

Read the source

Topics:SecurityWordPress

Rank Math SEO PRO 3.0.123: poisoned copies for eleven hours

Copies of Rank Math SEO PRO 3.0.123 downloaded or installed between October 15 at 20:02 and October 16 at 07:12 (UTC) contained malware (CVE-2026-111862, CVSS score 9.8). Version 3.0.124 is clean. A poisoned copy that was activated leaves the site compromised, and updating doesn't clean it.

Next step

If 3.0.123 was activated on a site during that window, restore a backup from before October 15 at 20:02 UTC and rotate every secret (passwords, database, salts, API keys, SSH). Otherwise, update to 3.0.124 and still check for wpsupport_* accounts and a wp-includes/class-wp-cache-util.php file.

Read the source

Topics:SecuritySEOWordPress

Finds

Page Parkour

Hakim El Hattab follows up on Page Commando: this time the page becomes a 3D city you run through as a ninja. Only text blocks, media and visible containers (background, border, shadow, image) turn into volumes, each sitting on its container's base, so the stacking shows how visible boxes are nested, not the raw DOM depth. No dependencies: CSS 3D transforms, 2D canvas, WebGL for the sky only, and Web Audio.

Next step

Run it on your templates to spot stacked boxes at a glance, as a bookmarklet or an unpacked Chrome extension (the bookmarklet is blocked by GitHub's and X's CSP). For actual DOM size, Lighthouse remains the reference.

Read the source

Topics:CSSJavaScript

Eroan Boyer
Founder of Agence Web Performance

The next issue, Tuesday morning.

Get Preload every week, two weeks before it goes public. Free, one-click unsubscribe.

All issues