Improve PageSpeed by measuring first, then fixing the largest causes of slow loading, delayed interaction, and layout movement. Run your page in PageSpeed Insights (PSI) for both mobile and desktop, separate real-user (CrUX) results from Lighthouse lab results, and retest after each significant change. Start with oversized images and render-blocking work before tuning minor details.
What PageSpeed Insights actually measures
PSI combines two kinds of evidence, and they answer different questions:
- Field data (CrUX): anonymized measurements from real Chrome users. It reflects the devices, networks, locations, and page experiences your visitors actually have, when enough data is available.
- Lighthouse data: a controlled simulation used for diagnostics and repeatable testing. It helps identify causes, but it is not a forecast of every visitor’s experience.
A single performance score is therefore not a complete diagnosis. Record the URL, test date, mobile and desktop results, Core Web Vitals status, and the leading opportunities before changing anything.
Use Core Web Vitals as the outcome
Focus on the user-facing metrics rather than chasing a score alone. The good thresholds documented in current PageSpeed guidance are:
Recommended Free Tools
#1 Best Overall
| Metric | What it represents | Good result | Typical causes of a poor result |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How quickly the main content becomes visible | Under 2.5 seconds | Large hero images, slow server response, render-blocking CSS or scripts |
| INP (Interaction to Next Paint) | How quickly the page responds throughout a visit | Under 200 milliseconds | Long JavaScript tasks, excessive event handlers, third-party code |
| CLS (Cumulative Layout Shift) | How stable the layout remains while loading | Under 0.1 | Images or ads without reserved space, late-injected content, changing fonts |
Field status is the better indication of whether visitors experience a problem. Use Lighthouse opportunities to find likely causes, then confirm improvement in field data as it accumulates.
Fix the largest bytes first: images
Images are often the fastest way to reduce transfer and improve the point at which useful content appears. Optimize the file and the way it is delivered, not just its filename.
Choose an efficient format and quality
- Use WebP or AVIF where your browser-support requirements allow it, with a fallback for clients that need one.
- Adjust compression quality until visual differences are acceptable; maximum quality is rarely necessary for a page image.
- Remove metadata and other data that does not contribute to display.
Serve the right dimensions
Do not send a desktop-sized original to a narrow phone. Generate responsive variants and let the browser select an appropriate source with responsive image markup. Match the intrinsic dimensions to the rendered slot so a 400-pixel card does not download a 2,400-pixel asset.
Prioritize and defer deliberately
- Load the above-the-fold hero image early when it is the LCP element, but keep it appropriately sized.
- Lazy-load images that are below the initial viewport.
- Reserve width and height (or an equivalent aspect-ratio box) for every image, advertisement, and embed to prevent layout shifts.
Reduce JavaScript work and interaction delay
JavaScript affects both loading and responsiveness: the browser must download, parse, compile, and execute it on the main thread.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- Vinyl Hard Cover: Durable grey vinyl hard cover provides long-lasting protection for your notes and records
- 200 Sewn Pages: Features 200 sewn pages with lined rule for organized and secure documentation
- Oilfield Book: Specifically designed for oilfield use with standard industry specifications
- Directional Drilling: Tailored for directional drilling operations and pipe tally marking on oil rigs
- Standard Driller Size: Measures 8.25 inches tall and 3.5 inches wide, the dimensions used by professional drillers
Remove work users do not need
- Delete unused libraries, components, polyfills, and analytics tags.
- Split large bundles so a route loads only the code required for that view.
- Replace expensive client-side rendering with server-rendered or progressively enhanced content when practical.
Defer noncritical scripts
Do not place synchronous scripts in the document head unless a specific dependency requires them. Defer or asynchronously load noncritical application code, advertising, chat widgets, A/B testing, and other third-party tags. Keep essential code small enough that it cannot monopolize the main thread during startup.
Find long tasks
In Chrome DevTools, open the Performance panel, record a page load and representative interaction, and inspect long tasks and scripting time on the main thread. A high INP can come from a short handler followed by expensive rendering, so examine the entire interaction rather than only the event listener.
Simplify the critical rendering path with CSS
CSS needed to display the initial viewport is part of the critical path. Remove selectors and frameworks that the page never uses, reduce the size of critical styles, and avoid making the browser wait for styles that belong to later sections.
- Inline or otherwise prioritize only the minimum critical CSS when your delivery stack supports it.
- Load noncritical styles after the initial render instead of blocking it.
- Audit component and utility bundles for duplicated rules.
- Check that font loading does not hide text or trigger large swaps; reserve space and choose a fallback strategy that keeps layout stable.
Retest visual stability after every CSS or font change. A smaller stylesheet is not an improvement if it causes content to jump.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #3
- EASY FORGOT YOUR PASSWORD? - This small password journal allows you to save all your passwords, account & login details in one place. Managing your online web account information & user data safe. The set comes with 2 password logbooks one to keep at work and one at home. Never forget your passwords again.
- SIMPLE & PRACTICAL - Wire bound password journals with durable plastic cover the sturdy plastic cover resists rips, tears, and folds. Features alphabetic tabs to help organize your data and navigate your accounts easily.
- POCKET SIZE - 2 pack 5"x7" and 3.5"x5.25" mini password journal with A-Z tabs and 120 pages each, lots of space, easy to write, there's even room to add to your password journal.
- DURABLE - Thick frosted poly covers will protect your password book from damage. Made out of premium paper great for fountains pens and ink. No feathering and bleeding. Thick paper & Strong Binding.
- GUARANTEED QUALITY - High quality, heavy-duty and BUILT TO LAST! Made by Excello Global Products. We are a family owned USA company and we have been making quality products for over 50 years.
Improve delivery with caching and a CDN
Browser caching for repeat visits
Set cache policies according to how often a resource changes. Version or fingerprint static files so they can be cached for a long time, while HTML and frequently changing API responses use shorter freshness windows. When a file changes, publish a new versioned name rather than relying on every browser to discover an update immediately.
CDN coverage for distributed visitors
A content delivery network can serve cacheable assets from locations closer to visitors, reducing network distance and origin load. Evaluate whether your audience is geographically distributed, which assets can be cached safely, how purges work, and what happens on a cache miss. A CDN does not fix an oversized image, slow database query, or excessive JavaScript by itself; it improves delivery after the payload and caching policy are sound.
Check cache behavior
- Verify that static assets return the intended cache headers.
- Confirm that compression is enabled for text resources.
- Measure both cold-cache and repeat-visit behavior.
- Test visitors in your main geographic regions, not only from the origin server’s location.
A repeatable PageSpeed improvement workflow
- Establish a baseline. Run the production URL in PSI on mobile and desktop. Save the date, device context, field-data availability, Core Web Vitals status, score, and top opportunities.
- Map the critical path. Identify the LCP element, blocking requests, largest transferred files, and scripts that consume main-thread time.
- Optimize images. Convert suitable assets, resize them for their rendered slots, provide responsive sources, reserve their layout space, and defer below-the-fold media.
- Reduce scripting. Remove unused JavaScript, split bundles, defer noncritical code, and inspect long tasks during real interactions.
- Trim and sequence CSS. Keep initial styles small, defer noncritical styles, and verify that fonts and late content do not move the layout.
- Configure caching and delivery. Apply appropriate browser cache headers, fingerprint static files, compress text, and assess CDN placement and invalidation.
- Retest under comparable conditions. Use the same URL and mobile or desktop context, then compare the changed metric and opportunity rather than relying only on the overall score.
- Monitor field results. Continue watching CrUX data and set alerts in a performance-monitoring system for regressions in loading, responsiveness, and stability.
How to choose what to fix first
When several opportunities compete for engineering time, rank them using these axes:
| Question | Why it matters |
|---|---|
| Does field data show the problem? | Real-user evidence tells you whether visitors are affected, while lab data helps explain why. |
| Which experience is harmed? | Prioritize LCP issues for loading, INP issues for interaction, and CLS issues for stability. |
| How much can be removed? | Bytes saved and main-thread milliseconds provide a concrete estimate of impact. |
| What is the implementation risk? | Changes to checkout, navigation, advertising, and personalization need functional and visual checks. |
| Will caching remain correct? | Long-lived caching requires reliable versioning and an invalidation plan. |
| Who benefits geographically? | A CDN may have little effect for a local audience but substantial value for visitors far from the origin. |
| Can the result be monitored? | Choose changes whose effect can be verified in repeatable lab tests and ongoing field reporting. |
Troubleshoot common symptoms
“My mobile score is much worse than desktop.”
Compare the mobile waterfall and Lighthouse trace for oversized images, slower network transfer, render-blocking resources, and long JavaScript tasks. Mobile devices have less bandwidth and less processing capacity, so a bundle that appears acceptable on desktop can still delay INP and LCP.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- Used Book in Good Condition
“The score is high, but visitors still complain.”
Check whether PSI has sufficient CrUX data for the page and inspect the field distributions, not only the lab score. Real visitors may use older phones, different networks, or regions unlike the Lighthouse simulation. Also test the specific flow they report, such as opening a menu or submitting a form.
“Lighthouse improved, but Core Web Vitals did not.”
Lab conditions can improve before the field dataset reflects the change. Confirm that the production deployment is live, compare like-for-like URLs and contexts, and continue monitoring CrUX. A lab gain that does not address the field bottleneck may simply optimize a different part of the page.
“CLS is failing even though the page looks fine on load.”
Record a full load and interaction, then identify late-loading images, ads, embeds, banners, or fonts that change dimensions. Give each variable element reserved space and avoid inserting content above material that is already visible.
What a successful optimization looks like
Success is a faster, more responsive, more stable experience for real visitors—not a permanently perfect laboratory score. Keep a dated baseline, make one material class of change at a time, verify that the page still works, and watch field LCP, INP, and CLS after deployment. Treat PSI as a diagnostic loop: measure, prioritize, change, retest, and monitor.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
