Insira um URL
Slow websites lose visitors. Google penalizes them. Customers leave.
You need to know exactly how fast your pages load – not just a vague "it feels slow" or a single number. You need data: load time, page size, number of requests, and more.
Our Page Speed Checker gives you all of that in a clean, readable table. No broken formatting. No messy text dumps. Even if you're checking pages generated by custom PHP code, the output stays structured.
Enter one or more URLs. One per line. Get a complete performance table for each.
Website owners – Your site feels sluggish. You want numbers before you call your hosting company. Run the page through our checker. Get load time, page size, and request count. Now you have evidence.
SEO professionals – Google's Core Web Vitals matter. Slow pages rank lower. Check your client's pages. Find the worst offenders. Prioritize fixes based on data, not guesses.
Developers – You just deployed a new feature. Did it slow down the site? Run the affected URLs through our checker. Compare before and after. If load time jumped from 0.8s to 2.5s, you know something broke.
Ecommerce owners – A 1‑second delay can cost you 7% conversions. Test your product pages. If they're slow, fix them before you lose sales.
Agency owners – Before sending a client report, test their pages. Show them load times, page sizes, and recommendations. Look professional.
Unlike many tools that just dump raw text or require you to parse messy API responses, our checker outputs a clean HTML table.
For each URL you submit, you'll see:
| URL | Load Time (ms) | Page Size (KB) | Requests | Status |
|---|---|---|---|---|
| https://yoursite.com/page1 | 845 | 142 | 34 | Success |
| https://yoursite.com/page2 | 2100 | 589 | 78 | Slow |
No broken columns. No missing data. Even if your pages are generated by custom PHP, ASP.NET, or any other backend, our tool parses the response and fills the table correctly.
We don't just ping the server. We actually download the full HTML of each page and measure:
For each URL, we make a fresh, uncached request. No CDN trickery. You get real numbers as a first‑time visitor would see them.
Step 1 – Open the Page Speed Checker on bingowebrabbit.com.
Step 2 – Enter URLs. One per line. Examples:
https://bingowebrabbit.com
https://example.com/slow-page
https://your-custom-php-site.com/product
Step 3 – Click "Check Speed".
Step 4 – Wait. Each URL takes 2–5 seconds depending on server response time.
Step 5 – View the results in a sortable table. Click any column header to sort by load time, size, or requests.
Step 6 – Download the table as CSV if you need to share or archive.
Load time (ms) – Under 500ms is excellent. 500–1000ms is okay. 1000–2000ms is slow. Over 2000ms is critical – fix immediately.
Page size (KB) – Under 50KB is very lean. 50–150KB is average. 150–500KB is heavy. Over 500KB for HTML alone is problematic (most of that should be in external assets).
Requests – Each request adds round‑trip time. Under 20 requests is good. 20–50 is normal. 50–100 is heavy. Over 100 is excessive.
Status – Any status other than 200 or 304 means the page isn't loading properly. Check for 301 redirects (adds delay) or 500 errors (server problem).
| Site Type | Typical Load Time | Typical Page Size | Typical Requests |
|---|---|---|---|
| Plain HTML site | 100‑300ms | 10‑30KB | 5‑15 |
| WordPress blog | 300‑800ms | 50‑150KB | 30‑60 |
| Ecommerce product page | 500‑1200ms | 100‑300KB | 50‑100 |
| Heavy SPA (React/Vue) | 800‑2000ms | 200‑500KB | 70‑150 |
If your pages exceed these ranges, investigate.
Many speed checkers return raw JSON or plain text. You paste 20 URLs, and you get a wall of text. Impossible to read. Even worse, if your website uses custom PHP code that outputs non‑standard headers or weird characters, those tools break entirely. Their output becomes gibberish.
Our tool does two things differently:
<pre> block with spaces. Not a comma‑separated mess. A real, border‑styled, sortable table.If you've tried other tools and seen broken tables or missing columns after pasting your own PHP‑generated URLs, try ours. The table stays intact.
Slow load time (>1.5s) – Likely slow database queries, unoptimized PHP, or cheap hosting. Consider caching, upgrading hosting, or optimizing code.
Large page size (>200KB HTML) – Your HTML might be bloated with inline styles, massive comments, or repeated code. Minify HTML, remove unnecessary whitespace.
Too many requests (>80) – Each external script, font, or image adds a request. Combine CSS/JS files. Use image sprites. Lazy load below‑fold images.
Redirect chain (status 301, then another 301) – Each redirect adds a full round‑trip. Fix your .htaccess or routing to point directly to the final URL.
Status 500 (Internal Server Error) – Your PHP code has an error. Check error logs. Our tool won't fix it, but it will tell you the page is broken.
Test multiple pages – A fast homepage means nothing if your product pages are slow. Enter 5–10 key URLs (home, category, product, blog post, contact). See the range.
Test at different times – Hosting performance varies. Run your URLs at 9 AM and 9 PM. Compare. If night is faster, your host is overselling daytime resources.
Test from different locations – Our tool uses servers in multiple regions (configurable). A page that loads fast in New York but slow in London suggests CDN or routing issues.
Test after every deployment – Automate it mentally. Every time you push PHP code, run the affected URLs through our checker. Catch slowdowns before users do.
Compare competitors – Run your top competitor's key pages. If they're faster than yours, that's a problem you can fix.
Mozilla/5.0 ...) to avoid being blocked.Is this the same as Google PageSpeed Insights?
No. Google's tool measures real user experience (Core Web Vitals) using lab and field data. Our tool measures raw HTML fetch time – server response + network latency. Both are useful. Use ours for quick, repeatable tests. Use Google's for deep optimization advice.
Why does my page show "slow" but loads fast for me?
You might be viewing cached versions. Our tool always fetches fresh, uncached. Or your local connection is faster than our test server. Run from different regions to get an average.
Can I test localhost URLs (127.0.0.1)?
No. The tool runs on our servers. We cannot reach your local machine. Upload your site to a staging server first, then test.
How many URLs can I test at once?
Up to 20 per batch. For larger lists, run multiple batches or contact us for bulk API access.
Is it free?
Yes, for normal usage. No hidden limits for personal or small business use. Heavy commercial use may require API subscription.
After entering these three URLs:
https://bingowebrabbit.com
https://bingowebrabbit.com/page-speed-checker
https://example.com
Your output table will look something like:
| URL | Load Time (ms) | Page Size (KB) | Requests | Status |
|---|---|---|---|---|
| https://bingowebrabbit.com | 342 | 48 | 23 | 200 OK |
| https://bingowebrabbit.com/page-speed-checker | 398 | 52 | 25 | 200 OK |
| https://example.com | 127 | 1.2 | 1 | 200 OK |
Sort by load time to see the fastest and slowest at a glance.
You can't improve what you don't measure.
The Page Speed Checker gives you clear, tabular data about how your pages perform. No black magic. No hidden fees. No broken tables – even if your site runs on custom PHP code.
Enter your URLs. Get a sortable table. Identify slow pages. Fix them. Repeat.
Try it now on bingowebrabbit.com