OneWebDesk

Page Weight Analyzer

Analyze a page's HTML size and the count/type of referenced resources.

Page Weight Analyzer shows the HTML document size (in bytes) of a URL together with how many external resources it references. It counts script, stylesheet and image tags by type so you can quickly gauge how heavy a page's structure is.

The tool only fetches and analyzes the HTML document itself on the server — it does not download individual resources like scripts or images. So the KB figure is the size of the HTML document, and the resource counts are based on the number of references declared in that document. For full transfer size, pair this with your browser's Network tab.

How page weight and request count affect performance

Slow pages usually come from two factors: too many bytes to download, and too many files (requests) to fetch. A large HTML document delays first paint, and the more scripts, stylesheets and images a page references, the more extra requests the browser must handle, which slows rendering.

  • HTML size: longer markup takes longer to parse and transfer. Excessive inline styles and scripts bloat the document.
  • Script count: many external scripts increase download, parse and execution cost, and raise the chance of render blocking.
  • Stylesheet count: scattered CSS files delay the start of rendering. Consider bundling and merging.
  • Image count: more image tags mean more requests and transfer. Consider lazy loading and modern formats.

How to read the numbers

The counts here reflect references declared in the HTML, not the bytes actually transferred. A script referenced multiple times, or resources loaded only conditionally, are all counted as static tags. A high number is not automatically a problem, but dozens of script or image references on a single page is a signal to review bundling, lazy loading and caching.

  • For accurate transfer size and load time, use the browser Network tab or a field-data performance tool.
  • If the HTML is unusually large, check whether server-side rendering is embedding too much inline data.
  • To cut text transfer size, check whether gzip/brotli is on with the compression check, and if the page is image-heavy, review the best format with the image format recommender.

Frequently asked questions

Can it tell me the size of each resource?
No. The tool fetches only the HTML document, so the KB figure is the HTML document size. It does not download individual resources like scripts or images — it only counts the references declared in the document.
Why does the reference count differ from real requests?
It counts only tags written statically in the HTML. Resources added dynamically by JavaScript, conditionally loaded, or referenced more than once can make the real browser request count differ.
Where is the URL I enter sent?
Analysis runs on the OneWebDesk server, which fetches only the HTML over a safe HTTP request. SSRF blocking, timeouts and a response size cap apply, and results are cached for 60 seconds. Nothing is shared with third parties.
Are very large pages fully analyzed?
Only up to a response size cap (about 2MB) is read. Larger HTML is analyzed in truncated form, and in that case the result shows a 'partially analyzed' notice.

Related tools