What changed on my page? How PageWeight spots it
When a tracked page gets heavier or slower, the Recent changes panel in PageWeight now shows what changed: files that were added or removed, files that grew or shrank, and requests that started failing. A change is listed only after it has held for three checks in a row, and it stays on the list for 30 days.
Why isn’t a score chart enough?
A performance score tells you that something got worse, not what. When a page drops from 82 to 64 overnight, the cause is usually one file: a new chat widget, a hero video, an analytics script that doubled in size, or a plugin update. Finding it means comparing two waterfalls by hand, and that only works if you saved the “before” one.
PageWeight already stores every check of every tracked page, so it can do that comparison for you.
What does the Recent changes panel show?
- Files added or removed, such as a new third-party script or a dropped font.
- Files that grew or shrank by at least 10 KB and 10%.
- Requests that started failing with a 4xx or 5xx status. Files from one host that broke at the same moment are shown as one incident.
- Third-party domains the page started or stopped loading from.
Each change shows when it started and whether it still holds: a broken request is marked as still failing or recovered, and an added file as still present or gone.
How does it avoid false alarms?
Most pages don’t load exactly the same files twice. Homepage images rotate, ad networks swap scripts, and build tools rename files on every release. A plain comparison of two checks flags all of that as change. When we compared consecutive hourly checks on 12 real sites over 12 days, nearly a third of all pairs looked like a significant change. The causes were rotating content and renamed files, not edits to the pages.
So PageWeight is stricter:
- A change has to stick. The new state must hold for three checks in a row, after a steady stretch in the old one. On hourly plans that takes about three hours; on the free plan’s daily checks, about three days.
- Renamed files stay the same file. A script whose name carries a version or a hash is matched across releases, so an upgrade reads as one file that changed size, not as one file removed and another added.
- Rotation is summed up, not listed. When a site swaps images or ad scripts of about the same size, you get one line such as “12 images swapped” that you can expand, instead of 24 separate entries.
- Files that only load sometimes aren’t reported as changes, and changes under 10 KB are counted rather than listed.
Where can you see it?
Open a tracked URL’s history in your dashboard. The Recent changes panel also appears on share links, in both the technical and the client version, and in printouts. On Solo and Agency plans, the Monday email includes a short “Changes this week” section for each page.
It works on every plan, including the free one with 3 tracked pages and daily checks. Hourly checks on paid plans catch a change sooner, but the list is the same.
What doesn’t it do?
The Recent changes panel compares the files a page loads, as seen by Google PageSpeed Insights. It doesn’t see text or layout edits that keep the same files, and it can’t tell you why a file changed. It tells you which file to look at first, which is usually the slow part. For what each file type costs you, see what page weight is and how third-party scripts slow a site down.