<- Go Back
Page Speed
Page Size, Objects, and Response Time: Per-Page Performance in RankFrame
Understand the per-page Performance audit in RankFrame: Page Size, Mobile Speed, Page Objects, Response Time, and Image Headers Expire. Learn what each value means and how to bring each one into the green.
Last Updated on
Read Time
3 min read
The five per-page checks
1. Page Size (KB)
The total size of the page including HTML, CSS, JavaScript, fonts, and images. Reported in KB. Targets: under 1,000 KB is good for marketing pages, under 2,000 KB is acceptable for image-heavy portfolios, anything above 3,000 KB warrants investigation. RankFrame shows a warning when the page is moderately large (e.g. 50.51 KB triggers a warning depending on context). Cut weight by compressing images and removing unused custom code.
2. Mobile Speed
A qualitative rating (good, fair, or poor) based on the mobile Lighthouse Performance score for this specific page. Distinct from the gauge in the SEO Analyzer because it reflects this single page, not the homepage or sitewide average. A page rated "poor" needs attention even if your sitewide mobile gauge looks healthy.
3. Page Objects
The total count of resource requests the page makes (HTML doc, CSS files, JS files, images, fonts, embeds). Reported as a single number (e.g. 47). High object counts increase total load time even if each object is small. Aim for under 50 on most Framer pages. Reduce by removing unused fonts, consolidating embeds, and deleting hidden elements.
4. Response Time (ms)
Time from request to first byte of HTML, in milliseconds (e.g. 1063ms). Anything under 600ms is good, 600 to 1500ms is fair, above 1500ms is poor and almost always a backend bottleneck. On Framer, high response time usually traces back to a heavy CMS query or a custom data fetch on the page.
5. Image Headers Expire
A caching check on the page's local images. Confirms that images are served with cache-control headers that allow browsers to reuse them on subsequent visits. Framer handles this for assets it controls. A failure here usually means an externally hosted image without proper cache headers.
Quick reference table
Check | Good | Action if Failing |
|---|---|---|
Page Size | Under 1,000 KB | Compress images, remove unused custom code, audit fonts. |
Mobile Speed | Good rating | Open the Speed tab and apply the per-page suggestions. |
Page Objects | Under 50 | Consolidate embeds, drop unused fonts, remove hidden frames. |
Response Time | Under 600ms | Simplify CMS queries, defer external API calls. |
Image Headers Expire | Pass | Move external images into Framer asset hosting. |
How these per-page checks relate to the site-wide Speed tab
The Speed tab gives you the bird's-eye view (gauges, Core Web Vitals, sitewide suggestions). The per-page Performance audit gives you the page-by-page breakdown so you can spot which pages are dragging the average down. Use the Speed tab to set goals, then use the Pages section to find and fix the worst offenders one page at a time.
Frequently asked questions
Why does RankFrame show a warning on a 50 KB page?
The warning thresholds are content-aware. A 50 KB page with no images may indicate missing assets or a broken page. Check the page in the live preview before assuming the warning is wrong.
Related to