Is fetch time the same as Core Web Vitals?

No. Fetch time is an early network signal. Core Web Vitals measure loading, responsiveness, and layout stability from a user perspective.

Why does compression matter?

Compression shrinks text responses such as HTML, CSS, and JavaScript so browsers download less data.

Are all render-blocking resources bad?

No. Some critical CSS is necessary. The issue is too many non-critical scripts or styles blocking initial rendering.

Should every image be lazy-loaded?

Usually below-the-fold images should be lazy-loaded. Important above-the-fold hero images may need eager loading.

Technical SEO

Live

Page Speed Analyzer

Lighthouse-style report with prioritized fix recommendations.

X / Twitter LinkedIn Facebook

URL

HTML weight, asset breakdown, compression, caching, and recommendations.

Start here · What does page speed analysis check?

Page speed analysis looks for reasons a page may feel slow to users or hard for crawlers to process efficiently.

This tool fetches a URL, reads headers and HTML, then reports HTML weight, initial fetch time, compression, Cache-Control, total assets, render-blocking scripts and styles, and lazy-loaded images.

It is a practical first pass. Use it to find obvious technical fixes before running deeper lab or field tools for Core Web Vitals.

When to use this tool

Slow page triage
Use it when an article, product page, or homepage feels heavy and you need a fast list of likely causes.
Template comparison
Compare a blog post, category page, and landing page to see which template loads the most assets.
CDN or hosting QA
Check whether compression and cache headers are present after infrastructure changes.
Image cleanup
Spot pages where many images are not lazy-loaded below the fold.

Examples

Walk through these with the form above — they are practice scenarios, not live data.

Blog post speed pass

Try this

Enter a long article URL with images, embeds, and affiliate widgets.

What to look for

Review HTML weight, image lazy-loading count, and script totals before opening deeper performance tooling.

Homepage after redesign

Try this

Analyze the new live homepage.

What to look for

Look for missing compression, too many render-blocking resources, or a slow initial fetch.

Short tutorial

Follow in order the first time you use the tool; later you can skip to the step you need.

Step 1 - Enter the URL
Use the public page users visit, not an admin preview or blocked staging URL.
Step 2 - Review top metrics
Start with HTML weight, fetch time, compression, and total assets.
Step 3 - Read recommendations
Prioritize errors and warnings about compression, render-blocking resources, cache headers, and lazy loading.
Step 4 - Check the asset breakdown
Large counts of scripts, stylesheets, iframes, or videos point to the template area to inspect.
Step 5 - Validate with deeper tools
After obvious fixes, use Core Web Vitals Estimator or Lighthouse-style testing for LCP, INP, and CLS.

More detail

New here? Skim Start here first, then run one Examples scenario in the form above.

Page Speed Analyzer does one job: lighthouse-style report with prioritized fix recommendations. It lives under Technical SEO on SEOToolkits, where the beginner idea is simple: Technical SEO keeps pages crawlable, indexable, fast enough, and understandable to search engines.

FAQ

Is fetch time the same as Core Web Vitals?: No. Fetch time is an early network signal. Core Web Vitals measure loading, responsiveness, and layout stability from a user perspective.
Why does compression matter?: Compression shrinks text responses such as HTML, CSS, and JavaScript so browsers download less data.
Are all render-blocking resources bad?: No. Some critical CSS is necessary. The issue is too many non-critical scripts or styles blocking initial rendering.
Should every image be lazy-loaded?: Usually below-the-fold images should be lazy-loaded. Important above-the-fold hero images may need eager loading.