Google has started rolling out the page experience update. It folds Core Web Vitals into ranking alongside mobile friendliness, HTTPS and the absence of intrusive interstitials. The rollout is gradual and finishes later this summer. Before anyone panics: this is a tiebreaker signal, not a replacement for relevance. A slow page with the best answer will still outrank a fast page with a worse one. Google explains the update on its page experience documentation page.
The three Core Web Vitals metrics, in plain language
Largest Contentful Paint asks how long until the main thing on the page appears. Target under 2.5 seconds. First Input Delay asks how long until the page responds to the first tap. Target under 100 milliseconds. Cumulative Layout Shift asks how much the page jumps around while it loads. Target under 0.1, which in practice means images and ads with reserved space.
Field data decides your score, not lab tools. That means real visits from real devices. For most Egyptian sites, those are mid range Android phones on mobile data rather than the laptop the developer tested on. The web.dev guide to Core Web Vitals explains how Google collects that data.
The triage order we use
First, layout shift. It is usually the cheapest to fix and the most annoying for users. Set width and height attributes on every image, reserve space for ads and embeds, and stop injecting banners above existing content. Second, Largest Contentful Paint. The cause is almost always a hero image that is too heavy or a font that blocks rendering. Compress, serve modern formats, preload the hero, and let text display while the font loads. Third, input delay. On marketing sites that is nearly always third party JavaScript. Audit the tag container and delete what nobody reads.
How to measure before and after
Write down a baseline before you touch anything. Pick your five most important templates. Use the homepage, a service or category page, a product or article page, the contact page and the checkout. Test each one with PageSpeed Insights and record the field data values, not only the lab score. Make one change at a time, wait for the field data to update, and compare. That discipline tells you which fix actually moved the number. It also stops a team from shipping ten changes and learning nothing. Landing pages deserve the closest look. Slow pages quietly undermine ad spend, as we explain in your ads are fine, your landing page is not.
What to ignore
Chasing a perfect score in a lab tool. Rebuilding the entire site because one metric is amber. And anyone selling a plugin that promises to fix the vitals in one click, because performance is a property of how the page is built, not something you can bolt on afterwards.
Do the triage, measure the field data again in four weeks, and move on to the content work that actually wins rankings. If you run a store, e-commerce SEO for Egyptian online stores covers that next step. If the audit shows the template itself is the problem, our website and app development team can tell you honestly whether a fix or a rebuild costs less over two years.
