Use Lighthouse as a repeatable troubleshooting tool: audit an important WordPress page, save the baseline, investigate the report’s clues, make one change, then rerun under the same conditions. Its findings identify potential issues on the page you tested; they do not prove that a particular plugin, host, or optimization will help your site.
Choose a representative page and configure the audit
Start with a page tied to a real user journey: for example, a landing page, article, or product page. One URL can reveal useful problems, but it cannot establish how every page or template performs.
As an Amazon Associate I earn from qualifying purchases.
Lighthouse can audit public pages and pages that require authentication. You can run it in Chrome DevTools, from the command line, as a Node module, or with Lighthouse CI. For a first audit, Chrome DevTools is a straightforward place to begin. See Lighthouse overview and Lighthouse variability.
Recommended Free Tools
- Open the page in Chrome and launch DevTools.
- Open the Lighthouse panel, choose the device that matches your question—mobile for a mobile investigation, desktop for a desktop comparison—and select the relevant categories: Performance, Accessibility, Best Practices, or SEO.
- Review the storage conditions before running. Clearing storage models a first-time visitor; a repeat-visit investigation may need a different setup.
- Run the audit and keep the report with a note of the page, device, categories, and storage conditions.
If a run errors or behaves unexpectedly, Chrome recommends trying a clean Incognito window without other tabs; browser extensions can interfere with audits. Keep the setup consistent when comparing results.
#1 Best Overall
- EXPAND YOUR HORIZONS: 3440 x1440 UltraWide QHD (WQHD) resolution with 21:9 aspect ratio for efficient productivity
- CURVED IMMERSION: The 1500R radius curved VA panel allows for more immersion and better color accuracy. It can also help alleviate eye strain during long hours of working
- RICH COLORS FOR WORK AND PLAY: Ultra Wide-Color technology produces true-to-life images and a wider spectrum of colors with sRBG 123.24 percent , NTSC 99.25 percent color gamut area coverage
- WINDOWS HELLO WEBCAM WITH NOISE-CANCELING MIC: Comes with built-in 5MP webcam, noise canceling microphone, and speakers, perfect for remote working. The webcam is equipped with advanced sensors for Windows Hello facial recognition, which conveniently logs you into your Windows devices in less than 2 seconds
- ONE CABLE IS ALL YOU NEED: USB-C docking transfers high-speed data, high-resolution video signal, and power to your laptop (up to 65W of Power Delivery support) via a single USB-C cable. Play and work in high resolution while simultaneously charging your notebook
Save and read a baseline before changing WordPress
Save the initial report or record its key results before editing the site. A baseline gives you something meaningful to compare against and helps distinguish a change’s effect from a different test setup.
Read the metrics alongside the page-load screenshots, Opportunities, Diagnostics, and passed audits. Opportunities describe potential performance improvements; Diagnostics help investigate what may be causing a problem. Treat a failed audit as a lead to check on the tested page, not as a one-click prescription or proof that the same issue affects every URL.
Rank #2
- Dell UltraSharp U2410 - LCD display - IPS- 24" - widescreen - 1920 x 1200 / 60 Hz
Lighthouse reports Performance, Accessibility, Best Practices, and SEO. Choose categories according to the experience you want to improve, and inspect the underlying metrics and audits rather than optimizing only for the overall Performance score. Lighthouse’s scoring weights have changed over time, so a particular score is not a guarantee of a good experience for all visitors. See Lighthouse performance scoring.
Free tools Windows power users keep installed
One-click scans. No signup required.
Trace the finding to the likely source
Use the audit details to decide what to inspect next. A finding may point toward code, assets, the server response, or a third-party service; establish the connection to the page before changing the site.
Rank #3
If the main thread is busy
The browser’s main thread parses HTML and CSS, evaluates and runs JavaScript, renders the page, and handles user events. When it is occupied, the page may respond slowly to interaction. Inspect script work, third-party code, and complex style or layout work before choosing a fix. Chrome’s main-thread work breakdown explains the diagnostic.
If JavaScript execution stands out
JavaScript has network, parsing, compilation, execution, and memory costs. Trace the scripts involved to the theme, a plugin, or an external service before disabling anything. Depending on what the report reveals, possible investigations include sending only necessary code, splitting code where appropriate, minifying or compressing it, removing unused code, and using caching. See Chrome’s JavaScript execution guidance.
Rank #4
- Exclusively compatible with N scale locomotives, this test stand works with most standard N gauge models, making it a flexible and practical addition to any hobbyist’s collection.
- With a straightforward structure and simple connection design, the rolling test stand can be assembled and put into use quickly without complicated tools or procedures.
- Manufactured from premium metal materials, the test bench offers excellent stability and wear resistance, ensuring reliable performance even with frequent daily use.
- This dedicated test treadmill lets you safely debug, test speed and inspect locomotive performance, greatly upgrading the fun and professionalism of your model train hobby.
- This is not a toy. Not intended for use by children under 14.
If requests or transferred bytes are high
Resource-summary diagnostics show requests and transferred bytes by resource type, including third-party contributions. They do not directly change the Performance score, although reducing requests or transfer size may affect other metrics. Use the report to identify what is actually contributing—such as images or other media, fonts, the document, or third-party assets—rather than reducing assets indiscriminately. See resource summary guidance.
If the document response is slow
A slow response before the page’s content arrives calls for investigation of the server and WordPress setup, not only front-end assets. Chrome’s WordPress guidance discusses options including a lightweight theme, full-page caching or static delivery, removing unnecessary plugins, managed or dedicated hosting, PHP OPcache, and memory caching such as Redis or Memcached. These are possibilities to assess against the actual bottleneck, not a universal checklist or a guarantee of improvement. See Chrome’s WordPress server-response guidance.
Best Value
Audit wording can vary by Lighthouse version. The server-response-time guide says that, as of Lighthouse 13, the response-time audit moved into the Document request latency insight. Follow the label and details in the report you actually ran rather than relying on an older audit name.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Change one thing, then rerun comparably
Choose a single change that addresses the evidence you found. For instance, if a specific plugin appears to add costly scripts to the tested page, investigate that plugin’s settings or behavior before considering disabling it. Check compatibility and the effect on site functions as well as the audit.
- Record the exact change you made.
- Rerun Lighthouse on the same page, with the same device, categories, and relevant storage conditions.
- Compare the specific metrics and observations that motivated the change, as well as the score.
- Keep, adjust, or revert the change based on the result and the site’s functionality.
Chrome’s DevTools guidance recommends auditing after each change to understand its isolated effect. If several plugins or settings change between runs, it becomes harder to tell which one affected the report. See guidance on comparable Lighthouse runs.
Repeat across important templates and watch for regressions
Once you have worked through one page, audit other high-impact pages or templates. An article, landing page, and product page may load different assets or trigger different scripts, so a fix that helps one is not automatically a fix for the others.
Teams that want to catch regressions can consider Lighthouse CI. A collection of repeatable audits can help track changes over time, but it still does not by itself establish how every visitor experiences the site. See Lighthouse’s available run modes.
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.




