Should You Measure Your Current Site Before a Redesign?
Yes. Measure your current site before a redesign, because the baseline is what scopes the rebuild and proves it worked. Record Core Web Vitals at the 75th percentile, error rates, funnel drop-off points and conversion by page type and device for at least 28 days. You don't need the new site to start measuring.
Last updated November 20, 2026
Teams planning an ecommerce website redesign often put measurement on hold until the new site exists, on the logic that the current site is too dated to be worth instrumenting. That gets the order backwards. To measure a baseline before an ecommerce website redesign is to find out which pages are slow, which steps lose shoppers and which errors cost orders, and those answers decide what the redesign has to change. This playbook covers what to record, how to build the baseline step by step, how long to collect it and how to use it to prove the redesign's impact after launch.
Key takeaways
- Measure the current site before a redesign: the baseline sets the scope of the rebuild and is the only way to prove its impact afterward.
- Record Core Web Vitals (LCP, INP, CLS) at the 75th percentile by page type and device, plus error rates, funnel drop-off and conversion rate.
- Google's good thresholds are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
- Collect at least 28 days of real-user data, matching the Chrome UX Report's rolling window, and avoid a baseline taken only during peak or a sale.
- Noibu's Performance Agent measures Core Web Vitals from real shopper traffic, ranks the worst page groups and stages changes for your review, so the baseline can start today.
Part of: Noibu's Performance Agent
Should you measure your current site before a redesign?
Yes. Measuring the current site before an ecommerce website redesign answers two questions the project cannot answer any other way: what the redesign needs to change, and whether the redesign made things better. Without a baseline, scope is set by opinion and by whatever looks oldest, and success is judged by whether the new site looks better. With a baseline, scope is set by the pages and steps where shoppers are actually lost, and success is a before-and-after comparison on the same metrics.
A pre-redesign baseline also protects revenue during the project. Redesigns change templates, scripts, URLs and checkout flows at once, and any of those can break something that worked. The common failure modes are covered in common mistakes to avoid during an ecommerce website redesign; a baseline is what lets a team see those mistakes in numbers instead of in a quarter-end revenue report.
Why don't you need the new site to start measuring?
Measurement describes what shoppers experience on the site that exists today, and that is exactly what a redesign is meant to improve. Real-user Core Web Vitals, error rates and funnel drop-off can all be collected from the current storefront without changing its design. Google's own field dataset, the Chrome UX Report, already holds data for eligible origins and URLs, split by phone, tablet and desktop, whether or not a store has set anything up.
Waiting has a cost. Every month without a baseline is a month of the old site's problems going unmeasured, and after launch there is nothing to compare the new site against. If conversion falls after relaunch, a team without a baseline cannot tell whether the redesign caused it or whether it was already falling. Measuring the current site first is not extra work layered on the redesign; it is the research phase of the redesign.
What should a pre-redesign baseline include?
A useful baseline before an ecommerce website redesign covers four areas: speed, stability, errors and conversion. Each should be recorded by page type (home, category, product, cart, checkout) and by device, because a redesign usually changes templates one page type at a time and mobile and desktop rarely behave the same way. For Core Web Vitals, use the thresholds Google publishes on web.dev: Largest Contentful Paint (LCP) of 2.5 seconds or less, Interaction to Next Paint (INP) of 200 milliseconds or less and Cumulative Layout Shift (CLS) of 0.1 or less, measured at the 75th percentile of page loads and segmented across mobile and desktop.
| Metric | What it shows | What to record | Segment by |
|---|---|---|---|
| Largest Contentful Paint (LCP) | Loading speed of the main content | Good at 2.5 s or less; poor above 4 s | Page type, device |
| Interaction to Next Paint (INP) | How fast the page responds to taps and clicks | Good at 200 ms or less; poor above 500 ms | Page type, device |
| Cumulative Layout Shift (CLS) | Visual stability while the page loads | Good at 0.1 or less; poor above 0.25 | Page type, device |
| Error rate | JavaScript, network and checkout errors per session | Share of sessions with an error, and the top errors by sessions affected | Page type, device, browser |
| Funnel drop-off | Where shoppers leave between product, cart and checkout | Step-to-step continuation rate | Device, traffic source |
| Conversion rate and revenue per session | Outcome the redesign is meant to move | Orders divided by sessions, and revenue divided by sessions | Page type of entry, device, traffic source |
Core Web Vitals thresholds: web.dev, Defining the Core Web Vitals metrics thresholds, assessed at the 75th percentile of page views.
The poor thresholds matter as much as the good ones. Google's threshold methodology classifies a page as poor for LCP above 4 seconds, for INP above 500 milliseconds and for CLS above 0.25, and assesses each at the 75th percentile of page views. Page types that sit in the poor band on mobile are usually the first candidates for a template rebuild, while page types that already pass may only need to be protected during the redesign.
Speed is also a search consideration. Google Search Central states that it highly recommends site owners achieve good Core Web Vitals for success with Search, so a redesign that regresses LCP or INP on category and product pages can cost organic traffic as well as conversion. Which Core Web Vitals tend to move ecommerce conversion most is covered in Core Web Vitals for ecommerce: which ones actually move conversion.
How do you build a baseline before an ecommerce website redesign?
Building a baseline before an ecommerce website redesign takes six steps, and none of them require the new design to exist. The step flow below is the extractable summary of the process; each step is explained underneath.
Six steps to a pre-redesign baseline
- 1
Group pages by type
List the page types the redesign will touch: home, category, product, search, cart and checkout.
- 2
Collect real-user Core Web Vitals
Record LCP, INP and CLS at the 75th percentile for each page type on mobile and desktop.
- 3
Count errors by page type
Record the share of sessions with errors and the top errors by sessions and revenue affected.
- 4
Map funnel drop-off
Record step-to-step continuation from product page to order confirmation, by device.
- 5
Record conversion and revenue
Capture conversion rate and revenue per session by entry page type, device and source.
- 6
Rank and freeze the baseline
Rank page types by revenue at risk, save the numbers and dates, and use them to set redesign scope.
Step 1: group pages by type. A redesign rebuilds templates, not individual URLs, so the baseline should be organized the same way. Grouping thousands of product URLs into one product page group gives a stable number to compare before and after, and it matches how the new templates will ship.
Step 2: collect real-user Core Web Vitals. Use field data from real shoppers, not only lab scores. Lab tools test one simulated device on one connection, while field data reflects the phones, networks and browsing habits of actual customers. The gap between the two is explained in why a Lighthouse score differs from real-user Core Web Vitals. A lab score can still help to reproduce a problem, but the baseline should be the field number.
Step 3: count errors by page type. Record how many sessions hit a JavaScript error, a failed network request or a checkout error, and which errors affect the most sessions and revenue. Errors on the current site are evidence for the redesign brief: an add-to-cart error caused by an old script is a requirement for the rebuild, and an error that disappears after relaunch is a measurable win.
Step 4: map funnel drop-off. Record the share of shoppers who continue from product page to cart, cart to checkout and checkout to order, separately for mobile and desktop. A large drop at one step on one device is a stronger scoping signal than a site-wide average, because it points to a specific template and a specific audience.
Step 5: record conversion and revenue. Capture conversion rate and revenue per session by entry page type, device and traffic source. Revenue per session is useful alongside conversion rate because a redesign can change average order value as well as the number of orders.
Step 6: rank and freeze the baseline. Rank page types by the revenue flowing through them and how far they miss the thresholds, then save the numbers with their date range. A frozen baseline is the reference point for every later comparison, so it should not be recalculated with new definitions after launch.
How long should you measure before a redesign?
Collect at least 28 days of data before an ecommerce website redesign. The Chrome UX Report API documentation describes its data as a 28-day rolling average of aggregated metrics, updated daily, so a four-week window lines up with the field data Google itself uses. Four weeks also covers weekday and weekend patterns and normal campaign cycles.
Avoid a baseline taken only during peak season, a sitewide sale or a major campaign. Traffic mix, device mix and conversion all shift in those periods, and a baseline built from them will make an ordinary post-launch month look worse than it is. If the redesign launches near peak, record the same weeks from the prior year as a second reference, using the same metric definitions.
How does a baseline scope the redesign?
A pre-redesign baseline turns the redesign brief from a list of preferences into a ranked list of problems. If product pages on mobile miss the LCP threshold and carry most of the revenue, the product template's image loading and third-party scripts move to the top of the brief. If checkout continuation is healthy on desktop but weak on mobile, the checkout rebuild can focus on the mobile flow instead of starting from scratch.
The baseline can also narrow the project. Some problems found while measuring the current site, such as a slow app script or a single broken form, can be addressed before the redesign starts, which recovers revenue sooner and removes noise from the post-launch comparison. Teams moving platforms as part of the redesign can apply the same approach with the ecommerce replatforming checklist of what to monitor before, during and after migration.
How do you prove the redesign worked?
To prove the impact of an ecommerce website redesign, compare the same metrics, with the same definitions, segments and window length, before and after launch. Compare each page type and device separately, because a site-wide average can hide a faster product page and a slower checkout in the same number.
Allow for settling time if URLs change. Google Search Central's site move guidance says to expect temporary fluctuation in ranking during a move and that it can take a few weeks or more for Google to start showing new URLs instead of old ones, so organic traffic shifts in the first weeks are not a verdict on the design. If conversion falls after launch, the baseline shows where to look first; the diagnosis is covered in what to do when conversion drops after a site redesign.
How does Noibu's Performance Agent build a pre-redesign baseline?
Noibu's Performance Agent works on the current site, so the baseline can start before the redesign does. It measures Core Web Vitals from real shopper traffic, ranks the worst-performing page groups and identifies the root cause of each slowdown. The output is a ranked list of page groups to put at the top of the redesign brief, plus changes the agent stages for your review, so improvements to the current site do not wait behind a dev cycle. Nothing goes live until a person on your team approves it, and the agent then measures what moved.
Noibu's CRO Agent covers the conversion side of the baseline. It finds underperforming product pages, the ones with traffic that are not driving add-to-carts, and rewrites them to convert better; your team reviews the changes, makes inline edits and publishes. Together, the two agents give a redesign team a measured starting point for speed and conversion on the site that exists today.
The Performance Agent and CRO Agent are two of six supervised agents, alongside the Bug Resolution, ADA, A/B Testing and ROAS agents, and all of them work in the Noibu console and in Claude, ChatGPT and other AI tools through Noibu MCP.
The short version
Measure the current site before an ecommerce website redesign. Record Core Web Vitals at the 75th percentile, error rates, funnel drop-off and conversion by page type and device for at least 28 days, freeze the numbers, and use them to rank what the redesign must change. After launch, compare the same metrics the same way. For a quick read on where the current site is slow or losing shoppers, start with Noibu's free website audit.
Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval. Trusted by retailers like Free People, Guess, Liquid I.V., and Ariat.
Frequently asked questions
Should I measure my current website before a redesign?
Yes. Measuring the current site before a redesign shows which pages are slow, which steps lose shoppers and which errors cost orders, and those findings set the scope of the rebuild. The same baseline is the only way to prove after launch that the redesign improved speed and conversion.
Do I need a new website before I can start monitoring performance?
No. Real-user Core Web Vitals, error rates, funnel drop-off and conversion can all be measured on the current site without changing its design. Measuring the current site is what tells the redesign team what to change first.
What metrics should a pre-redesign baseline include?
Record Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift at the 75th percentile, the share of sessions with errors, step-to-step funnel drop-off, conversion rate and revenue per session. Segment each by page type and device.
What are the Core Web Vitals thresholds to compare against?
Google rates LCP as good at 2.5 seconds or less and poor above 4 seconds, INP as good at 200 milliseconds or less and poor above 500 milliseconds, and CLS as good at 0.1 or less and poor above 0.25, each assessed at the 75th percentile of page views.
How long should I collect baseline data before a redesign?
Collect at least 28 days, which matches the rolling window of the Chrome UX Report and covers weekly patterns. Avoid a baseline taken only during peak season or a sitewide sale, and add the same weeks from the prior year if launch is close to peak.
Where should I start measuring before a redesign?
Start by grouping pages by type and collecting real-user Core Web Vitals and conversion for each group on mobile and desktop. For a quick read on the current site, run Noibu's free website audit, then use Noibu's Performance Agent to rank the worst page groups and stage changes for your review.
