Nonce Experiment

This experiment exists to validate how adame.io, WordPress, and the Web Speed proxy handle a public nonce-like value inside cacheable markup.

The page is intentionally permanent. It gives us a stable place to test proxy behavior without changing a production article, tool, or customer-facing conversion path.

What this validates

WordPress Origin tracing can identify the exact component that emits the nonce-like attribute.
The proxy can keep the cached HTML intact while blanking only the selected attribute value.
The proxy can fetch a fresh public value after page load and inject it back into the target attribute.
If injection fails, the configured warning flow can reload the page while bypassing cache.

The live control below is appended by the adame.io plugin so it behaves like real site output instead of static test markup.

Live nonce attribute fixture

This control renders a public, shared nonce-like attribute that rotates on a fixed five-minute bucket. It is intentionally not tied to a logged-in user, session, or cookie.

Only the nonce attribute value is expected to change between origin checks.