How to embed tweets in WordPress without slowing your site

Paste a snippet that already holds the tweets into a Custom HTML block. That is all it takes.

I’ve built a lot of tweet walls for WordPress sites, mostly for pricing and landing pages. The fix is always the same: load a self-contained snippet straight into the page, so it shows up fast and keeps the rest of the page fast too.

What happens when you paste a tweet link into WordPress?

WordPress turns the link into an official X embed through oEmbed, which loads X’s widget script and puts each tweet in its own iframe.

One tweet is fine. A testimonial section with eight or ten of them is a performance problem. The script has to load, every tweet becomes a separate frame, and the layout lurches as each widget is painted. Mobile visitors often see empty boxes before the tweets appear.

There is a search cost too. The text inside an iframe belongs to another site, so it doesn’t count as your page’s content. If customers praise a feature by name on X, that wording does nothing for your page.

What’s faster than the official embed?

Write the tweets into the page as plain HTML and use a small script only for the layout.

That is how the AddTweets embed tool works. You paste tweet links, pick a wall, slider or carousel, and copy one snippet. The snippet already holds each tweet’s text, author, date and photo, so nothing is fetched from X when someone visits. A script of about 4 KB arranges the cards.

If the script is blocked, visitors still see the tweets as a clean list of quotes with links. Nothing goes blank.

How do I add it in WordPress?

Use the Custom HTML block that ships with WordPress.

1. Build the wall in the embed tool and click Copy code.
2. In the WordPress editor, click the + button where the wall should go and search for “Custom HTML”.
3. Paste the code, use the block’s Preview tab to check it, then update the page.

If you still use the old classic editor, switch from the Visual tab to Text before pasting. The Visual tab won’t make your life any easier; it turns your code into plain text. Page builders such as Elementor or Divi have an HTML widget that takes the same snippet.

The full walkthrough, including what to do when a security plugin strips scripts, is in the WordPress embed guide.

Should I use a plugin instead?

Only if you need the wall to update itself, and check what the plugin loads first.

Most tweet plugins render the official embed under the hood, so you get the same scripts with a settings page on top. Some fetch tweets live on every page view through an API, which can break when that API changes. A static snippet avoids both. The trade-off is that new tweets won’t appear until you update the code yourself.

How many tweets should a wall have?

Eight to twelve is a good range.

More than that and you’ve probably lost the reader anyway. Pick tweets that name a specific result or feature, put the strongest one at the top and work down from there.

What do I do when someone deletes a tweet?

Reopen the saved wall, let it drop the deleted tweet, and paste the fresh code.

Because the text lives in your page, a deleted tweet stays visible until you update the snippet. If you save walls to your AddTweets account, opening one checks every tweet again and removes the ones that are gone.

Quick checklist

• Use a Custom HTML block, not a pasted tweet link.
• Keep the wall clean: eight to twelve tweets.
• Put it near the decision, such as your pricing page.
• Check it on your phone after publishing.
• Revisit the wall regularly: add new praise, retire old tweets and refresh the code.