Services
Industries
Free Tools
Resources
About Book a Consultation (407) 694-2055
Orlando, FL · Working nationwide since 2008
Free Tool · No signup

Page speed & Core Web Vitals.

Enter a URL and see how fast your page really loads, on mobile and desktop. We pull real Google data when your site has enough traffic, fall back to a fresh lab test when it does not, and explain all of it in plain English with the top fixes. No login wall.

You will get: Lighthouse score Core Web Vitals (LCP, INP, CLS) Plain-English verdict Top 3 fixes

Free, no signup. Powered by Google PageSpeed Insights (Lighthouse + real-user Core Web Vitals). A full test takes 20 to 40 seconds.

Running the speed test… this can take up to 40 seconds.

What your speed score is really telling you

Page speed is not a vanity number. It is one of the clearest predictors of whether a click turns into a phone call. This tool pulls the same data Google itself uses, real-user Core Web Vitals when your site has the traffic for it, a fresh Lighthouse lab test when it does not, and translates the whole thing into a plain-English verdict and the three fixes that would move the needle most.

Field data vs lab data (and why we are honest about it)

Field data comes from Google's Chrome User Experience Report (CrUX): the actual experience of real Chrome visitors to your site over the last 28 days. It is the truest picture, but Google only publishes it for pages that get enough traffic. Most low-traffic local service sites do not have it yet. When that happens, a lot of tools quietly show lab numbers and let you assume they are real-world. We do not. Lab data is a single controlled test that Lighthouse runs on demand, and when field data is missing we say so clearly and show the lab result instead.

The three Core Web Vitals

LCP (Largest Contentful Paint) is how long until the biggest thing on screen, usually your hero image or headline, finishes loading. Good is 2.5 seconds or under. INP (Interaction to Next Paint) is how quickly the page reacts when someone taps a button or link. Good is 200 milliseconds or under. CLS (Cumulative Layout Shift) measures how much the page jumps around as it loads, the annoying effect where you go to tap something and it moves. Good is 0.1 or under. Passing all three is a real ranking and conversion edge.

Why mobile speed is the one that pays the bills

The mobile test simulates a mid-range phone on a throttled connection, which is how most of your customers actually find you. A site can feel instant on your office desktop and still be painfully slow on a phone in a parking lot, and that gap is exactly where local businesses lose calls and form fills. If you only fix one number, fix mobile.

Pro tips

  • Test the page people actually land on, often a service or city page, not just the homepage.
  • Compress and properly size your images first. Oversized images are the number one cause of a slow LCP on local sites.
  • If you have no field data yet, that is normal for a newer or low-traffic site. Use the lab score as your baseline and re-check as traffic grows.
  • Re-run the test a couple of times. A single lab run can vary a few points based on network and server load.
  • A slow server response time (TTFB) usually points to cheap or overloaded hosting, or a bloated platform like a plugin-heavy build.

How we compare to the paid tools

GTmetrix gates mobile testing and multi-location runs behind PRO ($5 to $50 a month) and caps how many free tests you get. DebugBear and SpeedVitals are paid monitoring products. Ours is free, does both mobile and desktop, shows real Google field data when it exists and clearly-labeled lab data when it does not, and explains every number in plain English instead of a wall of jargon. No account, no credit card.

Frequently asked questions

What are Core Web Vitals?
Core Web Vitals are three real-user metrics Google uses to score experience: LCP (how fast the main content loads), INP (how quickly the page responds when you tap or click), and CLS (how much the layout shifts as it loads). Passing all three is a ranking and conversion advantage.
What is the difference between field data and lab data?
Field data (Google CrUX) is measured from real Chrome users over the last 28 days, so it is the truest picture, but it only exists for pages with enough traffic. Lab data is a single controlled Lighthouse test run on demand. Many low-traffic local sites have no field data yet, so we clearly show lab results instead rather than pretending field data exists.
Why is my mobile score so much lower than desktop?
Mobile tests simulate a slower CPU and a throttled connection, which is closer to how most customers actually visit. A site can feel fast on your office desktop and still be slow on a phone, which is exactly where you lose calls and form fills.
Does page speed actually affect SEO and leads?
Yes. Speed and Core Web Vitals are confirmed Google ranking signals, and study after study shows that every extra second of load time drops conversions. For a local service business a faster site means more of your clicks turn into calls and quote requests.
Is this the same as Google PageSpeed Insights?
It uses the exact same Google PageSpeed Insights data (Lighthouse plus CrUX) through Google's official API. We translate the raw scores into plain English with a business verdict and the top fixes, so you do not need to decode a wall of technical jargon.
Pro version coming soon

Always-on speed monitoring, and we fix it.

The Pro version tracks your speed continuously, alerts you when it regresses, and our team rebuilds the slow parts so your site stays fast.

Get early access, book a free call →

Want a site that's fast by default?

We build custom-coded sites that pass Core Web Vitals out of the box, and we fix the slow ones. Free speed audit available.

Get a free speed audit →Or call/text: (407) 694-2055

Where these speed numbers come from

Type a URL, pick mobile or desktop, and the tool calls Google's official PageSpeed Insights API. We measure nothing ourselves. Two different data sources come back. Field data is Google's Chrome User Experience Report: the experience of real Chrome visitors over the trailing 28 days, reported at the 75th percentile. Lab data is one Lighthouse test run on demand in a simulated environment, and the mobile run throttles both the connection and the CPU. The page labels which one you are looking at and never blends the two together.

The pass and fail thresholds are Google's published ones, not ours: LCP good at 2.5 seconds or under, INP at 200 milliseconds or under, CLS at 0.1 or under, TTFB at 800 milliseconds or under. The three top fixes are real Lighthouse audits that did not pass on your page, ranked by the millisecond savings Lighthouse itself estimates. Results are cached for an hour per URL and device.

Now the limits. It cannot see your competitors, your Search Console, or your analytics, and it cannot tell you what a speed fix will do to your rankings or your leads. If your page has no field data, which is normal on a lower-traffic local site, the tool falls back to whole-site data and labels it as such. If there is none of that either, you get lab numbers only. When Google's service is busy or rate limited, you get an error message, not an invented score. A broader check lives in the website report card, and the ranking side of the work sits under SEO.

Why did my score change when I ran it twice?

Lab scores come from a single simulated Lighthouse run, so a few points of movement between runs is normal and reflects network and server conditions at that moment, not a change to your site. Results are also cached for an hour per URL and device, so an immediate re-run can hand back the same numbers rather than a fresh test. Field data does not move run to run at all. It updates on Google's schedule from a trailing 28-day window.

Can this tell me why I am not ranking?

No. It measures loading performance on the one URL you enter and nothing else. It cannot see your keywords, your competitors, your Google Business Profile, or the words on the page, and speed is one signal among many. Nobody can tell you what a speed fix will do to your position or on what timeline, so treat the score as a build-quality check rather than a ranking forecast.