AMP for WordPress, speed and Core Web Vitals

#What Are AMP (Accelerated Mobile Pages)?

AMP (Accelerated Mobile Pages) is an open-source HTML framework developed by Google and the AMP Open Source Project to create fast-loading web pages for mobile devices. Launched in 2015, AMP was designed to address the growing need for faster mobile web experiences, especially in regions with limited internet connectivity.

The core principle behind AMP is simple: strip down web pages to their essential content and eliminate elements that slow down loading times. This is achieved through a combination of simplified HTML, restricted JavaScript usage, and the AMP Cache system that serves content from Google’s servers.

#Where AMP actually stands in 2026

A reality check before we go further: AMP is not a 2026 best practice. It is a 2015-era framework that Google demoted in 2021 when the Top Stories carousel stopped requiring it. Mobile-first indexing did not save AMP, because AMP was never the only way to be fast on mobile, and Core Web Vitals replaced it as the metric Google actually cares about.

What AMP does well, technically, has not changed. Strict CSS limits, no arbitrary JavaScript, and prefetching from Google’s CDN produce sub-1-second LCP almost by default, low CLS because layout rules are enforced, and predictable INP because there is no third-party script chaos. If you are working with a small team and need a mobile variant that is hard to make slow, AMP still delivers on that narrow promise.

What AMP does not do anymore is buy you preferential search treatment. The AMP badge is gone in most markets. Top Stories ranks canonical URLs with good Core Web Vitals just as readily as AMP URLs. The crawl-efficiency argument matters only at very large scale. So if you are considering AMP for the SEO upside specifically, that upside is mostly historical at this point.

#How AMP Works

#AMP HTML

AMP uses a specialized version of HTML with custom tags and restrictions:

• All CSS must be inlined and limited to 75KB
• JavaScript is restricted to AMP-approved components
• Images and videos use lazy loading by default
• Third-party scripts are sandboxed to prevent blocking

#AMP Cache

Google’s AMP Cache stores AMP pages and serves them directly from Google’s infrastructure, providing:

• Pre-validation of AMP pages
• Compression and optimization
• Global CDN distribution
• Near-instantaneous delivery

#AMP JavaScript

The AMP JS library implements best performance practices:

• Asynchronous loading of all resources
• Pre-calculation of layout before loading
• Sandboxed iframes for third-party content
• Built-in analytics support

#The WordPress AMP plugin landscape in 2026

Before touching anything, look at what is actually still maintained.

The official AMP plugin (amp on WordPress.org, formerly “AMP for WordPress”) is the only one I would still install on a new project. It is the plugin Google and Automattic backed, and it still ships updates against current WordPress and PHP versions. Three modes: Standard (the whole site is AMP), Transitional (AMP and canonical coexist), Reader (legacy templates, mostly relevant for old blogs you do not want to rebuild). Standard mode is the cleanest, but it will surface every theme incompatibility you have. Most paid themes from 2018-2020 break Standard mode in ways that take a day to fix.

AMP for WP, Accelerated Mobile Pages by Ahmed Kaludi and Mohammed Kaludi is the other plugin most clients arrive with. It is more permissive about ads, page builders, and WooCommerce, which is why agencies pushed it. Update cadence has slowed, GitHub issues sit open for months, and the WooCommerce add-ons broke in several WC 8.x releases. Functional, but I now treat it as legacy code I am migrating off, not a fresh choice.

Penci AMP, Schema AMP and the long tail of theme-bundled AMP plugins are mostly abandoned. If a client is on one of these, the migration question is not “if” but “when”.

Whichever plugin you are on, the setup that actually matters is small: pick Standard or Transitional, run the AMP validator from Search Console (while it still exists), wire amp-analytics to your existing GA4 property, and audit which canonical-page features silently disappear on the AMP variant. The plugin’s UI will not warn you when it strips your contact form’s reCAPTCHA or your booking widget’s JavaScript.

#What actually breaks in production

The AMP failure modes I keep seeing on real client sites, not the theoretical ones from the docs:

Validation errors after a plugin update. A perfectly valid AMP variant breaks the morning after someone activates a popup plugin, a chat widget, or a new analytics snippet. The non-AMP analytics tag injects inline JavaScript, and AMP rejects the whole page. The fix is removing the offending plugin’s frontend output from the AMP variant via the official plugin’s “Plugin Suppression” panel, but every new plugin reopens the question.

The 75 KB inline CSS limit. AMP requires all CSS inlined into a single <style amp-custom> block under 75 KB. Modern WordPress themes built around block patterns, large utility frameworks, or builder-generated styles routinely produce 120-200 KB. The fixes are real work: stripping unused selectors per template, splitting global styles from page-specific ones, sometimes building a separate stylesheet just for AMP. Plugins like AMP for WP advertise auto-stripping; results are uneven.

Third-party scripts that simply cannot run. AMP forbids arbitrary JavaScript. That means no Intercom, no HubSpot tracking pixel, no custom Stripe Elements integration, no booking calendar that depends on its own JS. Vendors offer amp-iframe workarounds; many do not. On WooCommerce stores I have audited, the AMP cart and checkout broke quietly because the payment gateway’s JS never loaded, so a percentage of mobile sessions ended on a page that looked fine but could not complete a purchase.

Google Ads and AdSense on AMP variants. AMP serves ads through amp-ad, which supports a subset of formats and a subset of targeting. Lazy-loaded ads, custom GAM line items, and any header bidding setup that relies on Prebid.js typically lose revenue on AMP pages versus their canonical equivalents. I have seen 20-40% RPM drops on AMP variants that publishers only noticed when they ran a side-by-side report.

Content drift between AMP and canonical. Editors update the canonical post; the AMP variant lags or strips an embedded video. Google’s content-parity rule means the AMP version eventually gets ignored or the canonical gets penalised in the AMP carousel. The official plugin handles this better than third-party ones because it generates AMP from the same source on request, but custom AMP templates almost always drift.

The honest fix for most of these is not fixing AMP. It is shipping fast HTML and CSS on the canonical site so AMP becomes redundant. A WordPress site that hits LCP under 2.0 s, CLS under 0.05, and INP under 200 ms with WP Rocket or LiteSpeed Cache, AVIF images, a CDN, and a theme that does not load five JS frameworks will outperform its own AMP variant on Core Web Vitals while keeping every feature intact.

#When AMP still makes sense, and when to walk away

The honest 2026 picture: AMP is a niche technology with a shrinking footprint. Google removed the AMP requirement for Top Stories in 2021. The Search Console “AMP” report still exists but reports a fraction of the volume it did in 2019. Major publishers including The New York Times, BBC News, The Washington Post and The Guardian have deprecated their AMP variants in stages between 2022 and 2025. Google’s AMP Cache stopped serving large parts of the open web. The cdn.ampproject.org URLs that used to dominate Top Stories traffic now rarely appear.

AMP still earns its place in three situations:

1. Legacy news publishers tied to AMP-only ad networks. A handful of regional news ad platforms still demand amp-ad integration. If your monetisation contract names AMP, you keep AMP until the contract changes.
2. Specific Google Discover dependencies. Discover does not require AMP, but a few publishers report measurable Discover gains on AMP variants for image-heavy lifestyle and recipe content. Worth A/B testing before committing.
3. Markets where 3G is still dominant. Parts of South-East Asia, sub-Saharan Africa and rural Latin America have median connection speeds where AMP’s prefetch-from-Google-Cache model still beats anything you can self-host. If your audience is largely on sub-1 Mbps connections, AMP is a real engineering option.

For everyone else, the math has flipped. I have done two recent migrations off AMP that are worth naming. A regional news publisher dropped AMP entirely in early 2025 after seeing AMP traffic shrink to single-digit percentages of organic mobile sessions. Twelve weeks post-removal, organic traffic was flat within noise and editorial throughput went up because the team stopped maintaining two versions of every article. A WooCommerce client running AMP for WP discovered their AMP cart was silently dropping mobile checkouts because the payment gateway’s JS could not load inside AMP; killing AMP on product and checkout templates recovered the conversions immediately.

If you are starting fresh, the work that pays off is unglamorous: a host that gives you HTTP/3 and decent TTFB, WP Rocket or LiteSpeed Cache configured properly, AVIF images served via a CDN, a theme that does not bundle five JavaScript libraries, and a discipline around Core Web Vitals (LCP under 2.0 s, CLS under 0.05, INP under 200 ms). That stack outperforms AMP on Core Web Vitals while keeping your forms, payments, custom analytics and design intact.

So the actual conversation I have with clients now: tell me which of the three niches above you are in. If none, we are not implementing AMP. We are removing it cleanly, redirecting AMP URLs to canonicals, and putting the hours into the canonical site instead.

If you want a second opinion on whether AMP is helping or hurting your WordPress site, get in touch with the URL and I will look.

#Related Resources

• WordPress Performance Optimization
• Core Web Vitals Guide
• Mobile SEO Best Practices
• WordPress Speed Optimization Services