Website performance: what a business owner should ask to measure

Website performance is easier to discuss when the question describes a visitor's experience. Can they read the introduction quickly? Does a tap produce a response? Does the contact button move while they try to use it? A single score cannot describe every part of that journey.

Know the three Core Web Vitals

Google's Web Vitals guidance identifies Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness and Cumulative Layout Shift for visual stability. Its good-experience targets are LCP within 2.5 seconds, INP at most 200 milliseconds and CLS at most 0.1, evaluated at the 75th percentile and considered separately for mobile and desktop.

Those are measurement targets, not a promise that a website will rank or generate enquiries. Use them alongside a review of the actual tasks visitors need to complete.

Ask what the report represents

A controlled test helps investigate a release. Real-user data describes how a site behaves across actual devices and visits. The two can differ, and a small site may not yet have enough field data for every report. Ask which kind of evidence supports the recommendation before comparing numbers.

Record the page, test conditions and date. A desktop homepage test is not the same exercise as a product page on a phone. Repeating a comparable test after a change is more useful than comparing unrelated screenshots of scores.

Start with the visitor's route

Review the introduction, navigation, enquiry form and a representative content page. Notice whether large media delays the useful information, whether controls respond promptly and whether content shifts after appearing.

An interiors website may need substantial photography. The question is how to preserve the detail visitors need while delivering appropriately sized images. An app-like page may need to examine the work happening when a person taps or types. The problem determines the improvement.

Request a prioritised change list

For each proposed fix, ask for the observed problem, affected pages, expected effect and a way to check it. Separate a confirmed bottleneck from a general best-practice suggestion. Identify which changes could affect visual quality, integrations or editing workflows.

Example: "The mobile introduction downloads an image far larger than its display size; prepare a smaller version and compare the same page before and after." That gives a developer a specific task and gives the owner a reviewable result.

Keep performance in the maintenance plan

New videos, tracking scripts, plugins and image uploads can change the experience later. Give editors simple media guidance and review important pages after significant additions.

Use our mobile review checklist to connect measurements to tasks. Our web development service can discuss performance checks as part of the build and handover scope.