Facebook Instant Articles no longer exists, so there is nothing left to set up. If you came here to make your articles load fast for people arriving from a phone, install a caching plugin and get your pages inside Google’s three Core Web Vitals thresholds:
Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, Cumulative Layout Shift under 0.1. That gets you the speed Instant Articles used to provide, on your own domain, in every app and browser rather than one.
The rest of this page covers how to hit those numbers on WordPress, and what happened to the old format.
What happened to Instant Articles
Meta stopped supporting Instant Articles in mid-April 2023. The reason it gave was straightforward commercial arithmetic: news article links make up less than 3% of what people see in the Facebook Feed, and the audience prefers video. A Meta spokesperson put it as “as a business it doesn’t make sense to over invest in areas that don’t align with user preferences”.
The official
Instant Articles for WP plugin was closed in the WordPress plugin directory on 18 April 2023, days after support ended. The closure notice is permanent. If you still have it installed on an old site, deactivate and delete it; it cannot receive security updates.
Why this is better news than it sounds
Instant Articles was fast because it stripped your page down and served it from Facebook’s own infrastructure. The trade was real: readers never reached your site, your analytics saw less, your ad stack was replaced by theirs, and the whole thing worked in exactly one app.
The speed part is now something you can do yourself, and it counts everywhere. A well-cached WordPress article served over a decent host loads in well under a second for most readers, keeps your own advertising and email capture, and earns the page experience signals Google uses in search.
The three numbers to hit
Core Web Vitals are measured at the 75th percentile of real page loads, split between mobile and desktop, which means three-quarters of your visits have to be good, not your one lucky test run.
- Largest Contentful Paint (LCP): 2.5 seconds or less. How long until the biggest thing on screen, usually your featured image or headline, has actually rendered.
- Interaction to Next Paint (INP): 200 milliseconds or less. How quickly the page responds when someone taps something. INP became a stable Core Web Vital in 2024, taking over from First Input Delay, so any speed guide still built around FID is measuring a metric Google has retired.
- Cumulative Layout Shift (CLS): 0.1 or less. How much the layout jumps around while loading. Late-loading ads and images without width and height attributes are the usual culprits.
Those thresholds come from
Google’s own Web Vitals documentation. Check your site against real visitor data in the Core Web Vitals report in Search Console rather than a single lab test.
Step 1: page caching
This is the change that moves LCP more than anything else you can do in an afternoon. Without caching, every visitor makes WordPress rebuild the page from the database. With it, most visitors get a finished HTML file.
LiteSpeed Cache is the one to reach for if your host runs LiteSpeed or OpenLiteSpeed, which many shared and managed hosts now do. It has more than 7 million active installations, holds 4.8 out of 5 across 2,769 reviews, and is tested against WordPress 7.1. Full page caching talks directly to the server’s built-in LSCache, so it is quicker than anything PHP can do. On Apache or NGINX you still get the image optimisation, minification, lazy loading and database cleanup, and you can route caching through its QUIC.cloud CDN instead.
WP Super Cache is the host-agnostic choice. It is maintained by Automattic, has over a million active installations, sits at 4.3 out of 5 from 1,345 reviews, and is tested against WordPress 7.1. It offers three modes: Expert mode uses Apache mod_rewrite to serve static HTML and bypass PHP entirely, Simple mode lets PHP serve the cached file and needs no .htaccess changes, and WP-Cache handles logged-in users and URLs with query strings.
Start with Simple mode. It is nearly as quick as Expert mode and far harder to break. If you want the paid options weighed against the free ones,
our cache plugin comparison goes through them, and
WP Rocket versus W3 Total Cache covers the two most argued-about names.
Step 2: your images
On an article page the largest contentful element is almost always the featured image, so LCP is usually an image problem wearing a performance costume.
Serve it in WebP or AVIF, size it to the width it actually displays at rather than uploading a 4,000-pixel original, and always set width and height so the browser reserves the space and CLS stays flat.
Our image optimiser comparison covers which plugins convert and compress without wrecking quality.
One thing to get right: do not lazy-load the featured image. Lazy loading below-the-fold images is good practice and helps mobile enormously, but lazy-loading the hero image delays the very thing LCP measures.
Our lazy loading guide explains when you still need a plugin at all, given WordPress now does most of this natively.
Step 3: cut the JavaScript
INP is almost entirely about JavaScript. Every analytics tag, chat widget, social embed, related-posts carousel and consent banner competes for the same main thread, and on a mid-range Android phone that thread is busy.
Audit what actually loads on an article template. Remove the widgets nobody clicks. Defer what you keep. Replace embedded video players with a click-to-load thumbnail. If your theme loads a page builder’s full asset bundle on posts that contain no builder content, that is usually a setting rather than a rewrite.
Step 4: the host underneath it all
Caching hides a slow server from repeat visitors but not from the first one, and not from anything that cannot be cached. If your time to first byte is poor on an uncached request, no plugin fixes that. A host on current PHP with a local object cache and a CDN in front will beat a tuned plugin stack on cheap shared hosting every time.
Reaching Facebook readers now
Without Instant Articles, a post shared to Facebook is an ordinary link that opens in the in-app browser or the reader’s default browser. So the thing that determines how it feels is the same thing that determines how it feels in Google: your own page speed.
What is worth spending time on is the preview. Set a clear Open Graph title, description and image for each article so the link renders properly in the feed, and check that your featured images are the right shape for the card. That, plus a page that loads quickly, is the whole job now.
The short version
Instant Articles is gone and its plugin is closed. Cache your pages, fix your featured images, cut the scripts you do not need, and hold LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. You end up with what Instant Articles promised, without handing your readers to somebody else’s app.
