Page Speed
Docs
Page Speed
Page Size, Objects, and Response Time: Page Speed in RankFrame
Last Updated on
Read Time
3 min read
In short
What it does
Understand page size, page objects and response time, and where RankFrame shows them: the SEO Analyzer Speed tab, with Page Size and Response Time checks and Lighthouse scores for mobile and desktop.
Where
SEO Analyzer > Speed
Cost
Free
Where to Find Page Size and Response Time
Open the SEO Analyzer and click the Speed tab. It has two parts: Speed Insights, which runs Lighthouse for mobile and desktop when you click Check Speed (or Re-analyze Speed), and two checks, Page Size and Response Time. Pick a page from the page menu at the top, or open a page from the Pages section, to see these numbers for that page.
1. Page Size
The total size of the page, including HTML, CSS, JavaScript, fonts and images. As a general guide, under 1 MB is good for marketing pages, under 2 MB is acceptable for image-heavy portfolios, and anything above 3 MB is worth investigating. Cut weight by compressing images and removing unused custom code.
2. Response Time
How long the server takes to respond to the request, in milliseconds. Under 600 ms is good, 600 to 1,500 ms is fair, and above 1,500 ms is slow. On Framer, a slow response usually traces back to a heavy CMS page or a custom data fetch on the page.
3. Mobile and Desktop Performance
Speed Insights shows a Lighthouse score out of 100 for mobile and desktop, with First Contentful Paint (FCP), Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS) under each. These are the Core Web Vitals style measures Google cares about. Mobile scores are usually lower than desktop, so fix mobile first.
4. Page Objects
Page objects are the separate requests a page makes: the HTML document, CSS files, scripts, images, fonts and embeds. RankFrame does not count them, but they show up in your Lighthouse results, because every extra request adds to load time and to LCP. Aim to keep them down by removing unused fonts, consolidating embeds and deleting hidden elements you no longer need.
Quick reference table
Measure | Good | Action if Failing |
|---|---|---|
Page Size | Under 1 MB | Compress images, remove unused custom code, audit fonts. |
Response Time | Under 600 ms | Simplify CMS pages, defer external API calls. |
LCP | Under 2.5 s | Shrink the hero image, cut requests above the fold. |
CLS | Under 0.1 | Give images and embeds fixed sizes. |
Page Objects | As few as possible | Consolidate embeds, drop unused fonts, remove hidden frames. |
Good to know:
Checking one page at a time
Speed results are per page and per language. Check your homepage first, then work through your most visited pages from the Pages section. After you change something in Framer, publish and click Re-analyze Speed to see the new numbers.
Related features
Page Speed: Mobile and desktop Lighthouse scores with Core Web Vitals.
SEO Analyser: Score every page out of 100 with 16 checks and a PDF report.
Frequently asked questions
Does RankFrame count page objects?
No. The Speed tab shows Page Size, Response Time and Lighthouse results for mobile and desktop. Page objects affect those results, so reducing them improves your scores even though there is no separate count.
My response time is 2 seconds. What is causing it?
Is Page Objects the same as the number of files in my Framer project?
My Image Headers Expire check fails. How do I fix it?
Should I aim for the lowest possible Page Size?
Related
Still stuck?
Try the troubleshooting guides, or send support the page link and a screenshot.