Skip to main content
Lightify > Overview The overview page reports a performance score, your Core Web Vitals over time, and which pages and assets have been optimized.

​
Where the number comes from

Lightify injects a small collector into the cached copy of your homepage and records what real visitors experienced. Those measurements are averaged into a score. Two consequences follow from that, and both matter.

It reflects reality

Real devices, real networks, real distances from your server. Not a lab test on a simulated phone.

It needs traffic

A quiet site takes time to collect enough samples. A new install shows nothing at first, and that is correct rather than broken.
The collector is injected into the cache file, not into the live render, so the first uncached visitor is never measured. The score describes the experience of people who got a cached page, which is what you are trying to optimize.

​
The metrics

The weighting follows Lighthouse, with INP standing in for total blocking time and TTFB for speed index.

​
What to do about each

Too much JavaScript running on the main thread. Delay JavaScript execution is the direct fix, especially for third-party tags. Deferring helps too.This is 30% of your score and the metric most often ignored, because it only shows up when someone actually interacts.
Your largest above-the-fold element arrives late. Usually an image.Turn on preload critical images, make sure your hero is not lazy-loaded, and convert it to WebP. If your LCP element is text, the cause is usually a web font blocking render, so try use system fonts first.
Content moves as the page loads. Properly size images fixes the most common cause. Prevent layout shifts addresses the rest by not showing anything until it is settled.Also look for ads, embeds, and cookie banners injected above existing content, which no plugin setting can fix.
Your server is slow to respond. Page caching is the main answer, so first confirm it is actually active.If it is active and TTFB is still poor, the cause is upstream of the plugin: shared hosting under load, a distant server, or a slow database on uncached requests. An object cache helps the requests page caching cannot.

​
Why this disagrees with PageSpeed Insights

They measure different things, and both are right. A site can score 95 in Lightify and 60 in a Lighthouse lab test without either being wrong. Lighthouse deliberately simulates a slow device on a slow network; your visitors may be on fast phones near your server.
Use both. Lightify tells you what your visitors experienced. Lighthouse tells you what a specific page does on a bad device, which is better for finding a specific problem to fix. If they disagree wildly, the lab test is usually showing you the uncached experience.
PageSpeed Insights also shows real-user data from the Chrome UX Report when your site has enough traffic. That is the number closest to Lightify’s, and the two should broadly agree.

​
Optimized pages and assets

The overview also lists what Lightify has processed: which pages are cached, and which CSS, JavaScript, image, and font files have been optimized. Use it to confirm work is actually happening. If a template you expected is missing, it is either excluded, never visited since the last purge, or not cacheable. Preloading after a purge fills the gaps.

​
Getting alerted

Rather than checking this page, turn on score alerts and get an email when the grade changes in either direction.