Measure speed the way Google does, then find out why: heavy images, blocking scripts, redirect chains, slow servers and insecure resources.
Eleven performance tools. Core Web Vitals and Lighthouse come from Google PageSpeed Insights; everything else is measured directly from your page.
Enter your URL in the Core Web Vitals report to see LCP, INP and CLS rated against Google's thresholds, using real-user data when Google has it. Then run the image audit, JS and CSS diagnostics and page-weight analyzer to find what is slowing the page, and the server response-time checker to separate a slow server from a heavy page.
Speed is a user-experience problem first and a ranking signal second. Websolindia combined Google's own measurement with direct checks of your page so you get the number and the reason behind it.
The Core Web Vitals and Lighthouse tools call Google PageSpeed Insights. The image, script, weight, redirect, HTTPS and response-time tools fetch your page and its files directly and measure real transfer sizes and timings.
Each tool names its thresholds, so you can see exactly why something passed or failed.
Pick a tool from the tabs above. This table shows what each one does and whether it needs an API key.
| Tool | What it does | Data source |
|---|---|---|
| PageSpeed Insights | Run Google PageSpeed Insights (Lighthouse) for any public URL: performance, accessibility, best-practices and SEO scores, key metrics and the biggest speed opportunities. | Built-in — no API key |
| Core Web Vitals report | Google's three Core Web Vitals — LCP, INP and CLS — judged against Google's thresholds, using real-user data when Google has it and lab data when it does not. | Built-in — no API key |
| Mobile and desktop performance | Run PageSpeed Insights for mobile and desktop together and compare scores and metrics side by side. | Built-in — no API key |
| Image optimization audit | Lists every image on a page with its real file size and format, and flags oversized files, old formats (PNG/JPEG that could be WebP/AVIF), missing dimensions, missing alt text and broken images. | Built-in — no API key |
| JavaScript and CSS diagnostics | Sizes every script and stylesheet on a page, flags render-blocking scripts, uncompressed or uncached files and third-party code, and adds Google's unused-code findings when PageSpeed is available. | Built-in — no API key |
| Redirect chain checker | Follow up to 10 URLs hop by hop. See every status code and where each redirect lands — and flag chains, loops and temporary redirects that waste crawl budget and speed. | Built-in — no API key |
| HTTPS and mixed-content checker | Checks the certificate (issuer, expiry), whether http:// redirects to https://, HSTS, and lists any insecure http:// resources loaded on an HTTPS page. | Built-in — no API key |
| Page weight analyzer | Adds up the real transfer size of the HTML, images, scripts, styles and frames on a page and shows what is heaviest — the quickest way to find what is slowing the load. | Built-in — no API key |
| Server response-time checker | Measures DNS, connection, TLS and time-to-first-byte over several requests from our server, so you can tell a slow server from a slow page. | Built-in — no API key |
| Accessibility audit | Checks the accessibility basics in the HTML — language, title, headings, image alt text, empty links, zoom blocking — and adds Google Lighthouse's accessibility score when PageSpeed is available. | Built-in — no API key |
| Lighthouse report | The full Lighthouse summary from PageSpeed Insights: all four category scores with colour bands, key lab metrics, opportunities and diagnostics, in one report you can export. | Built-in — no API key |
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | ≤ 2.5 s | ≤ 4.0 s | > 4.0 s |
| Interaction to Next Paint (INP) | ≤ 200 ms | ≤ 500 ms | > 500 ms |
| Cumulative Layout Shift (CLS) | ≤ 0.1 | ≤ 0.25 | > 0.25 |
| First Contentful Paint (FCP) | ≤ 1.8 s | ≤ 3.0 s | > 3.0 s |
| Total Blocking Time (lab) | ≤ 200 ms | ≤ 600 ms | > 600 ms |
| Time to First Byte | ≤ 800 ms | ≤ 1.8 s | > 1.8 s |
| Tool | How the score is built |
|---|---|
| Image audit | 100 minus 12 per oversized image, 6 per older-format image over 30 KB, 3 each for missing dimensions or alt, 15 per broken image |
| Page weight | ≤ 1 MB scores 100, ≤ 2 MB 85, ≤ 3 MB 65, ≤ 5 MB 40, above 20 |
| Server response | Median of up to five requests: ≤ 200 ms 100, ≤ 500 ms 90, ≤ 800 ms 75, ≤ 1.8 s 45 |
| HTTPS check | Penalties for plain HTTP, invalid or expiring certificate, no http→https redirect, missing HSTS, mixed content |
Everything except the PageSpeed-based tools works with no key. PageSpeed works keyless, but Google limits keyless requests heavily, so the site owner should add a free key.
| Provider | What it unlocks | How the site owner enables it |
|---|---|---|
| Google PageSpeed Insights | Lighthouse scores and Core Web Vitals (works with a free key; keyless use is heavily rate-limited) | psi_key in config.php |
| Topic | What to know |
|---|---|
| Lab vs field | Lab data is one simulated load; field data is real visits and only exists for pages with enough traffic. |
| Sizes | Image, script and weight totals come from the files linked in the HTML. Resources loaded later by JavaScript or CSS are not included. |
| Location | Server timing is measured from our server, so visitors far away will see more network time. |
| Image savings | Savings from WebP/AVIF are an estimate (about 25–35%), not a measurement. |
| Accessibility | Automated checks catch only part of accessibility problems; manual testing is still needed. |
They are Google's three user-experience metrics: LCP (loading), INP (responsiveness) and CLS (visual stability). Google assesses the 75th percentile of real visits.
Lab tests vary with server load and network conditions. Look at trends and the field data rather than a single score.
90–100 is good, 50–89 needs improvement, and below 50 is poor. Focus on the metrics and opportunities rather than the number itself.
As small as quality allows — often under 100 KB for content images — in modern formats such as WebP or AVIF, with width and height set to avoid layout shift.
It is a URL that redirects through several hops before the final page. Each hop adds delay and wastes crawl budget; point the first URL straight at the final one.
It is an HTTPS page loading some resources over plain HTTP. Browsers may block them and it undermines the secure padlock.
The built-in tools on this page are free and need no sign-up. Features that rely on third-party data (marked in the table above) only work when the site owner has connected that provider, because those providers charge per request. Visitors are never charged.
No. Addresses and keywords are used only to run your request and are not stored on our servers. A few tools save their own history (rankings, reviews, workspace data) in your browser's local storage so you can see change over time; clearing site data removes it.
Built-in checks read the public HTML your server returns and apply published rules, so they are repeatable and explainable. Estimates (traffic, visibility share, difficulty) are directional. Always confirm important findings in Google Search Console and your analytics.
They are built by the Websolindia team — a website design and SEO company in New Delhi, India, serving businesses since 2014. Every tool explains how it calculates results so you can check the logic.
