Nebula Lighthouse discovery: when the product count is mostly page-title noise
Nebula Lighthouse discovery: when the product count is mostly page-title noise
Tag archive
Nebula Lighthouse discovery: when the product count is mostly page-title noise

Lantern treated high-priority modulepreloads and fonts as if they blocked paint. Lighthouse 13.6 reads Chrome’s render-blocking signal instead. Here is what agencies should stop undoing.
A practical walkthrough for bulk Lighthouse audits from an XML sitemap, with real output and the trade-offs between doing it locally and in the cloud.
Core Web Vitals are ranking signals, but most teams still optimize them like lab-only scorecards....
Tools do not fix performance. Systems do. Most developers treat performance as a checklist: run a...
In October 2026 we measured the websites of 4,918 US HVAC companies that advertise on Google. We...

A short rule list for loading="lazy": below the fold yes, LCP hero no, and retest after every theme or plugin change that touches images.

A green compression toggle is not an LCP fix. Confirm Content-Encoding on the critical path, then check the LCP element and Time to First Byte that still dominate the lab run.

Lighthouse 13.6 changed how PageSpeed Insights simulates FCP and LCP. A higher lab Performance score can appear when the HTML did not move. Here is a short check.

You run PageSpeed Insights and get a 34 on mobile. Panic? Not yet. That prominent Performance score...

Same URL, same Lighthouse engine: different CPU, throttling, and cache. Compare tools fairly instead of merging the scores.
If Lighthouse Accessibility (or axe) flags color-contrast or missing focus styles, you usually do not...