Speed is not a separate technical score. On a campaign page, it affects whether the promise appears, whether interactions feel trustworthy, and whether paid traffic gets a fair chance to convert.
LCP: when the page feels ready
Largest Contentful Paint measures how quickly the biggest piece of content in the first viewport becomes visible—usually the hero image or headline. In business terms, it is the moment the visitor can tell whether they are in the right place. Every second before that is a second of paid attention spent on nothing.
The usual culprits are predictable. An oversized hero image in a legacy format. Fonts that block text from rendering. A hero that waits for JavaScript to hydrate before it appears. Third-party tags loaded in the head ahead of the content.
The fixes are equally predictable, and most are a single afternoon of work:
- Serve the hero image in a modern format at the size it is actually displayed, with explicit width and height.
- Preload the hero asset and give it high fetch priority; lazy-load everything below the fold instead.
- Render the headline and subhead as server-delivered HTML so text does not wait on scripts.
- Use font-display so text is readable during font loading, and self-host or subset the faces you keep.
- Move non-essential third-party scripts out of the critical path.
Google publishes current thresholds for each metric, so check its Web Vitals documentation rather than memorizing a number. The direction is what matters: the hero should appear in the first moment, not after it.
INP: whether the page responds
Interaction to Next Paint measures how quickly the page visibly reacts after a tap, click, or keypress. It replaced First Input Delay because it looks at the whole visit, not just the first interaction—which is exactly what matters on a page whose value depends on a form.
Poor responsiveness usually comes from too much JavaScript competing for the main thread: heavy analytics and tag managers, chat widgets, A/B testing scripts that block rendering, or client-side validation running on every keystroke.
The remedy is triage, not heroics. Count the third-party scripts on the page and justify each one against the campaign it serves. Defer chat and support widgets until a visitor asks for them. Validate on blur rather than on input. Break long tasks so the browser can paint between them.
Responsiveness is also a credibility signal. When a button does nothing for half a second, visitors tap again, assume the form failed, or leave. Immediate visual feedback on submit—a disabled state with a spinner and a short label—costs almost nothing and removes an entire class of doubt.
CLS: whether the page stays put
Cumulative Layout Shift measures unexpected movement of content after it renders. On a landing page, it is the reason someone taps the wrong thing, loses their place in a paragraph, or misses the button entirely.
The common causes are images and embeds without reserved dimensions, fonts that swap to a different metric mid-load, banners and consent bars injected above existing content, and elements that resize after data arrives.
Fixes are mechanical: set width and height or an aspect ratio on every image, video, and iframe; reserve space for anything injected late; match fallback and web font metrics as closely as you can; and avoid inserting announcement bars above content that has already painted.
Layout stability disproportionately affects mobile, where a small shift can move a button under a thumb already in motion. It is one of the few performance problems visitors describe as feeling “broken,” so it deserves attention out of proportion to its technical difficulty.
Use field data and prioritize value
Lab tools like Lighthouse are diagnostic; they tell you what to fix. Field data—real visits on real devices and networks—tells you whether it matters. Use both, and treat the field data as the score that counts.
Segment before you act. A page can look healthy overall while performing badly for the mobile paid traffic you are buying. Look at metrics by device and by campaign, because that is where the money is going.
Then prioritize by value rather than by score. The highest-return sequence on most campaign pages is: fix the hero image and fonts, remove or defer unnecessary third-party scripts, reserve space for anything that loads late, and only then chase the remaining points.
Set a performance budget so the wins hold. Agree on a maximum hero weight, a maximum number of third-party tags, and a rule that new embeds load after interaction. Without a budget, every page drifts back toward slow one well-intentioned addition at a time.
Performance work belongs in the campaign plan. Protect the message, the interaction, and the layout before adding another tracking script.
Sources and further reading
Our guidance is informed by current primary and research-led resources, including Google’s Web Vitals documentation, Google Search’s people-first content guidance, Nielsen Norman Group’s form usability research, and Baymard Institute’s form and checkout research.