Site speed and SEO: what to measure besides a pretty score

A pretty site that takes several seconds on a phone loses both leads and search. Core Web Vitals are a useful language: paint, layout stability, response. The awkward part is that a lab report and the feeling of a person with an ordinary phone often disagree. Chasing a round number on the homepage without opening a catalog page is almost useless.

Where slowness usually hides

• Images with no dimensions and no compression. They also shove the layout while they load.
• A pile of analytics and chat scripts connected "so they exist". Each one waits on the network.
• Fonts that block text. A person sees an empty screen while the score can still look tolerable.
• The catalog and the product page, not only the homepage. Search looks where buyers go.

Technical optimization is these fixes and the order of the queue, not "tricks". If the site is only being ordered now, a budget for images, fonts and scripts is cheaper to put into the layout than to rewrite the storefront a quarter later. Field data from real people's browsers matters more than one run from a fast server.

Lexora combines development and technical SEO: structure, meta, speed and basic form hygiene. We hand over the fix list in priority order, not sorted as "fix all 40 notes from a plugin".