A slow site loses people before they read a word. On a mobile connection in a busy mall or on the road, three extra seconds feels like a broken page, and a visitor who leaves never becomes a customer. Google also uses page experience as one of many signals.
You do not need to be technical to improve this. You need to know three names, one tool and a short list of fixes.
Core Web Vitals measure three things on real phones: how fast the main content appears (LCP, aim for 2.5s or less), how quickly the page reacts to taps (INP, 200ms or less), and whether it jumps around (CLS, 0.1 or less). Most fixes are about images and fewer scripts.
The three metrics in plain language
Each metric answers one question a visitor would ask.
- LCP (Largest Contentful Paint): how long until the biggest thing on screen, usually the hero image or headline, appears. Good is 2.5 seconds or less.
- INP (Interaction to Next Paint): when I tap a button or menu, how fast does the page respond? Good is 200 milliseconds or less.
- CLS (Cumulative Layout Shift): does the page jump while loading, making me tap the wrong thing? Good is 0.1 or less.
Measure first, on mobile
Open PageSpeed Insights, paste your address and read the mobile tab, not the desktop one. Look first at the field data from real visitors if it is shown, then at the list of opportunities below. Test your home page and your most important landing page, and note the numbers so you can compare after changes.
Fix images first
Images are the heaviest part of most small business sites and the usual cause of slow LCP. Fixing them gives the biggest gain for the least effort.
- Use modern formats such as WebP or AVIF, and never upload a photo straight from a phone at full size.
- Serve the image at the size it is shown, not four times larger.
- Load the hero image first, and lazy-load images further down the page.
- Always give images a width and height so the page does not jump (this also fixes most CLS).
Cut scripts, fonts and clutter
Every chat widget, tracker, slider and extra font adds weight and slows taps. Keep only what earns its place. Use one or two font families, and for Arabic sites choose one Arabic face rather than three. Avoid auto-playing video above the fold.
Slow INP usually means too much JavaScript running when the user taps. Fewer third-party scripts is the simplest cure.
Let Uttra help, then re-test
Because Uttra generates a clean, lightweight site you can keep adding to, you can ask for the fixes directly: Compress all images on the home page, set width and height on every image, lazy-load images below the first screen and remove the unused slider. Publish, wait for new data, and re-run PageSpeed Insights.