What this checks
- Heavy HTML and asset payloads
- Oversized images
- Render-blocking third-party scripts
- Mobile performance risk
Spot oversized pages, heavy hero images and launch assets that make mobile visitors wait before they trust your product or convert.

Ask Richard about your report
Paid reports include direct founder help. If a finding is unclear, send it with the page, evidence and suggested fix attached, and Richard will explain what to do next.
Public pages only. No account, no card, no worker job.
Run the checker above for source-level page-weight risks, then use PageLens AI for browser-based screenshots, asset handling and page-level performance context.
Run complete launch scanTarget keyword: page weight checker
A page weight checker looks at how much data a visitor has to download before a page feels useful. Heavy HTML, oversized hero images, unused JavaScript, large fonts and stacked third-party scripts all make the first impression slower. That matters most on mobile networks, where a beautiful page can still feel broken if it waits too long to show content.
Good page weight is not about making every site tiny. It is about matching payload to purpose. A landing page should not ship megabytes of unused component code. A product screenshot should be compressed and sized for the viewport. Tracking scripts should be intentional, not inherited from every campaign you have ever run.
This check is useful after redesigns, AI-builder exports, CMS template changes and image-heavy launches. The goal is to catch obvious bloat early, then use a deeper audit for screenshots, route-level evidence and fix priorities.