Slow Website: What Is Worth Fixing First?
Use real visitor data and diagnostic tests to decide which website speed problems deserve attention, without chasing a perfect score.

The short answer: measure a few important pages, find the biggest problem visitors actually encounter, and fix that before replacing your host or rebuilding the site. A slow page can be caused by oversized images, too much JavaScript, content that shifts while loading, a slow server response, or a combination. A single score does not tell you which one to tackle first.
What the three Core Web Vitals mean
Core Web Vitals are three measures of loading, responsiveness, and visual stability. Google's current Web Vitals guide gives these “good” targets, assessed at the 75th percentile of page loads and separately for mobile and desktop:
- Largest Contentful Paint (LCP): how long it takes for the largest main item in view, often a headline or large image, to appear. Good is 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds visually after a tap, click, or key press. Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much visible content unexpectedly shifts during the page’s lifetime. Good is 0.1 or less.
These are user-experience measures, not a diagnosis by themselves. A page can feel sluggish because its main image takes too long to appear, because a menu does not respond promptly, or because an ad or embedded element pushes the page around.
Measure before changing things
Run PageSpeed Insights on your homepage and one or two important pages, such as a service page or contact page. Check mobile and desktop. Look at both parts of the report:
- Field data comes from the Chrome User Experience Report (CrUX) and reflects real visitors over a rolling 28-day period. It is the better view of what people have experienced, when enough data is available.
- Lab data is a Lighthouse test in a controlled simulation. It offers diagnostics you can investigate, but it is not a record of every visitor's device, connection, or behavior.
The numbers can differ because one is real-world history and the other is a simulated run. Field data may be missing for a page with too few samples; PSI may show data for the whole site instead, or no field data at all. Missing data does not mean the page is fast. Because PSI field data covers a 28-day window, a recent fix may take time to show up clearly in that report.
Use the lab report to find clues, then compare with field data when it exists. Do not treat one run, one device, or the green performance score as the whole story.
A practical order for the first fixes
Start with what the report and the page itself point to. The steps below are recommendations, not guaranteed outcomes.
- If the main content appears late, check the largest image first. A large hero photo may be much bigger than the space it occupies. Ask whether it can be resized to the display dimensions, compressed without visible damage, or delivered in a suitable modern format. web.dev's image performance guide explains that sending fewer bytes, for example by serving correctly sized images, reduces download time, and that modern image formats can shorten load time and may improve LCP. If the main image is lazy-loaded or only discovered after JavaScript runs, ask a developer to check that too. Do not lazy-load the image that is supposed to appear first; save lazy-loading for below-the-fold images.
- If taps or menus feel delayed, review scripts and widgets. Chat, booking, maps, video, advertising, and tracking tools can add code from outside providers. Too much JavaScript can keep the browser busy instead of responding to a visitor. Google's Core Web Vitals optimization guide recommends removing unnecessary JavaScript and reviewing unused tag-manager code. First identify what each script does and who relies on it. Do not remove payment, booking, consent, or analytics tools without checking the consequences.
- If the page jumps, reserve space for content. Images, ads, and embeds can move nearby text when their final dimensions arrive. Ask for image width and height, or a reserved area for content whose size is known only later. This can address CLS without changing the site's overall design.
- If the first response is slow across several pages, investigate hosting and caching. A slow Time to First Byte (TTFB) means the browser waits longer for the first response from the server. It is a useful clue, not proof that you need a more expensive hosting plan. Ask your developer or host to check server response time and caching; a content delivery network (CDN) may help in some setups. Google's guide discusses caching and CDNs as ways to reduce TTFB. Before deciding that hosting is the cause, look for the same delay across several important pages.
- Retest the same pages after each meaningful change. Keep a short note of the issue, the change, and whether the lab diagnostics or field data changed. Changing one likely cause at a time makes it easier to tell what helped and what created a new problem.
If the report shows several issues, prioritize the one that affects the most important page or blocks the main task a visitor came to do. A homepage hero image may matter more than a small image far down a page; a slow booking interaction may matter more than a slightly imperfect score.
What a good score can and cannot tell you
Google says Core Web Vitals are used by its ranking systems, but good results in a report do not guarantee top search rankings. Its page experience guidance also says there is more to page experience than these metrics. Treat the report as a way to find user-facing friction, not a promise of more traffic or a reason to pursue a perfect number.
Limits of this advice
PageSpeed Insights is a starting point, not a complete performance investigation. Results vary with device, network, page content, and third-party services. Without access to your site and its hosting, no one can tell from a general article which component is responsible. Ask whoever manages the site to explain the evidence behind a proposed change and to check that important forms, booking, payment, and tracking still work afterward.
For deciding whether the work calls for repairs or a larger project, see when to redesign versus repair.
Evidence
Sources
- Web Vitals | Articles | web.devGoogle web.dev · Retrieved
- About PageSpeed Insights | Google for DevelopersGoogle · Retrieved
- Image performance | web.devGoogle web.dev · Retrieved
- The most effective ways to improve Core Web Vitals | Articles | web.devGoogle web.dev · Retrieved
- Understanding Google Page ExperienceGoogle · Retrieved
A useful next step
Keep a useful record
Use the ownership checklist to organize the accounts and people involved in your site.
Open the ownership checklist