Page speed
Page speed: what slows your page down and how to fix it
GeoRush Speed tests any public page with Lighthouse, Google's open-source measurement engine, on mobile or desktop. You get an A–F grade, Core Web Vitals, the request waterfall, a filmstrip of the load and third-party scripts, with plain-language fixes and monitors that alert you when a page gets slower.
Updated on
The problem: slow pages lose visitors and readers
A page that takes too long to show its main content loses part of the people who land on it, including those coming from Google or from an AI assistant. Crawlers, whether from search engines or AI, also work on limited time: the slower your server responds and the heavier the page, the harder it is to read.
Most speed tools give you a score and a technical checklist. GeoRush gives you the same data, explained: what is happening, how much time it costs you and what to do, with steps for your team or for your AI coding tool.
How it works
- 1
Paste a URL
Any public page: yours, a new landing page or a competitor's. Choose mobile or desktop.
- 2
GeoRush runs Lighthouse
It loads the page in a real browser and records metrics, requests, screenshots and audits. It usually takes 10 to 40 seconds.
- 3
The grade is calculated
The A–F grade blends performance (70%) and structure (30%): A from 90 points, B from 80, C from 70, D from 60, E from 50, and F below that.
- 4
Every fix is explained
Each opportunity shows the estimated saving, a plain-language explanation and a ready-to-paste prompt for your AI tool with steps and reference code.
- 5
The page is monitored
Set up a daily or weekly monitor. If the page regresses, you get an alert in GeoRush and, if connected, in Slack or your webhook.
What you see in every report
- Summary: A–F grade, performance and structure scores, LCP, TBT, CLS, fully loaded time and total size, with a screenshot.
- Performance: First Contentful Paint, Speed Index, LCP, Time to Interactive, TBT, CLS and server response time (TTFB).
- Structure: Lighthouse audits ranked by impact (high, medium, low), with the estimated saving in milliseconds or bytes.
- Waterfall: every request in load order, with type, size and duration, and which ones come from third-party domains.
- Filmstrip: the load frame by frame, so you see what a visitor sees at each moment.
- Third parties: scripts from other companies (analytics, chat, ads) and how much weight and time they add.
- History: how the same URL on the same device has changed over time, plus a side-by-side compare view for any two tests.
The metrics in one sentence each
| Metric | What it measures | What usually improves it |
|---|---|---|
| LCP | When the largest element (usually the hero image or main headline) is painted. | A compressed WebP or AVIF hero image that is not lazy-loaded; a fast server. |
| TBT | How long JavaScript blocks the browser from responding. | Less JavaScript, deferring what is not needed, reviewing third-party scripts. |
| CLS | How much the page jumps around while loading. | Width and height on images, reserved space for ads or banners. |
| TTFB | How long the server takes to start responding. | Page caching, a CDN and faster database queries. |
Lighthouse is a lab test. For what real visitors experience (including INP), use GeoRush web analytics.
What you do with it
Sort by impact and start with what costs you the most time: usually the hero image, render-blocking JavaScript or a third-party script. Paste the fix prompt into your AI tool or hand it to your developer, ship the change and test again; the history shows whether it worked.
For the pages that matter (homepage, pricing, the pages AI cites), set up a monitor. You can have up to 20 per workspace. It alerts you when the grade drops a letter, LCP rises more than 20%, or blocking time (TBT) rises more than 50%. Every report can be shared through a public link you can switch off at any time. Speed tests do not use AI credits; to prevent abuse, each workspace can run up to 20 manual tests per hour.
Measure your site and what AI says about it
Start free: page speed, SEO audit and visibility in ChatGPT, Gemini, Claude and Perplexity in one place.
Frequently asked questions
Keep reading
SEO and technical audit
Crawl your site, find SEO errors and check whether AI bots can read it, with code to fix it.
Web analytics
Cookieless analytics with a dedicated channel for AI assistant traffic and the AI bots that read your site.
Alerts, API and MCP
Slack or webhook alerts when your AI visibility changes, plus a REST API and MCP server.
Action plan
Tasks ranked by estimated impact, with steps, copy-paste code and before/after measurement.