Before you announce a new WordPress site, run through a short list: confirm the cache stack is active, set up a real backup habit, decide your editor workflow, and test the site as a visitor would. Most launch-day problems are one of these four things left unchecked, not some exotic misconfiguration.
This checklist assumes a fresh WordPress install on Flashcloud hosting. Work through it top to bottom before you point traffic at the domain.
Start with the block editor, add plugins only when needed
WordPress ships with the block editor (Gutenberg) built in, and it covers more ground than people expect: columns, galleries, buttons, cover images, and reusable patterns are all native blocks. Build your first pages with core blocks before reaching for a page builder plugin.
This isn't a purity rule, it's a performance one. Every plugin you add is code that runs on every page load. Page builders in particular add their own CSS and JS on top of core WordPress, and that weight adds up fast. If your site is slow six months from now, a stack of heavy plugins is one of the first places to look.
A practical rule: install a plugin when a core block genuinely can't do the job, not because it's available. Common legitimate needs at launch are a form plugin (contact forms aren't a core block), an SEO plugin for meta control, and, if you're running a store, WooCommerce. Skip anything billed as an "all in one" toolkit until you've confirmed you need more than one thing from it.
Confirm the cache stack is doing its job
Every Flashcloud WordPress install comes with LiteSpeed Web Server, the LiteSpeed Cache plugin pre-installed, and a Redis object cache. Before launch, open wp-admin → Plugins and confirm LiteSpeed Cache shows as active. If it's missing or disabled, your pages are being generated fresh on every request instead of served from cache, and you'll feel it under any real traffic.
You don't need to configure much manually, the plugin comes pre-tuned. What's worth checking at launch:
- Purge the cache once after your final content changes, so the first visitor doesn't see a stale build from testing.
- If you're running WooCommerce, check that cart and checkout pages aren't being served from full-page cache before launch.
- If your media library has anything uploaded at full camera resolution, check the image optimization settings in LiteSpeed Cache's plugin menu.
If you want the deeper picture of what runs at the server level versus what's left to you as the site owner, see My WordPress site is slow.
Set up backups before you need them
Your account already has daily automatic backups running in the background, but launch day is still the right time to take a manual snapshot. Do it right before you go live, and again right after, so you have a clean restore point on either side of the cutover.
If you're migrating content in from somewhere else, staging in themes, or running any bulk import, back up immediately before that step too. A backup taken five minutes too late doesn't help you.
Test major changes off the live domain
If you're still finalizing a theme, testing a plugin that touches checkout or forms, or making structural changes after the site has already gone live, do that work on a separate dev copy first rather than on the domain visitors are using. See Using WordPress staging for more on keeping a test copy separate from production.
This matters even more once the site is live and taking real orders or form submissions, since overwriting the live database with an old copy can wipe out anything that came in during the gap. If you're running a store, the same caution applies doubly, see Running a WooCommerce store for the store-specific version of this workflow.
Do a pre-launch walkthrough
Before you call it done, check the basics as a visitor would, not as the admin:
- Load the homepage and your key pages in a private browser window, logged out.
- Submit any forms and confirm you receive the notification email.
- Check the site over HTTPS. SSL is auto-issued by Let's Encrypt about 5 minutes after your domain's DNS points to Flashcloud, and renews automatically, so this should work once DNS has propagated.
- Open
wp-admin → Tools → Site Healthand read through anything under "Critical issues." Most items under "Recommended improvements" are not launch blockers, see WordPress Site Health warnings and which ones matter for which ones to actually act on. - If you're on WooCommerce, run a full test purchase end to end, add to cart, checkout, confirmation email.
If something won't cooperate
If DNS isn't resolving, SSL hasn't issued after a reasonable wait, or a plugin conflict is blocking your launch and you can't isolate the cause, open a ticket from the portal. Support is real humans, no phone tree, and you can share credentials through the ticket's secure-share panel if they need access to help diagnose it.