Your booking form might be costing you leads.
Not because it looks bad. Because Google can now measure exactly how slow it feels—step by step—and that measurement is on a path toward Search Console.
Here's what changed, what it means for your site, and what to check before it becomes official.
The Short Version of a Technical Announcement
Google added experimental versions of its three Core Web Vitals metrics to the Chrome User Experience Report (CrUX). CrUX is Google's database of real-world speed data collected from Chrome users—it's the same pool of data that informs site performance tooling across Google's products.
The new versions of these metrics track something called soft navigations. Here's the plain version: a soft navigation happens when a page updates its content and its URL without doing a full reload. Think of filling out a multi-step appointment form where you move from Step 1 to Step 2 without the whole page blinking and restarting. The URL in your browser bar changes, the content changes, but the browser never fully leaves and re-enters the page. That transition is a soft navigation.
Before this update, Google's tools only measured the very first time someone landed on a page. Everything that happened after that—every form step, every in-page update—got lumped back into that first load. The landing page took the blame (or credit) for all of it, making it hard to know which specific step in a booking flow was actually slow.
Now each of those transitions gets its own measurement.
The Three Metrics, Explained Simply
Google's Core Web Vitals are three scores that describe different aspects of how a page feels to use.
LCP — Largest Contentful Paint. This measures how fast the biggest visible element on the screen—usually a photo or a headline—finishes loading. A slow LCP means people stare at a blank or partial page.
INP — Interaction to Next Paint. This is the one that matters most for booking flows. INP measures how quickly the page responds after someone clicks a button or taps a field. If someone taps "Next" on your booking form and nothing happens for a beat, that's a bad INP score. With the new soft-navigation tracking, INP is now measured per page view instead of using the single slowest interaction across an entire session. For sites that rely heavily on in-page updates, Google's own data shows this roughly doubles the number of sites that pass the test on Android.
CLS — Cumulative Layout Shift. This measures whether things jump around on screen unexpectedly—like a button moving just as someone tries to tap it. The new version groups layout shifts by individual view instead of the whole session, which gives a cleaner picture of which step in a flow is causing problems. Google's data shows this change puts desktop sites that rely heavily on soft navigations roughly on par with traditional multi-page sites.
Does This Apply to Your Site?
Probably not in a dramatic way yet—but the direction is worth understanding.
Google's data shows that about 70% of sites in CrUX have very little soft navigation traffic. If your website reloads completely every time someone clicks a link or advances a form step, the new metrics will look essentially identical to the old ones for you.
But here's where it gets worth your attention: modern booking tools, contact forms, and scheduling widgets often behave like single-page applications (SPAs—apps that load once and swap content in place rather than reloading the full page). If your site uses a booking widget that steps users through a calendar, a service picker, and a contact form all within one loaded page, that's exactly the kind of traffic these metrics now track separately.
Among the top 1,000 websites, 42% on desktop use soft navigations for more than half of their page views. That share is likely to grow as more sites adopt modern booking and scheduling tools.
Why Conversion Rate Is the Real Conversation
Google's announcement is about measurement, but the measurement exists because the underlying experience is real. A form step that takes a noticeable moment to respond after a tap doesn't just frustrate people—it causes them to leave.
Think about what happens at the moment someone is about to book your service. They've already decided to move forward. They're on Step 2 of 3. Then the page stutters. Most people don't wait to see if it recovers. They close the tab.
A weak INP score at that step isn't just a technical problem—it's a lead problem. Google is building the infrastructure to measure it precisely. The source material is clear that Search Console plans to adopt this data once the metrics move from experimental to stable; it does not state that soft-navigation scores will directly affect rankings, so treat that piece as an open question rather than a settled fact.
What is settled: if your booking flow feels slow, real people are noticing it right now, regardless of what Google does next.
What Makes a Site Slow at These Moments
Heavy JavaScript is the most common cause. When a user taps "Next" on a booking step, the site has to run code to validate their input, hide the current content, load the next step, and repaint the screen. If that JavaScript is bloated or disorganized, the delay is noticeable. Google's own data notes that sites relying heavily on soft navigations still lag behind traditional multi-page sites on INP specifically because of the JavaScript running during page changes.
Third-party scripts—live chat widgets, tracking pixels, analytics tools—compete for the browser's attention at the exact moment the user is waiting for a response.
Site-builder platforms vary widely. Some generate lean, well-organized code. Others layer in scripts that slow every interaction.
What to Do This Week
You don't need to be a developer to start understanding where your site stands.
- Open Google PageSpeed Insights (search for it—it's a free Google tool) and paste in the URL of your booking page or contact form. Look specifically at the INP score. Google publishes thresholds in its developer documentation. Note your number and track whether it changes after any work is done.
- Walk through your own booking flow on a phone. Use a mid-range Android device if you have one, not your newest model. Tap through each step and notice whether responses feel immediate or delayed. This is the experience your customers are actually having.
- Check how many third-party scripts load on your booking page. Your web developer can do this quickly using Chrome DevTools, which is built into the Chrome browser. Ask them: "How many third-party scripts load on this page, and which ones fire on every interaction?" Every unnecessary script is a candidate for removal or deferral.
- Ask your developer or web partner whether your booking tool is a single-page application. If yes, ask them to pull your INP data from CrUX Vis using the "Include soft navigations" toggle—it's now available in the tool. Comparing the stable and experimental scores side by side shows you where the gaps are.
- Screenshot your current PageSpeed Insights results before making any changes. Changes take time to show up in Google's data, and a clear before-and-after picture is useful for knowing what actually helped.
What Comes Next
The metrics are still experimental. Google has said to expect some shifts in the numbers as measurement improves, so treat the experimental figures as directional, not final. The November CrUX release is the next scheduled checkpoint.
Google aims to conclude the experimental phase around May 2027. After that, Search Console plans to adopt the new data. That's the sequence as described—the specifics of what follows may still shift based on feedback Google receives between now and then.
The practical task is the same either way: know your current INP score, understand whether your booking tool creates soft navigations, and make sure the page where someone is trying to hire you performs well under real conditions. That work is worth doing regardless of any measurement timeline.