301→302301→302
A temporary redirect where a permanent one belongs.
Found by Redirect checker →
redirect loopredirect loop
The URL redirects back to itself and never settles.
Found by Redirect checker →
Audit

Page weight and speed checks

Response time, HTML size, compression, HTTP version, render-blocking and oversized assets, plus CrUX field data when you supply a key.

Page weight and speed checks

Asset weight

asset-weight-check reports render-blocking resources, oversized files, duplicate libraries, missing minification and caching.

Page weight and speed checks

Lab versus field

Crawl and browser timings are lab evidence; field Core Web Vitals come from crux-report, which needs a credential.

How it works

Three steps, one saved scan

  1. Fetch the page and its assets

    asset-weight-check downloads the page, then each linked stylesheet and script. It reads sizes, headers and markup. It does not render the page.

  2. Measure the server and the HTML

    A native crawl or a Screaming Frog export feeds the audit rules. They flag slow responses, heavy HTML and missing compression or HTTP/2.

  3. Compare with real-user data

    crux-report pulls field LCP, INP and CLS from the Chrome UX Report. It needs a Google Cloud API key that you supply.

What it checks

Checks in this feature

CheckWhat it meansSeverityEvidence
SLOW_RESPONSEThe server takes too long to answer the request.ImportantResponse time per URL
LARGE_HTMLThe HTML document is large for the page or for the site.ImportantHTML size in bytes
HTML_OVER_2MBThe HTML document is larger than 2 MB.ImportantHTML size in bytes
HTML_BLOATA lot of markup for very little text.TipBytes and word count per page
NO_COMPRESSIONHTML is sent uncompressed when gzip or Brotli would help.TipContent-Encoding header per URL
HTTP1_ONLYThe page is served over HTTP/1.x, not HTTP/2 or newer.TipHTTP version per URL
How to run it

One command

bash
seohead asset-weight-check --url https://example.com/

Install first: installation guide. Every command also runs as an MCP tool for AI agents.

Related checks

From the check registry

SLOW_RESPONSELARGE_HTMLNO_COMPRESSIONHTTP1_ONLYHTML_BLOAT
FAQ

Questions

Page weight and speed checks
No. asset-weight-check reads bytes and static markup. It cannot tell which CSS or JavaScript is unused. That check needs a rendered page, so it is reported as skipped.
No. Crawl and browser timings are lab data. Field Core Web Vitals come from crux-report, which needs a Google Cloud API key.
Google's web-vitals-2024-03 policy. LCP is good up to 2.5 s and poor above 4 s. INP is good up to 200 ms and poor above 500 ms. CLS is good up to 0.1 and poor above 0.25.
By default, any single linked CSS or JavaScript file over 500 KB. The threshold is configurable.
No. The checks send read-only requests. Fixes are yours to make.

Check your redirects locally