Run a website speed audit before a marketing campaign by testing the exact pages your ads and emails will send people to, on mobile first, using both lab data and real-user data, then fixing the slowest problems and load-testing the site before launch day.
Paid traffic is expensive, so every second your page takes to load costs you leads you've already paid for.
The audit takes a few hours if you follow a checklist: define the scope, check your hosting and server response, review tracking tags and SEO basics, test each landing page, fix what the data shows, and confirm the site can handle the traffic spike.
Here's how to do each step.
1. Why a Speed Audit Belongs in Your Campaign Plan
Campaigns send a burst of visitors to a handful of pages, often on phones and mobile networks, and often from social apps or ads that make people impatient.
If those pages are slow, you pay for clicks that never turn into leads. Several studies show how sensitive visitors are.
A Google and Deloitte study of 30 million mobile sessions found that a 0.1-second mobile speed improvement was linked to an 8.4% increase in retail conversions.
Google and SOASTA research found the chance of a mobile visitor bouncing rises about 90% as load time goes from one second to five.
Speed also affects ad performance. Google Ads includes a landing page experience factor in Quality Score, so a slow or hard-to-use page can raise your costs.
And overall, most sites have room to improve: the 2025 Web Almanac from HTTP Archive found only 48% of mobile sites and 56% of desktop sites pass all three Core Web Vitals.
Because most campaign traffic comes from phones, your audit should start with the mobile experience.
This guide on how to build a better website experience for mobile users covers layout, tap targets, and loading habits that make mobile pages feel fast.
Try this: Open the page your ad will link to on your phone, using mobile data instead of Wi-Fi, and time how long it takes before you could act.
2. Define the Scope and Timeline
Audits fail when they try to test everything. Focus on the pages that carry the campaign.
List:
- Landing pages for each ad group, email, and social post
- The pages visitors go to next, such as pricing, product, booking, or checkout pages
- Thank-you and confirmation pages, since tracking often fires there
- Your homepage, because many visitors click through to it
- Devices and networks: at minimum, a recent phone on mobile data and a mid-range or older phone
Set a timeline. A good rule is to finish the audit two weeks before launch, leaving time to fix issues, retest, and freeze changes.
Ask your team to avoid major updates in the last few days, since late plugin updates, theme edits, and new scripts are a common cause of launch-day problems.
Routine upkeep supports this schedule. If your site hasn't been updated in a while, outdated software and content can slow it down or create security risks, so read this guide on website maintenance and updates to see how often to review core software, plugins, and content.
Try this: Put the audit, fix, retest, and freeze dates on one calendar, working backward from launch day.
3. Audit Your Hosting, Server Response, and Caching
Every page depends on how quickly your server responds. Time to First Byte (TTFB) measures how long it takes for the first byte of data to arrive after a request.
Google's guidance treats 800 milliseconds or less as good, and since TTFB uses up part of your 2.5-second Largest Contentful Paint budget, aim much lower in practice.
Check:
- Server response time on your key pages
- Caching: Is page caching enabled, and does it work for landing pages?
- CDN: Are images and static files served from a content delivery network?
- Hosting plan limits: CPU, memory, bandwidth, and concurrent connections
- PHP and software versions: Are they current and supported?
- Database health: Are there slow queries or bloated tables?
- Uptime history: Has the site had outages or slowdowns recently?
If your site runs on WordPress, many speed gains come from a few well-known fixes.
This guide to the ways to speed up a WordPress website walks through caching, images, plugins, and hosting upgrades.
Try this: Ask your host what traffic your plan can handle and whether it scales automatically during spikes.
4. Audit Tracking Tags, SEO Basics, and Technical Health
Campaign pages carry extra code: analytics, ad pixels, tag managers, chat widgets, and heatmaps. Each one adds requests and processing time. Audit them like this:
- List every script that loads on your landing pages.
- Remove what you don't need, such as old pixels from past campaigns.
- Delay or defer non-essential tools so they don't block the page from showing.
- Confirm tracking works, including form submissions, purchases, and call clicks, since a fast page that doesn't record conversions wastes your budget.
- Check basic SEO: titles, descriptions, canonical tags, indexing settings, and redirects. Campaign pages often shouldn't be indexed, while evergreen pages should be.
- Fix broken links and redirect chains, which slow visitors and waste ad clicks.
- Verify HTTPS and security so browsers don't warn visitors.
Campaigns and organic search often feed each other, so it helps to understand how your site performs for both.
This WordPress SEO guide to boost organic traffic covers the on-site settings and content habits that support organic visibility alongside paid traffic.
Try this: Use Google Tag Manager's preview mode, or your browser's network tab, to count how many third-party requests your landing page makes.
5. Run Lab and Field Tests on Every Campaign Page
Now measure. Use two kinds of data, because they answer different questions.
- Lab data comes from a controlled test, such as Lighthouse. It's repeatable and great for diagnosing problems.
- Field data comes from real visitors, collected through the Chrome User Experience Report (CrUX) over a rolling 28-day window at the 75th percentile. It shows what people actually experience, and Google's Core Web Vitals assessment uses it.
Google's PageSpeed Insights shows both in one report. According to Chrome's developer documentation, CrUX collects real-user experiences from the field while Lighthouse is a controlled test in the lab.
A page can score well in a lab test and still show poor field results if real visitors use slower devices and networks.
New landing pages may have no field data yet, in which case PageSpeed Insights may show origin-level data or none, and you'll rely on lab data.
Core Web Vitals targets, measured at the 75th percentile, are:
| Metric | Good |
|---|---|
| Largest Contentful Paint (LCP) | 2.5 seconds or less |
| Interaction to Next Paint (INP) | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | 0.1 or less |
A practical testing routine:
- Run each page in PageSpeed Insights on mobile first, then desktop. Record the lab metrics and field data if available.
- Check Google Search Console's Core Web Vitals report to see URL groups Google flags as poor or needing improvement.
- Use Chrome DevTools with CPU and network throttling to simulate a mid-range phone on a slower connection.
- Test from other locations with a tool like WebPageTest or GTmetrix, especially if your customers are in different regions.
- Test the full journey, not just the first page: click through the form, checkout, or booking flow.
- Run each test several times and use the median, since results vary from run to run.
For a technical walkthrough of reading CrUX data inside PageSpeed Insights, see Chrome's guide to viewing CrUX data in PageSpeed Insights, and for how the wider web performs, see HTTP Archive's 2025 Web Almanac performance chapter.
6. Diagnose and Prioritize Fixes
Turn the results into a ranked to-do list. Common problems and fixes include:
| Problem | Likely fix |
|---|---|
| Slow LCP | Compress and resize the hero image, use WebP or AVIF, preload it, and don't lazy-load it |
| High TTFB | Better hosting, server caching, CDN, and database cleanup |
| Poor INP | Reduce heavy JavaScript, delay third-party scripts, and break up long tasks |
| Layout shifts | Set image and ad dimensions, reserve space for banners, and load fonts properly |
| Heavy pages | Remove unused plugins, scripts, and large videos |
| Render-blocking files | Minify, defer, and inline critical CSS |
| Slow forms | Simplify fields and test submission speed |
To identify further improvements, follow Google's recommendations to optimize website loading performance.
These techniques cover resource loading, image optimization, JavaScript execution, and other performance improvements that can make campaign landing pages faster and more responsive.
Rank each fix by impact and effort. Do the high-impact, low-effort items first, such as image compression and removing unused scripts.
Save bigger projects, like hosting migration, for early in your timeline so you have time to retest.
Make changes one at a time, or in small batches, and retest. That way you know what worked, and you can roll back anything that breaks the page.
7. Load-Test for the Traffic Spike
A page can be fast for one visitor and slow for a thousand. Before a major campaign, test how your site behaves under load:
- Estimate peak traffic. Use your ad budget, expected click-through rates, and email list size to guess how many visitors could arrive in the first hour.
- Run a load test with a tool such as k6 or a hosted testing service, on a staging copy or at a quiet time with your host's permission.
- Watch response times, error rates, and server resources as simulated users increase.
- Check dependencies. Payment gateways, booking systems, and third-party APIs can become bottlenecks.
- Set up caching rules that keep landing pages served from cache under heavy traffic.
- Confirm autoscaling or a plan upgrade is ready if you expect a major spike.
Follow these website load testing best practices from Grafana to simulate realistic visitor behavior, identify server bottlenecks, and understand how your website responds to increasing traffic.
This helps you spot performance problems before a marketing campaign sends a large number of visitors to your site.
Tell your hosting provider about the campaign, so they can flag capacity issues in advance.
8. Final Pre-Launch Checks and Monitoring
In the last week:
- Retest every campaign page on mobile and desktop.
- Freeze changes. No plugin updates, theme edits, or new scripts unless urgent.
- Back up the site and know how to restore it.
- Test tracking with a real form submission and purchase.
- Click every link and button in your ads and emails, including UTM-tagged URLs.
- Set up uptime monitoring and alerts so you hear about problems immediately.
- Assign an owner who can act fast during launch.
After launch, watch your analytics and speed monitoring daily. Compare bounce rate, conversion rate, and page speed against your baseline, and adjust quickly if something slips.
Remember that Google's field data covers a rolling 28-day window, so changes take weeks to show fully, but your own real-user monitoring and analytics can show problems much faster.
9. A Simple Audit Report Template
Record your findings so the whole team can act:
| Page | Device | LCP | INP | CLS | TTFB | Top issue | Fix | Owner | Status |
|---|---|---|---|---|---|---|---|---|---|
| Landing page A | Mobile | ||||||||
| Pricing page | Mobile | ||||||||
| Checkout | Mobile |
Keep your baseline and post-fix numbers side by side. The improvement is useful evidence when you ask for a budget or explain results.
10. Common Mistakes to Avoid
- Testing only the homepage. Campaign landing pages are the ones that matter.
- Testing only on desktop or office Wi-Fi.
- Trusting a single lab score. Use field data and multiple runs.
- Chasing a perfect 100. Focus on real-user metrics and conversion results.
- Adding new tracking tags at the last minute.
- Skipping the load test for large campaigns.
- Forgetting the post-click journey. A fast landing page followed by a slow checkout still loses sales.
- Launching without monitoring.
Also Read: Steps to Check Website Speed Before Launching a Campaign
Audit Timeline Cheat Sheet
| When | Task |
|---|---|
| 3 to 4 weeks before launch | Define scope, run baseline tests, and review hosting |
| 2 to 3 weeks before | Fix top issues and clean up tags |
| 1 to 2 weeks before | Retest, load-test, and confirm tracking |
| Final week | Freeze changes, back up, set up monitoring |
| Launch week | Watch metrics daily and fix issues quickly |
The Bottom Line
A website speed audit before a marketing campaign protects your ad spend. Test the pages visitors will actually land on, check both lab and real-user data, fix the biggest bottlenecks first, and confirm your site can handle the traffic spike.
Then freeze changes, monitor closely, and compare results with your baseline. A few focused hours of work before launch can mean more conversions from the same budget.