Google PageSpeed integration
PageSpeed Insights integration: Core Web Vitals next to AI search
Add your own Google API key and run PageSpeed Insights on any page from inside Rankry. Get Lighthouse scores, lab metrics, real-user Core Web Vitals and the fixes Google suggests, on mobile or desktop, right beside your AI visibility work.
7-day Base trial · No card needed
PageSpeed · Mobile
ugcplanner.com/pricing82/100
Performance score
- Largest Contentful Paint2.1 s
- Interaction to Next Paint180 ms
- Cumulative Layout Shift0.14
- SEO100
Sample data
In short
The PageSpeed integration runs Google PageSpeed Insights on the pages you choose, from inside Rankry, the AI search optimization platform. You bring your own Google API key; Rankry runs the test on mobile or desktop and shows Performance, Accessibility, Best Practices and SEO scores, lab metrics, Chrome UX Report field data and Google’s improvement opportunities. Runs are manual, so you decide which pages to test and when.
Setup
How do I set up the PageSpeed integration?
Rankry’s setup guide has four steps, and the key stays yours: tests run on your own Google quota, not on a shared one.
- 01
Open Google Cloud Console
Sign in to Google Cloud Console and choose or create a project to hold the key.
- 02
Enable the PageSpeed Insights API
Find “PageSpeed Insights API” in the API library and enable it for that project.
- 03
Create an API key
Under Credentials, create an API key. Restricting it to the PageSpeed Insights API is a good habit.
- 04
Paste the key in Rankry
Open Integrations, then Google PageSpeed, and paste the key. Rankry stores it encrypted for that project.
- 05
Run your first test
Enter a URL, choose mobile or desktop, and run it. The overview shows the scores; the report detail has everything else.
- 06
Repeat for any page
Test your homepage, pricing page or a new article. Rankry keeps the latest report for each URL and device.
What it measures
What does a PageSpeed run measure?
Each run calls Google PageSpeed Insights for one URL and one device. This is what comes back and where each part comes from.
| Area | What Rankry shows | Where the data comes from |
|---|---|---|
| Lighthouse scores | Performance, Accessibility, Best Practices and SEO, plus Agentic Browsing when Google returns it | A Lighthouse lab test Google runs on the page |
| Lab metrics | First Contentful Paint, Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift, Speed Index, Time to Interactive | The same lab test, on a simulated device and connection |
| Field data | FCP, LCP, CLS, Interaction to Next Paint and Time to First Byte from real Chrome users | The Chrome UX Report (CrUX), when the page or site has enough traffic |
| Opportunities | Suggested fixes with “Est. savings”, diagnostics and passed audits | Lighthouse audits |
| Filmstrip | Screenshots of the page as it loads, frame by frame | The Lighthouse lab test |
Field data appears only when Google has enough real-user data for the page or the site.
Speed and AI search
Does page speed affect AI Overviews and ChatGPT citations?
Think of speed as a gate, not a boost. A page that loads slowly, times out or hides its content behind heavy scripts is harder for any crawler to fetch and read, whether that is Googlebot building the index AI Overviews and AI Mode draw on, or the crawlers behind ChatGPT, Claude and Perplexity search. Once a page loads quickly and reliably, making it faster still is unlikely to change whether AI cites it.
Google says Core Web Vitals are used by its ranking systems, and also that relevant, helpful content matters more than a perfect score. Use PageSpeed to find real problems, such as a slow server, a huge hero image or a layout that jumps, rather than to chase 100.
What matters most for AI search is whether your content is in the HTML at all. Several AI crawlers are reported to fetch pages without running JavaScript, so text that only appears after scripts run may be invisible to them. Rankry’s AI Readiness audit checks whether your homepage is pre-rendered; PageSpeed shows how heavy and slow a page is to load.
Core Web Vitals
Which Core Web Vitals matter for AI search?
PageSpeed reports all of these. The first three are Google’s Core Web Vitals; the others help explain them.
Largest Contentful Paint (LCP)
How long until the main content is visible. Google’s “good” threshold is 2.5 seconds or less for most visits.
Interaction to Next Paint (INP)
How quickly the page responds to taps, clicks and key presses. Good is 200 milliseconds or less.
Cumulative Layout Shift (CLS)
How much the layout jumps while it loads. Good is 0.1 or less.
Time to First Byte (TTFB)
How fast the server starts responding. A slow server delays every visitor and every crawler, before anything else can load.
Total Blocking Time (TBT)
A lab measure of how long scripts block the page. High values often mean heavy JavaScript, which some crawlers won’t run at all.
First Contentful Paint (FCP)
When the first text or image appears. A late FCP on a content page usually points to render-blocking files.
Devices and history
Should I test mobile or desktop?
Mobile is the default, and for most sites it is the one to watch. Google mostly indexes the mobile version of pages, and the mobile test runs on a slower simulated device and connection, so problems show up there first.
Run desktop when your audience is mostly on desktop, or to compare the two. Rankry keeps one report per URL and device, so a page can have a current mobile report and a current desktop report side by side.
A new run replaces the previous report for that URL and device, and repeat runs within 60 seconds return the cached result. Rankry doesn’t keep a list of past runs, so note the scores before and after a fix if you want to compare them.
Connected
How does PageSpeed work with the rest of Rankry?
PageSpeed reports aren’t only on the PageSpeed page. Rankry Brain and the MCP server can read them too.
In Rankry Brain
Ask “How fast is my site?” and Brain reads your saved PageSpeed reports, then explains the scores and the biggest fixes. It reads reports; it doesn’t start new runs.
Through the MCP server
Claude Code, Cursor or another MCP client can list your reports, read one in full, or run a fresh test with run_pagespeed_audit, the one MCP tool that saves something.
With AI Readiness
AI Readiness checks whether AI crawlers are allowed to read your homepage and can; PageSpeed checks how fast and stable any page is. Fix crawl access first.
With Search Console
If Search Performance shows mobile doing worse than desktop for a page, a mobile PageSpeed run on that page is the natural next check.
Where to start
Which pages should I test first?
You run each test yourself, so start with the pages AI answers are most likely to cite.
- Your homepage, which AI Readiness also audits
- Pricing and product pages that buyer questions lead to
- Comparison and “best of” pages written to win prompts
- Pages the Sources page lists as yours for important prompts
- New articles drafted in Content Studio, once they are live
- Pages where Search Console shows mobile lagging desktop
Explore Rankry
Related features
Do I need my own Google API key?
Yes. The PageSpeed integration runs on a Google API key you create in Google Cloud Console with the PageSpeed Insights API enabled. Rankry stores it encrypted for your project, and tests use your key’s quota rather than a shared one.
Does the PageSpeed Insights API cost anything?
Google doesn’t charge for the PageSpeed Insights API; usage is limited by the quota on your key. Rankry doesn’t add a separate run allowance for PageSpeed. Check the quota for your key in Google Cloud Console if you plan to test many pages.
Can Rankry run PageSpeed tests automatically?
No. Runs are manual: you choose the URL and device and start the test. There is no schedule. From an MCP client you can ask for a fresh test with run_pagespeed_audit, which is still a test you start.
Does Rankry keep a history of PageSpeed results?
Rankry keeps the latest report for each URL and device, mobile and desktop. A new run replaces the previous one, and there is no list of past runs, so note your scores before a fix if you want to compare.
Why is there no field data for my page?
Field data comes from the Chrome UX Report, which only has numbers for pages and sites with enough real Chrome visits. New or low-traffic pages often have lab data only. The lab metrics and Lighthouse scores are still shown.
Should I test mobile or desktop?
Start with mobile, which is Rankry’s default. Google mostly indexes the mobile version of pages, and the mobile test is the stricter of the two. Add a desktop test when much of your audience uses desktop.
Which plans include the PageSpeed integration?
It is available on plans that include it. If your plan doesn’t, Rankry says the integration isn’t included. The pricing page lists what each plan includes.
Is PageSpeed the same as Rankry’s AI Readiness audit?
No. AI Readiness runs 36 checks on whether AI crawlers can find, read and cite your site, from robots.txt rules to structured data. PageSpeed measures how fast and stable a page is to load. They complement each other.
Will a better PageSpeed score get me into AI answers?
Not on its own. Speed works as a gate: a page that is too slow or script-heavy can be hard for crawlers to read. Past that point, what earns a citation is content that answers the question and sources that mention you.
Check the pages AI should be citing
Start a free trial, add your Google API key, and test the pages that matter for your AI visibility.
7-day Base trial · No card needed