Google PageSpeed Insights (PSI) is a page-level diagnostic for a live WordPress URL. It combines Lighthouse laboratory tests with Chrome User Experience Report (CrUX) field data from real visitors, so it can show both a reproducible test and what eligible users experienced over the previous 28 days. Use PSI to locate the bottleneck, not to choose a plugin or host: fix the failing WordPress layer, then verify the change across representative templates and in Search Console.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What PageSpeed Insights measures on a WordPress site
PSI answers two different questions for the exact URL you enter. Its field panel reports how real Chrome users experienced that page, while its Lighthouse panel runs a controlled test intended to expose causes you can reproduce. Google describes the service as providing “both lab and field data about a page.” A homepage test therefore says something about that homepage; it does not certify every post, archive, product, or checkout template.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →The distinction matters because a page can look excellent in Lighthouse and still fail Core Web Vitals in the field. Lighthouse uses a simulated device, network, cache state, and interaction pattern. CrUX aggregates eligible visits made by people using different devices, connections, browsers, caches, extensions, and locations. The two views are complementary rather than competing scores.
Field data: what visitors experienced
CrUX data is a rolling 28-day summary. PSI updates the displayed data daily, but each daily view still represents the preceding 28 days of observations. A deployment made yesterday is therefore mixed with older behavior until those older visits age out. A new or low-traffic URL may have too few eligible samples for a URL-level result. In that case PSI can display origin-level data, which describes the broader origin rather than the specific path. Always read the reported scope before treating a number as proof about one page.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Lab data: a repeatable investigation
Lighthouse runs a controlled audit for the URL and reports a performance score, timing metrics, and diagnostics. It is useful for isolating a large image, render-blocking CSS, a long JavaScript task, or a slow server response under the test conditions. Because those conditions differ from real visits, a lab improvement is evidence that the tested scenario changed—not evidence that the CrUX 75th percentile has already improved.
Core Web Vitals targets for 2026
For 2026, the Core Web Vitals are Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Google evaluates the 75th percentile of available field observations. A page passes when every available Core Web Vital is in the Good range under Google’s sufficiency rules.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →| Metric | Good at the 75th percentile | What it represents |
|---|---|---|
| LCP | 2,500 milliseconds or less | When the largest visible content element finishes rendering |
| INP | 200 milliseconds or less | Responsiveness across a user’s interactions during the visit |
| CLS | 0.1 or less | Unexpected visual movement while the page is loading and being used |
Use the three thresholds as pass/fail guardrails, not as an invitation to optimize one number while another deteriorates. A page with Good LCP and CLS but Poor INP does not pass Core Web Vitals. If a metric has no eligible field data, PSI applies its stated sufficiency rules; do not silently treat a missing measurement as a pass.
Supporting metrics
First Contentful Paint (FCP) is a useful clue about when the first visible content appears. Google’s Good upper bound shown in PSI documentation is 1,800 milliseconds. Time to First Byte (TTFB) is an experimental supporting metric with a Good upper bound of 800 milliseconds in that documentation. Neither replaces LCP, INP, or CLS for the Core Web Vitals decision. Use FCP and TTFB to narrow the investigation, then judge the outcome with the three required vitals.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
How to run a useful PSI check
- Choose representative URLs. Start with the homepage, one typical post, a category or archive page, and a conversion, product, or other high-value template. Include pages that share a template as well as pages with distinctive components such as a hero carousel, forms, video, or third-party embeds.
- Test the live canonical URL. Enter the public URL that visitors and search engines use, not an editor preview, a staging address, or a URL that immediately redirects. Record the date, protocol, path, and whether the page was logged in or personalized.
- Run mobile and desktop separately. PSI reports separate experiences. A page can meet desktop targets while mobile users encounter a slow hero image, a crowded main thread, or a different layout. Keep the device view with the result in your notes.
- Capture the field panel first. Write down LCP, INP, and CLS, each percentile or status shown, the sample-sufficiency message, and whether the scope is URL or origin. A field result is the baseline for deciding whether a change matters to users.
- Capture the Lighthouse panel for the same URL. Save the performance score, FCP, LCP, CLS, and the diagnostics and opportunities. Keep the test conditions consistent when comparing runs; otherwise a different simulated network or cache state can obscure a small change.
- Identify the limiting metric. Compare each field 75th-percentile value with 2,500 ms for LCP, 200 ms for INP, and 0.1 for CLS. Use FCP and experimental TTFB as supporting clues, not as substitutes.
- Map the clue to a WordPress layer. Inspect the template, theme CSS, plugin scripts, image dimensions and formats, font loading, cache behavior, server response, and third-party embeds implicated by the diagnostic.
- Change one bottleneck at a time. Record the change and timestamp, clear or warm the relevant caches consistently, and rerun the same lab test. Do not attribute a field improvement immediately; the 28-day window still contains earlier observations.
- Verify beyond the tested page. Use Search Console’s grouped Core Web Vitals report to check whether related URL groups and statuses changed. Test at least one page for every materially different template.
How to read the two PSI panels together
| Question | Panel to use | How to interpret it |
|---|---|---|
| Are real visitors experiencing a Core Web Vitals problem? | CrUX field data | Use the 75th-percentile LCP, INP, and CLS, sample sufficiency, and URL/origin scope. |
| What can I reproduce and inspect now? | Lighthouse lab data | Use the controlled timings and diagnostics to find a likely cause. |
| Did yesterday’s deployment fix the site? | Neither immediately | Lab data can change immediately; field data needs the rolling 28-day population to reflect the new behavior. |
| Are several templates affected? | Search Console grouped report | Use grouped URL data to see site-wide patterns, then return to PSI for a specific live URL. |
When the panels disagree, do not average them into a single verdict. A Good lab result with Poor field data commonly means that real visitors use slower phones or networks, encounter a different cache state, interact with expensive scripts, or land on variants the lab did not exercise. A Poor lab result with Good field data can occur when the controlled test is harsher than the traffic mix or when the tested URL has too few field samples and the displayed origin result is not page-specific.
Fixing a poor LCP result in WordPress
LCP is usually limited by the path to the largest visible element: server response, render-blocking resources, discovery of the element, or the element’s download and rendering time. Use the Lighthouse element identification and timing clues to determine which part dominates.
When the server or TTFB is the clue
- Check whether full-page caching is active for anonymous visitors and whether cache misses trigger expensive WordPress queries.
- Compare the response behavior of the tested URL with another page using the same template. A slow first byte across many templates points toward origin processing, database work, or delivery geography rather than one image.
- Confirm that cache invalidation is not removing a page from the cache on every request. After a configuration change, test both a cold and a warmed request consistently.
TTFB is an experimental supporting metric, so use its 800 ms Good upper bound as a diagnostic signal rather than a Core Web Vitals pass condition. If TTFB is high while the page’s static assets are reasonable, investigate server processing and delivery before rewriting front-end code.
When the LCP element is an image
- Serve the correct intrinsic dimensions for the rendered slot so the browser does not download a desktop-sized asset for a small mobile display.
- Use an efficient format and responsive sources where the WordPress media and theme support them.
- Do not lazy-load the image that is visible in the initial viewport; delaying the likely LCP resource can make discovery later.
- Reserve space and ensure the image is discoverable in the initial HTML or preload strategy only when measurement shows it is the actual bottleneck. Preloading too many assets competes with the page’s critical resources.
When CSS, fonts, or layout discovery is slow
- Remove unused theme or plugin CSS from the critical path where your build and cache process can do so safely.
- Load only the font weights and subsets the template needs, and define a fallback strategy so text can render while a web font arrives.
- Check that a consent banner, carousel, or script is not preventing the main content from being painted.
After each change, rerun the lab test and confirm that the identified LCP element and its timing actually changed. A higher lab score without a lower field LCP is not proof of a user benefit.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Fixing a poor INP result
INP reflects interaction responsiveness, not merely the initial load. A page can paint quickly and still respond slowly when a visitor opens a menu, filters a list, submits a form, changes a quantity, or scrolls through an interactive component.
Find the interaction that blocks the main thread
Use Lighthouse diagnostics and browser performance traces to look for long JavaScript tasks around event handlers, style recalculation, layout, and rendering. Identify whether the work comes from the theme, a plugin, an analytics or advertising tag, a page builder component, or a third-party embed. Field INP may expose interactions that a lab run never performs, so collect evidence from both panels before changing code.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows 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 reinstallWordPress changes that commonly reduce interaction work
- Defer nonessential third-party scripts until they are needed, while keeping consent and security behavior intact.
- Limit scripts to templates that use them instead of loading every plugin’s JavaScript site-wide.
- Break up long handlers and expensive synchronous calculations; process large lists in smaller chunks where the feature allows it.
- Reduce the number of active listeners and avoid repeatedly forcing layout while an interaction is in progress.
- Retest menus, search, filters, carts, forms, and other critical actions after optimization. A fast trace that breaks a key interaction is not a successful fix.
Because INP is a field metric, judge success by the 75th percentile over time. A single fast click in Lighthouse cannot establish that real users now meet the 200 ms target.
Fixing a poor CLS result
CLS measures unexpected movement. The most common WordPress causes are media without reserved dimensions, late-loading fonts, injected banners, and components that insert content above what the visitor is reading.
- Set width and height attributes or an equivalent aspect-ratio reservation for images, video, and embeds.
- Allocate space for consent notices, ad slots, related-content modules, and other elements that arrive after the initial HTML.
- Make sure font swaps do not change line wrapping enough to move headings and buttons. Test the chosen fallback and font-display behavior on mobile.
- Do not insert promotional bars or toolbar content above the page after the first paint unless the layout has reserved room.
- Use the layout-shift diagnostic to identify the moving node, then reproduce the sequence with cache and viewport conditions close to those in the report.
The Good CLS threshold is 0.1 at the 75th percentile. A page that looks stable during a quick desktop visit can still accumulate shifts on slower phones, so verify the field trend as well as the lab trace.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Using FCP and TTFB without misreading them
FCP at 1,800 ms or less is a useful indication that the first visible response is arriving promptly. If FCP is slow and LCP is also slow, start with server response, render-blocking CSS, fonts, and the critical image. If FCP is reasonable but LCP is poor, focus on the largest element and the resources needed to render it.
TTFB at 800 ms or less is an experimental supporting target in PSI documentation. A high value can point to origin processing, cache misses, or delivery distance, but a lower TTFB does not guarantee good INP or CLS. Treat it as one branch of the investigation, not a replacement for the three Core Web Vitals.
Why a WordPress score can change without a code change
PSI results vary when the test’s simulated network, device, cache state, or server response varies. Lighthouse is a single controlled observation, so run comparisons under consistent conditions and look for a repeated pattern rather than reacting to one score.
Field values change for a different reason: the CrUX dataset is a rolling 28-day population. PSI’s interface may refresh daily while still retaining many visits from before your deployment. A recent fix can therefore show an improved lab result and unchanged field status for days or weeks. Conversely, a field result may worsen after a release even if your own test device looks fast, because the affected traffic uses devices or networks your test did not represent.
PSI versus Search Console
Search Console groups similar URLs in its Core Web Vitals report. That makes it useful for seeing whether a status affects a class of pages, but the grouping can hide differences between templates and individual components. PSI is the better tool for inspecting one specific live URL and its diagnostics.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use both in sequence: identify a failing group in Search Console, select representative URLs from that group, inspect each with PSI, apply a template-level fix, and return to Search Console to see whether the group improves. A passing homepage cannot prove that every post, archive, or transactional template passes.
Comparing implementation options responsibly
PSI does not certify a particular WordPress plugin, hosting provider, CDN, theme, or optimization service. If you are choosing between implementations, compare the measured problem and the operational trade-offs rather than the vendor’s headline score.
| Decision factor | Questions to answer |
|---|---|
| Field impact | Did the relevant 75th-percentile LCP, INP, or CLS improve for the affected URL group? |
| Lab evidence | Did the diagnostic, element timing, or long-task trace change in the expected direction? |
| Template coverage | Does the change apply to the homepage, posts, archives, and conversion templates that need it? |
| Cache and rollback risk | How are cache invalidation, personalized pages, and rollback handled? |
| Server geography and TTFB | Does delivery reduce the measured response delay for the regions and visitors that matter? |
| Maintenance cost | Will updates, compatibility checks, and debugging add recurring work? |
Do not promise a particular PSI score from an infrastructure change. Measure the bottleneck first, make the smallest reversible change that addresses it, and keep a dated record of what changed.
A practical verification and troubleshooting checklist
- No field data appears: read the sample-sufficiency notice and check whether PSI has substituted origin-level data. Use lab diagnostics for immediate work, then wait for eligible traffic to accumulate.
- Mobile fails but desktop passes: inspect mobile image selection, font downloads, JavaScript cost, viewport-specific components, and server response on the mobile test.
- Lighthouse passes but CrUX fails: investigate device and network diversity, cache misses, real interactions, third-party scripts, and whether the URL-level sample represents a different template variant.
- CrUX passes but Lighthouse fails: repeat the lab run consistently and determine whether the simulated conditions are unusually harsh. Still fix clear diagnostics that affect real visitors; do not dismiss them solely because the field sample passes.
- The result does not change after a fix: confirm that the live URL serves the new code, purge the correct caches, rerun the same lab conditions, and remember that field data retains older visits for the rest of the rolling window.
- One page improves but the site does not: test another URL using the same template and review the grouped Search Console report. A page-level fix may not cover a plugin or layout used elsewhere.
What a credible 2026 PSI report should contain
For each tested URL, keep the date, mobile or desktop view, URL-versus-origin field scope, sample-sufficiency message, 75th-percentile LCP, INP, and CLS, Lighthouse timings and score, the top diagnostics, and the exact WordPress change made. Record cache state and any template or plugin dependency that could affect reproducibility. Recheck the same representative URLs after each change, then evaluate the field trend only after enough of the 28-day population reflects the new behavior.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
