Page weight
x-ray
Paste your page's HTML and see the skeleton of what it loads - every script, stylesheet, image, font and embed, with the heavy ones flagged and a prioritized fix list. No network test needed; it runs entirely in your browser.
Paste. Scan. Lighten.
Honest note: without a network test this tool cannot know real transfer sizes - it counts what the HTML asks the browser to fetch. That structural picture is where most weight problems hide. For measured bytes, run the same page through your browser's DevTools Network tab afterwards.
Estimated cost table
| Resource | Count | Requests | What it costs |
|---|
Every external resource
Yetty serves your pages as clean static HTML on a global CDN - no builder runtime, no script soup, fast by construction.
The six things
that weigh a page down
Scripts
External vs inline, and the bytes of inline code. JavaScript is the most expensive byte on the web - it must download AND run.
Stylesheets
Each external stylesheet blocks rendering until it arrives. Fewer, smaller, or inlined critical CSS wins.
Images
Missing width/height causes layout shift; missing loading="lazy" downloads off-screen images nobody sees yet.
Fonts
Each font family and weight is a download that can flash or shift text. Two families is usually plenty.
Embeds
YouTube, maps and social widgets are the big rocks - hundreds of KB each before anyone interacts. Use click-to-load facades.
The HTML itself
Inline scripts, styles and base64 blobs bloat the document - the one resource nothing can lazy-load.
Page weight,
answered simply
How heavy should a web page be?
The median web page today weighs around 2 MB, but fast sites aim much lower - under 1 MB transferred, and under about 50 requests. What hurts most is not one big number but the shape: dozens of small scripts each cost a request, and a single YouTube embed can pull in more JavaScript than the rest of your page combined.
Do YouTube and map embeds really slow a page down?
Yes - they are usually the heaviest thing on the page. A default YouTube embed loads roughly half a megabyte of scripts before anyone presses play, and an interactive map is similar. The standard fix is a facade: show a static thumbnail image, and only load the real embed when the visitor clicks it.
Why do images need width and height attributes?
Without them the browser does not know how much space an image will take, so the page jumps around as images load - that jump is Cumulative Layout Shift, one of Google's Core Web Vitals. Adding width and height (or CSS aspect-ratio) reserves the space up front, and loading="lazy" keeps off-screen images from loading at all until needed.
More free tools: the full toolbox · image alt auditor · redirect chain visualizer · the best way to host an AI-built site