Checkout takes 9 seconds before the first offer. Here’s where the time went.
On a client’s membership, a buyer waited 9 seconds between clicking pay and seeing the first upsell offer, and about 8 seconds to log in to the members site. No single fix covered it all.
The biggest single gain had nothing to do with plugins: the server’s code cache was full. After that, the wins came from letting the buyer move on before the follow-up work runs, and from finding two slow checks that ran on every page. Pay to first offer went from 9 seconds to 3.2.

What we measured
The client sells on one WordPress site, with WooCommerce and FunnelKit for checkout and one-click upsells, and teaches on a separate members site. WP Fusion connects both to FluentCRM. We timed test orders on the live sites, with a 100% coupon so the card payment isn’t included, before and after the changes.
Clicking pay to the first offer: 9 s to 3.2 s
On the main site, where the buyer pays.
“No thanks” to the next page: 2 to 4 s, now 0.6 s
Each offer the buyer turns down.
Thank-you page: 3.4 s to 1.6 s
The time before the server starts answering.
The smallest request the site answers: 0.87 s to 0.27 s
A good measure of the cost every page pays before it does any real work.
Logging in from the order email: about 8 s to 1.75 s
On the members site.
Members home page: 3.7 s to 0.8 s
On the members site.
Discussion pages, repeat views: 1.9 s to 0.85 s
On the members site.
The first real card order after the changes took 6 seconds from click to first offer, and about 5 of those were the card payment itself.
The biggest win had nothing to do with plugins
PHP, the language WordPress is written in, can keep its compiled code in memory so it doesn’t have to read every file again on every page. That memory is called OPcache. Here it was set to the usual 128 MB and was full, so most of the site’s code was compiled again on every page.
Giving it more room took about 0.6 seconds off every page on the site, the main site and the members site alike. It was the biggest single gain, and it’s a server setting, not a plugin. A membership site running many plugins can outgrow that default.
Ask your host or whoever runs your server how big the cache is and how full. If it’s full, it needs more room. That’s a change for them, not for a plugin.
Let the buyer through first
After the code cache, three things stood between pay and the first offer. Each was work that didn’t need to happen while the buyer waited.
Asynchronous Checkout in WP Fusion: about 2 seconds
By default WP Fusion tags the buyer before the next page loads. With Asynchronous Checkout on, the buyer moves on first and the tagging happens right behind them. It’s one setting in WP Fusion.
Two plugins called home while the buyer waited: about 3.3 seconds together
A reviews plugin called its service during checkout (about 0.85 s), and a “someone just bought” popup plugin called its service twice before the thank-you page (about 2.5 s). Both would wait up to a minute if their service was slow. A small must-use plugin now sends the buyer’s page first and makes the same calls a moment later.
A slow lookup: about 1 second
A referral plugin checked each new referral code against every customer’s details. The table that holds user details had no index for “find by name and value”, so the database read it all. One index made that lookup instant.
What we left alone: a card payment took about 5 seconds, with seven exchanges between the site and Stripe. That’s how the payment plugin works.
Logging in to the members site took 8 seconds
Buyers log in to the members site from a button in their order email. With WP Fusion’s login sync on, the members site asked the main site’s CRM for the member’s latest tags and details before showing any page. The member waited while that happened.
A small must-use plugin now shows the page first and runs the same sync straight after. If the sync ran a few minutes ago, it skips it. Logging in went from about 8 seconds to 1.75.
The discussion pages did something similar: they asked for the member’s tags on every single view. Now the tags are reused if they were fetched in the last 5 minutes. The first view still checks, on purpose, because what a member can open depends on their tags. Repeat views went from 1.9 seconds to 0.85.
A slow members home page: two surprises
The members home page took 3.7 seconds. Neither cause was where you’d look first.
The word “@media” looked like a mention
The page’s own styling contains “@media”. BuddyBoss reads “@name” as a mention of a member, so on every view it looked through the member records for someone called “media”. We stopped that check on ordinary pages. Mentions in the feed, forums and comments still work.
A widget added up a number for every member
A widget on the page was set to total a number across every member, on every view, when it should have shown the member their own. It was slow, and it was wrong too: each member saw the whole site’s total. Showing each member their own number fixes both.
With the same code cache and index fixes as the main site, the home page now takes 0.8 seconds.
Check your own site
Run these on a copy of your site first, and time the pages as a buyer and as a member, not as an admin.
- How big is the PHP code cache (OPcache), and is it full? Your host can tell you.
- Is WP Fusion’s Asynchronous Checkout on?
- Which plugins call an outside service during checkout or on the thank-you page, and how long will they wait?
- Does WP Fusion fetch tags from the CRM when members log in, and does the member wait for it?
- Does any widget on your members’ pages add up numbers for every member?
- Time the pages a buyer actually sees, as a buyer, before and after each change.
The times in this guide come from our own test orders on the client’s live sites in November 2026.
Questions owners ask
Do I need a developer for these fixes?
For some. WP Fusion’s Asynchronous Checkout is one setting you can change yourself. The code cache size is a server setting, and the database index is a change to a table, so ask whoever runs your server. The rest were small must-use plugins, which need someone who writes PHP.
Is Asynchronous Checkout safe for access?
It lets the buyer move on first and adds the tags a moment later. Test it with a new buyer on a copy of your site, and check that access and the login email still arrive.
Can I make the card payment itself faster?
We looked and left it alone. A card payment took about 5 seconds, most of it spent going back and forth with Stripe. That is how the payment plugin works, and cutting into it isn’t worth the risk.
Does reusing the tags let people keep access they’ve lost?
For a few minutes, on repeat visits. The first discussion page in a visit still asks for the member’s latest tags, so access is checked. After that the tags are reused for 5 minutes. Choose a shorter time if access changes must apply at once.
Will a caching plugin fix this?
Mostly not. Checkout, offers and members’ pages are built fresh for each person, so page caching doesn’t apply to them. The code cache in this guide is a different thing: it saves the site’s compiled code, not the pages.
