How to Check Real Customer Page Speed — Before and After Website Changes

When you change a website—new theme, bigger hero image, or a new booking form—you need to know how real customers are affected. Lab tests are useful, but this guide focuses on practical, repeatable ways to check real customer page speed before and after changes so you make decisions that help local businesses in Birmingham, Solihull, Sutton Coldfield and the wider West Midlands.

Why measure real customer page speed (not just lab scores)

Developer tools and Lighthouse give a controlled ‘lab’ view. Real User Monitoring (RUM) captures what your actual customers experience across different devices, networks and locations. For local service businesses that rely on phone calls, form submissions and quick mobile journeys, field data tells you whether a change helped or hurt conversions.

Field vs lab testing: what to use and when

Use lab tests to:

• Diagnose specific performance issues (render-blocking CSS, caching headers, unused JavaScript).
• Compare before/after in controlled conditions (same device, connection).

Use field/RUM to:

• Measure real customer metrics (First Contentful Paint, Largest Contentful Paint, Interaction to Next Paint, cumulative layout shift) across real networks.
• Confirm whether lab improvements actually change user experience for residents and customers in Birmingham and surrounding areas.

Decide a repeatable test protocol

Before you make changes, document a test protocol. Repeat the same tests after deployment to make a fair comparison.

• Pages to test: home, representative service pages, key landing pages (e.g. booking/quote forms).
• Geography: prioritise locations that matter — Birmingham city centre, Solihull, and a couple of West Midlands suburbs. If your analytics show other hotspots, include them.
• Devices: mobile and desktop, with emphasis on mobile for local service searches.
• Connection profiles: a 3G/4G mobile profile and a standard broadband profile for lab tests.
• Timing: capture a 7–14 day pre-change baseline (longer if traffic is low), and the same window post-change.
• Key metrics: LCP, FID/INP, CLS, Time to First Byte (TTFB), and bounce/engagement on tested pages.

Tools and data sources that fit small local businesses

A practical toolkit balances cost and usefulness. Combine two data sources: a RUM feed for field data and synthetic/lab tools for diagnosis.

• RUM options: Google Analytics 4 (with web stream) provides field timing. Chrome User Experience Report (CrUX) gives public field summaries. For more control, a lightweight RUM script or a small custom web application can capture metrics and events from your real visitors.
• Synthetic tools: WebPageTest and Lighthouse help you debug issues. Run tests using the same device and connection settings defined in your protocol.
• Reporting and summaries: save raw results into a simple dashboard. We sometimes use lightweight dashboards or a custom web app to aggregate test results, compare before/after and trigger alerts.
• Assisted insights: when you want quicker interpretation, tools such as AI Assist SMEs can be used in workflows to summarise trends and suggest straightforward prioritised fixes.

Baseline: capture a clear before snapshot

Collect these items before you touch the site:

• Traffic and conversion trends for the pages you’ll change (from your analytics).
• RUM metrics for the last 7–14 days (LCP, INP, CLS, TTFB).
• Lab runs (3–5 runs per page using your defined device/connection).
• Current caching, CDN configuration and image delivery settings.
• A short note of expected changes (what you’re changing and why).

Make changes with a prioritised checklist

When making updates, prioritise low-risk, high-impact items first. Use this practical checklist to guide work and communicate risk to stakeholders (owners, customers, tradespeople).

Performance change checklist

• Document the versioned backup of the site before updates.
• Implement changes on a staging environment that mirrors production.
• Optimise images and media (compress, proper formats, responsive sizes).
• Defer or remove unused third-party scripts during initial testing.
• Ensure caching headers and CDN are configured correctly.
• Test and fix layout shifts caused by dynamic content or ads.
• Run lab tests on staging, then run a short RUM pilot if possible.

Validate after deployment — the before/after comparison

After you deploy, run your protocol and compare like-for-like. Keep the same pages, device types and geographic focus. Look for both metric changes and behavioural signals: has bounce increased on mobile? Are form completions lower?

When interpreting results, focus on:

• Median and distribution — averages can hide variability for local customers on slow connections.
• Segmented performance — for example, mobile visitors from Birmingham compared to desktop visitors from outside the region.
• Conversion impact — small speed regressions can have outsized effects on form completions and calls for time-sensitive services.

Automate monitoring with a simple custom web app

Instead of spreadsheets, a small custom web application can schedule synthetic tests, ingest RUM data and present clear before/after snapshots for non‑technical users. Typical features for a small-business monitoring app:

• Scheduled WebPageTest runs for chosen pages and locations.
• RUM ingestion from Google Analytics or a lightweight RUM beacon.
• Before/after comparison reports that highlight regressions and suggested fixes.
• Email alerts for major regressions on high-traffic pages.

Integrating a tool like AI Assist SMEs can help automatically summarise test results and suggest the next fixes, which is handy when you need quick recommendations for a trades business owner.

Short example workflow — a Birmingham plumber

1. Baseline: capture 14 days of RUM for the homepage and the booking page; run 5 synthetic tests from a London mobile profile and a Birmingham mobile profile.
2. Change: replace a full-width background image with a responsive, compressed image and move a third-party review widget to load after interaction.
3. Staging tests: run the same synthetic tests on staging and confirm lower LCP and no new layout shift.
4. Deploy: push to production in a low-traffic window and start a 14-day post-deploy RUM capture.
5. Compare: use your dashboard to compare median LCP, INP and booking completions. If RUM shows worse performance for Birmingham mobile users, rollback or iterate on the specific change (e.g. defer more scripts).

Practical tips for local service businesses

• Start small: tackle the top 2–3 pages that drive enquiries first.
• Communicate with staff: if you change forms or CTAs, ensure the office knows to expect slight fluctuations in enquiries while monitoring runs.
• Keep stakeholders informed with a short weekly performance summary (a dashboard snapshot and plain English notes).

Ready-made resources and where to learn more

For design-focused improvements, our web design and SEO resources explain practical fixes and priorities. See our web design category for layout and theme guidance and the SEO category for how speed ties into local visibility and rankings. We also publish practical how-to posts and case studies on the DigiSitio blog.

Checklist — Quick pre/post test checklist (copy and use)

• Document test protocol: pages, devices, locations, time window.
• Capture 7–14 days of RUM data before change.
• Run 3–5 synthetic lab tests per page (same device/connection each run).
• Apply change on staging; run the same lab tests.
• Deploy during low-traffic window; capture 7–14 days post-change RUM.
• Compare median/distribution and conversion events; act on regressions.
• Automate recurring checks with a simple dashboard; trigger alerts on major regressions.

Call to action

If you want help designing a repeatable before/after testing protocol or building a small custom monitoring app for your Birmingham or West Midlands business, we can help. Get in touch at the DigiSitio homepage to discuss a practical plan that fits your budget and busiest pages.

Useful links: DigiSitio homepage, our web design resources, our SEO category, a practical guide on reducing image weight and improving mobile responsiveness, and our blog for more practical guides. You can also explore tools we use in workflows such as AI Assist SMEs.

Want a short, practical assessment? Start with a 30-minute review of your top three pages and a clear before/after plan — book a chat via our homepage.