Codeinate
Find your tool

Menu

Web performance and Core Web Vitals: fast pages on the phones your customers actually use

Web performance optimization is the work of making a page load, render and respond faster on real devices and networks, measured by Google's Core Web Vitals: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.

Updated

Book a free 30-minute call

Overview

A slow page is expensive in three ways. Visitors leave before it loads. Google uses page experience as a ranking signal and as part of the landing page experience that affects what you pay for ads. And a slow page is usually a heavy page, which costs more to serve.

The good news is that most slow pages are slow for the same few reasons: oversized images, scripts from third parties, fonts that block text, and layouts that jump as things load. These are fixable without a redesign.

Codeinate measures on a mid-range phone on a slow connection, because that is where your visitors are, then fixes the biggest cause first and measures again. Every change comes with a before and after number.

What a speed review covers

  • Core Web Vitals on real devices

    Lab measurement at phone width with a throttled network and CPU, plus field data from Chrome users where Google provides it. Codeinate reports Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift per page template.

  • Images and media

    Right-sized, modern formats, width and height set so nothing jumps, lazy loading below the fold and the hero image given priority. This alone is often the largest gain.

  • Scripts and third parties

    Every tag manager, chat widget, analytics script and font loader is weighed. Each one either earns its place, loads later, or goes.

  • Fonts and text

    Self-hosted fonts, only the weights in use, and a fallback that matches so text shows at once and does not shift when the font arrives.

  • Server, caching and delivery

    Compression, long cache lifetimes for files with hashed names, a content delivery network close to your visitors, and a fast first byte. Codeinate checks your own site's response headers the way it checks Codeinate's.

  • Layout stability and interaction

    Reserved space for ads, banners and embeds so content does not move; handlers that respond within the budget so taps feel instant.

Problems that come up, and what happens next

Problems that come up, and what happens next
The problemWhat Codeinate does about it
The page looks fine on the office laptop but visitors on phones leave.Codeinate measures at phone width on a slow connection and shows you the same page the way they see it. Then Codeinate fixes what that measurement names first.
A hero image the size of a poster is sent to every phone.Multiple sizes, a modern format and a priority hint for the first image. The rest load as the visitor scrolls.
Five marketing scripts load before the page's own content.Scripts move after the content, load on interaction where possible, and the ones nobody can name a use for are removed with the marketing team's agreement.
Text jumps when the font loads, and buttons move as banners appear.Matched fallback fonts and reserved space for everything that arrives late. Layout shift drops to near zero.
The site is on a platform you cannot change much.Even on a hosted platform, images, scripts, fonts and caching headers are usually in your control. Codeinate works within the platform's limits and tells you what is not possible there.

How a speed review runs

  1. 1

    Measure

    Your key page templates measured at phone and desktop width, slow and fast network. A short note ranks the causes by impact.

  2. 2

    Fix the biggest cause first

    Images, then scripts, then fonts, then delivery. Each change is measured on its own so you know what it was worth.

  3. 3

    Verify in the field

    Where Google's field data exists for your site, Codeinate watches it move over the following weeks; lab numbers are the start, real users are the proof.

  4. 4

    Keep it fast

    A performance budget in the build and a monthly check, so a new banner or plugin cannot quietly undo the work.

When a campaign starts tomorrow and the landing page takes ten seconds

With one day there is no time for a rebuild, so the order is: compress and resize the images above the fold, remove or defer every script that is not needed for the page to work, make sure compression and caching are on at the server, and check the page on a real phone on mobile data.

Those four steps usually bring a page from unusable to acceptable in a day. The proper review afterwards makes it fast. If the page is for Google Ads™, see the SEO and lead generation service for why speed changes what you pay.

What usually makes a page slow, and what fixes it

What usually makes a page slow, and what fixes it
CauseWhat the visitor feelsFixTypical effort
Oversized imagesBlank area, then a slow fillResize, modern format, lazy loadingHours
Third-party scriptsPage freezes, late contentDefer, load on interaction, removeHours to days
Blocking fontsInvisible text, then a jumpSelf-host, subset, matched fallbackHours
No compression or cachingEvery visit is slowServer headers, CDNHours
Heavy framework on a content pageLong wait before anything worksStatic rendering, less JavaScriptDays to weeks

Check your page speed first

Run your page through Google's PageSpeed Insights, paste the numbers into Codeinate's page speed check with your monthly ad budget, and see an estimate of what a faster page would be worth before you talk to anyone.

Check your page speed

Questions people ask

What are Core Web Vitals?

Core Web Vitals are three measurements Google uses to describe page experience: Largest Contentful Paint (how soon the main content shows), Interaction to Next Paint (how quickly the page responds to a tap or click) and Cumulative Layout Shift (how much the layout jumps while loading). Google publishes the thresholds for good, needs improvement and poor.

Does page speed affect Google ranking?

Yes, page experience including Core Web Vitals is a ranking signal, though content relevance matters more. Speed also affects how many visitors stay and, for Google Ads™, the landing page experience that influences your ad rank and cost.

How do you measure speed?

In the lab at phone width with a throttled network and CPU, and with Google's field data from real Chrome users where your site has enough traffic for it to exist. Codeinate reports both, because they can disagree and the reasons matter.

Do I need a new website to be fast?

Usually not. Images, scripts, fonts and server settings cause most slowness, and all four can be fixed on an existing site. A rebuild is the answer only when the platform itself is the problem, and Codeinate says so if it is.

How fast is codeinate.com?

Codeinate measures its own site the way it measures yours and publishes the numbers on the case studies page, including what is not good enough yet. That page is being rebuilt against a strict performance budget.

How long does it take to see results?

Lab numbers improve the moment a change ships. Google's field data is a rolling window of real visits, so it moves over the following weeks.

More from Codeinate

Google Cloud™ Partner

Codeinate is a Google Cloud™ Partner

Codeinate's products work inside the Google tools you already use

  • Google Sheets
  • Google Docs
  • Google Forms
  • Google Slides
  • Google Drive
  • Gmail
  • Google Calendar
  • Google Workspace Marketplace badge

Google Workspace Marketplace and the Google Workspace Marketplace logo are trademarks of Google LLC. Google Cloud, Google Sheets, Docs, Forms, Slides, Drive, Gmail and Google Calendar are trademarks of Google LLC.