What this checks
- Heavy HTML and asset payloads
- Oversized images
- Render-blocking third-party scripts
- Mobile performance risk
Performance · page weight checker
Page weight checker
A website page weight checker measures the bytes a webpage needs to load and shows where that weight comes from, including images, scripts and HTML. Enter a public URL below to find oversized assets and likely mobile performance pressure. Use the result as a diagnostic starting point alongside real-user and lab speed metrics.
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.
Page weight first pass
Checks HTML size, image/script counts and obvious source-level weight risks.Public pages only. No account, no card, no worker job.
Why it matters
- Slow first impressions hurt conversion.
- Large generated images are a common AI-builder failure mode.
- Performance problems often repeat through templates.
How to use it
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.
Get Launch Pass — $29Example result
What a free performance check can surface.
Review before launch
Heavy HTML and asset payloads
The free tool gives you a visible first-pass signal. A paid PageLens AI report adds page evidence, severity, screenshots, ownership context and a scoped repair prompt.
What the full scan adds
- Desktop and mobile screenshots for every priority finding.
- Severity, owner impact and fix acceptance criteria.
- Markdown repair prompts for Cursor, Codex, Lovable, Bolt and other builders.
- Re-scan proof when the page improves.
Copy-paste fix prompt
Review this page for page weight checker. Start with this finding: "Heavy HTML and asset payloads". Make the smallest production-safe fix, preserve the existing design, then list verification steps for desktop, mobile and crawler-visible HTML.
Upgrade path
Ship Check
$0
Verdict and top three launch risks
Launch Pass
$29
Key flows, AI-ready fixes, and verification
What the result means
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.
Limits of this check
Transferred bytes vary with caching, compression, personalization, geography and third-party requests. Page weight is important, but it is not the same as Core Web Vitals or experienced speed.
Why page weight is one of the easiest speed problems to miss
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.
Frequently asked.
- What is page weight?
- Page weight is the total amount of data a browser downloads to load a page, including HTML, CSS, JavaScript, images, fonts and third-party resources.
- Why does page weight affect conversion?
- Large pages take longer to load, especially on mobile. Visitors may bounce before they read the offer, and paid traffic becomes less efficient.
- What usually makes a page too heavy?
- Oversized images, unused JavaScript, multiple analytics tags, video backgrounds, large fonts and duplicated scripts are common causes.
- How do I reduce page weight quickly?
- Start by compressing images, removing unused third-party scripts, lazy-loading non-critical media and shipping only the JavaScript needed for the current page.