Ttooleras

Website Speed Test

Web Tools

Test website speed with real Core Web Vitals (LCP, INP, CLS), performance scores, resource sizes, and waterfall timing. Get specific, actionable recommendations for faster pages.. Free, private — all processing in your browser.

This tool is coming soon. Check back later!

Advertisement

A slow website costs conversions, rankings, and user patience in equal measure. Google's Core Web Vitals are now ranking signals, and even a half-second improvement can lift organic traffic measurably. This speed test runs a real performance audit on any public URL and reports Core Web Vitals, a performance score, resource breakdown, and specific recommendations prioritized by impact.

The audit measures Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) — the three current Core Web Vitals. It also measures classic metrics like First Contentful Paint, Time to First Byte, Total Blocking Time, and Speed Index. Each metric is scored against Google's thresholds (good, needs improvement, poor) so you know where to focus.

Beyond the metrics, the tool provides a resource waterfall showing what loaded when and how long each request took. Render-blocking CSS and JS are highlighted, unused code is flagged, unoptimized images are called out with suggested formats and sizes, and third-party scripts (analytics, chat widgets, ads) get their own impact assessment. Every recommendation includes an estimated savings in milliseconds and a plain-English explanation of how to fix it. Run the test on desktop and mobile network profiles to understand the user experience across devices, and export the report to share with your dev team or stakeholders.

Website Speed Test — key features

Core Web Vitals measurement

Real LCP, INP, CLS measurement matching Google's ranking signal thresholds.

Classic speed metrics

FCP, TBT, TTFB, Speed Index, and Lighthouse-style performance score.

Resource waterfall

Visualize every request's timing to spot bottlenecks.

Prioritized recommendations

Specific actions ordered by estimated impact in milliseconds.

Image audit

Identifies unoptimized images with format and size suggestions.

JS/CSS analysis

Finds render-blocking and unused code for async/defer fixes.

Mobile and desktop profiles

Test under both conditions to understand user experience across devices.

Export reports

HTML, JSON, CSV exports for sharing and tracking over time.

How to use the Website Speed Test

  1. 1

    Enter the URL

    Paste the full URL of the page you want to test. Public URLs only.

  2. 2

    Choose device profile

    Mobile (slower network and CPU) is the default and most important. Desktop audits are useful for productivity sites.

  3. 3

    Start the audit

    The tool loads the page in a controlled environment and collects metrics.

  4. 4

    Review Core Web Vitals

    Check LCP, INP, CLS scores. Red means poor, yellow needs improvement, green is good.

  5. 5

    Follow recommendations

    Work through the prioritized list — biggest potential savings first.

Common use cases for the Website Speed Test

SEO optimization

  • :
  • :
  • :

Development

  • :
  • :
  • :

Marketing

  • :
  • :
  • :

Ops and reliability

  • :
  • :
  • :

Website Speed Test — examples

Homepage audit

Typical performance run

Input
https://example.com/
Output
CWV + score + waterfall

Product page

Commerce checkout step

Input
product URL
Output
LCP and INP specifically

Blog post

Content-heavy

Input
blog URL
Output
CLS issues from images

Mobile vs desktop

Both profiles

Input
URL + both
Output
side-by-side metrics

Third-party impact

With/without analytics

Input
compare runs
Output
script blocking time identified

Technical details

Website speed tests use a headless browser (Chrome DevTools Protocol) to load your page under controlled network and CPU conditions, then collect the metrics browsers expose through the Performance API. The core metrics tracked:

- LCP (Largest Contentful Paint): time until the largest above-the-fold element renders. Target: under 2.5s. Often an image or hero text block.
- INP (Interaction to Next Paint): perceived responsiveness during interactions (clicks, taps, key presses). Replaced FID in March 2024. Target: under 200ms.
- CLS (Cumulative Layout Shift): sum of all unexpected layout shifts during page load. Target: under 0.1. Often caused by images without dimensions or injected ad slots.
- TTFB (Time to First Byte): server response latency. Target: under 800ms. Indicates hosting or CDN quality.
- FCP (First Contentful Paint): time until first text or image renders. Target: under 1.8s.
- TBT (Total Blocking Time): time main thread was blocked during load. Target: under 200ms.
- SI (Speed Index): how quickly above-the-fold content visually populates. Target: under 3.4s.

The tool runs the audit with a simulated slow 4G network profile and mid-tier mobile CPU to approximate real-world conditions (per Google's mobile-first approach). Desktop tests use faster network and CPU assumptions. Results include a lighthouse-style score (0-100 per category) combining all metrics.

Recommendations come from analyzing the resource waterfall. Large images are flagged with suggestions for WebP/AVIF conversion. Render-blocking JS is identified for async/defer/module loading. Unused CSS in above-the-fold selectors suggests critical CSS extraction. Third-party scripts get individual impact assessments so you can weigh features against performance. Exports include HTML, JSON, and CSV formats for tracking improvements over time.

Common problems and solutions

Lab vs field metrics

Lab tests use synthetic conditions. Real user metrics (CrUX) show actual visitor experience and can differ significantly.

Single-page app limits

SPAs with client-side routing need special audit approaches — test specific routes individually.

CDN caching

First-load results may differ from cached-load results. Run multiple times to see both states.

Third-party variability

External scripts (analytics, ads, chat) vary in load time. Average several runs for stability.

Geographic variation

Test from different regions if your audience is global. Latency alone can swing TTFB dramatically.

Over-optimizing for scores

Pursuing a perfect score can harm UX (e.g., stripping all animations). Balance metrics with user research.

Website Speed Test — comparisons and alternatives

Google PageSpeed Insights is the reference test but runs on Google infrastructure and isn't always available for every URL. GTmetrix offers good analysis but gates features behind a paid tier. WebPageTest is powerful but has a steep learning curve. This tool uses the same Lighthouse engine, surfaces Core Web Vitals prominently, adds prioritized recommendations with savings estimates, and runs in the browser — no account, no queuing, no limits. Pair with Chrome DevTools Performance tab for deep investigation.

Frequently asked questions about the Website Speed Test

What are Core Web Vitals?

Google's three key user-experience metrics: LCP (load), INP (interactivity), CLS (visual stability). They're ranking signals since 2021 (FID replaced by INP in 2024).

Why do I get different scores on different runs?

Network variability, CDN cache state, and third-party script timing all affect results. Average several runs for a stable number.

How do I improve LCP?

Optimize the largest element (usually an image or hero text): serve WebP/AVIF, set proper dimensions, preload critical resources, reduce TTFB with CDN, defer non-critical JS.

What's the difference between lab and field data?

Lab tests (this tool) are synthetic and reproducible. Field data (CrUX from real users) reflects actual experience and is what Google uses for ranking.

Does this match PageSpeed Insights?

Both use Lighthouse under the hood. Small differences come from network simulation and CPU throttling settings.

Can I test staging sites?

Yes if publicly accessible. For behind-VPN sites, use the Lighthouse CLI locally.

How often should I test?

On every major release, after third-party script additions, and monthly for tracking. CI integration catches regressions continuously.

Are third-party scripts always bad?

They add risk. Measure each one's impact — some (lightweight analytics) are fine, others (full chat widgets, ad stacks) can tank your score.

Additional resources

Advertisement

Related tools

All Web Tools

Learn more

Explore more tools

200+ free tools that run in your browser.

Browse all tools →