Page speed

Free page speed test + auto-updating speed badge

Last updated: November 2026·By FeedPulse Editorial

Test how fast any page loads on mobile with Google's PageSpeed Insights API, then show the result on your own site with an auto-updating page speed badge. Re-checked every 6 hours once your site is registered, every 14 days for one-off lookups. Free, no signup.

free page speed testwebsite speed test freepage speed testpage speed badgesite speed widgetwebsite speed testpage load time widgetwebsite speed checkerload time badgefree pagespeed widgetwebsite performance badgesite speed testsite speed embedpage speed insights widget

· No signup · No email · 100% free forever · Tip — paste a full URL like feed-pulse.com/blog/foo to test that specific page

/ deep dive

A free page speed test for any URL

Paste any URL and we run it through Google's PageSpeed Insights API on mobile, the same lab test you get at pagespeed.web.dev. It loads the page on a simulated mid-range phone over a throttled connection. The main figure is the Speed Index (how quickly the page visibly fills in), with the Lighthouse performance score out of 100 underneath. If Speed Index isn't available we show Largest Contentful Paint instead. Because the numbers come from Google's own tool, anyone can verify them.

What the number does and doesn't tell you

This is a lab result from a single run, so it can move a little between checks even when nothing changed. It is not the same as Core Web Vitals, which Google measures from real Chrome users (the CrUX dataset) and which feed its page-experience signals. A lab test is the right tool for catching regressions before your visitors do; for field data, look at the Core Web Vitals report in Search Console or the field-data section of PageSpeed Insights.

Does page speed affect Google rankings?

Somewhat. Core Web Vitals are part of Google's page-experience signals, but Google is clear that it still ranks the most relevant content first, even when its page experience is weaker. In practice speed works more like a tie-breaker between comparable pages. The stronger reason to fix a slow page is that visitors feel it.

How to run a fair website speed test

Lab tests vary from run to run, because network conditions and server response times change. To test website speed fairly, test the exact URL your visitors land on (with or without www, on https), run the test two or three times and look at the typical result rather than the best one, and change one thing at a time between tests. If your page sits behind a CDN, the first test after a deploy can be slower while caches warm up.

Reading the result: Speed Index, LCP and the performance score

Speed Index measures how quickly the visible part of the page fills in during load, and a lower number is better. Largest Contentful Paint (LCP) marks the moment the biggest image or text block in the viewport appears. The Lighthouse performance score out of 100 is a weighted blend of several lab metrics, including Speed Index, LCP and Total Blocking Time, so it can move even when Speed Index stays the same. Lighthouse calls 90 and above good, 50 to 89 needs improvement, and below 50 poor.

Why this free page speed test uses mobile

Google indexes the web with a smartphone crawler, and for many sites most visits now come from phones. Mobile tests are also stricter: PageSpeed Insights simulates a mid-range phone on a throttled connection, so a page that does well on mobile usually does well on desktop too. If you need a desktop result as well, run the URL at pagespeed.web.dev and switch to the Desktop tab.

The most common causes of a slow page

The same few problems come up again and again in PageSpeed Insights reports: images much larger than the space they're shown in, too much JavaScript running before the page becomes usable (often from themes, page builders, chat widgets and ad scripts), render-blocking CSS and web fonts, and slow server responses on uncached pages. On WordPress, a caching plugin and fewer plugins overall usually help most. On Shopify, apps you no longer use that still inject scripts are a frequent cause.

Will adding widgets slow my page down?

Any third-party script costs something. Keep the number of embeds low, load them after your main content where possible, and run this page speed test before and after adding one so you can see the real effect on your own page rather than relying on anyone's promise.

Why the number changes between tests

Each run loads the page fresh from Google's servers, so the result moves with your server's response time, third-party scripts that load differently each time, and ads or embeds that vary from one load to the next. Differences of a few hundred milliseconds are normal. A consistent jump after you change something is the signal worth acting on.

Show the result as a speed badge

Embed the result on your own site with one script line. Put it in your <head> and each page shows its own result, or place it in a footer or sidebar. It comes in 10 themes and four sizes, re-checks every 6 hours for registered sites and every 14 days otherwise, and works on WordPress, Shopify, Wix, Webflow, Ghost, Squarespace, Blogger and plain HTML.

/ authoritative sources
/ faq

Frequently asked questions

Questions we hear most often — also emitted as FAQPage schema so search engines can surface these in “People also ask” results.

+What is a good page load time?
For Largest Contentful Paint, Google treats 2.5 seconds or less as good and over 4 seconds as poor, measured on real visits. For the lab Speed Index this tool shows, Lighthouse scores a mobile result of about 3.4 seconds or less as fast. Faster is better, but compare yourself with sites like yours rather than chasing a single number.
+How does Google measure page speed?
For ranking purposes Google uses Core Web Vitals from real Chrome users, collected in the Chrome User Experience Report (CrUX): Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, assessed at the 75th percentile of visits. PageSpeed Insights shows that field data when a page has enough traffic, alongside a Lighthouse lab test.
+How is my page speed measured here?
We call Google's PageSpeed Insights API in mobile mode and show the lab Speed Index in milliseconds, falling back to Largest Contentful Paint if Speed Index is missing, with the Lighthouse performance score underneath. Registered sites re-check every 6 hours, one-off lookups of other domains are cached for 14 days, and the result panel has a Refresh button.
+Does page speed affect SEO ranking?
Core Web Vitals are part of Google's page-experience signals, so speed does count, but relevance comes first: Google will still rank a slower page that answers the search better. Treat a poor score as a user-experience problem worth fixing rather than a guaranteed ranking lever.
+Why does my speed badge say Measuring…?
The first PageSpeed Insights run for a new page can take up to about 90 seconds. Until a real result arrives the badge says Measuring…, and if Google's API is temporarily unavailable it says Unavailable. It never shows a made-up number in the meantime, and it updates by itself once the measurement lands.
+How can I make my site faster?
Start with the biggest wins PageSpeed Insights lists for your page. Common ones: compress and correctly size images (WebP or AVIF), lazy-load images below the fold, defer non-critical JavaScript, remove unused scripts and CSS, serve files from a CDN with compression enabled, and limit how many web fonts load before the page renders. Re-test after each change so you know which one helped.
/ also free
AI SEO Audit
Paste any URL — get a Gemini-powered audit of title, meta, schema, CWV, internal links + a prioritised fix list. Free, no signup.
/ other free seo tools
/ free widgets you can embed too