Site Performance
Core Web Vitals and speed, under control.
Measure LCP, INP and CLS with real-world and lab data, and find out what slows down every page.
Site Performance: what slows down each page, with lab data and real-user data
Core Web Vitals page by page
Lab tests and real users on the same pages, against Google's thresholds.
- One page per sectionThe home page and one page for each section of the site, picked by the SEO audit: the page templates that matter, without testing every URL.
- Mobile lab testPerformance from 0 to 100, LCP, CLS and TBT for each page, with good, needs improvement and poor thresholds.
- Real Chrome usersLCP, INP and CLS at the 75th percentile over the last 28 days, rated Good, Needs improvement or Poor: the data Google uses for rankings.
- Site-wide dataWhen a page has too little traffic, the real-user data comes from the whole domain and the «site-wide» badge says so.
LCP diagnosis: where the time goes
For each page, the largest visible element and the phases of its loading.
- LCP elementWhich image or text block sets the LCP, with its selector.
- Loading phasesTTFB, Load Delay, Load Duration and Render Delay on one bar, so you see how much each one weighs.
- Dominant phasePoints to where the fix belongs: server or caching, a resource discovered late or lazy-loaded, CSS or fonts blocking the render.
- Server responseThe TTFB of each page: above 600 ms the bottleneck is hosting or caching.
Layout shifts and slow resources
What moves while the page loads and what delays the first paint.
- Layout shift mapA screenshot of the page with the worst CLS, with a numbered box on every element that moves.
- Cause of each shiftUnsized image, web font or injected iframe, with the element's selector and its CLS score.
- Fonts and imagesUnoptimized fonts that cause a flash of unstyled text (FOUT) and images with no declared width and height.
- Render-blocking resourcesThe stylesheets and scripts the browser has to download before it can show the page.
Development tickets, audit and reports
From diagnostics to the changes to make, inside the tools you already use.
- AI development ticketFor each sampled page, the fixes written in plain language for whoever works on the code.
- Built on the real HTMLIt opens with the root cause inferred from the loading phases and names the exact files and attributes to change.
- Fitted to the platformIt takes the detected CMS into account, for example the WordPress theme and plugins installed.
- Inside audits and reportsMeasurements are repeated with every SEO audit, run by hand or scheduled, and appear in the Core Web Vitals section of the PDF report and in the AI connector.
Performance is measured with Core Web Vitals: LCP for how fast the main content appears, INP for how quickly the page responds to clicks and taps, CLS for layout stability. Miraqo collects them during the SEO audit on a sample of pages, the home page and one page for each section of the site, from two sources that complement each other: the Lighthouse lab test on a smartphone, which gives Performance, LCP, CLS and TBT with the technical detail, and CrUX, real Chrome user data from the last 28 days, which adds INP.
For each page the diagnostics show what slows loading down: the dominant LCP phase, images without dimensions, unoptimized fonts, render-blocking stylesheets, elements that shift the layout. The AI development ticket turns all of this into fixes ready for whoever works on the code, starting from the root cause. Lab data can vary from one audit to the next even when the site has not changed: to judge a fix, the trend and the real-user data are what count.
Site Performance: how it works
- 01
The SEO audit measures the pages
With every audit, run by hand or scheduled, Miraqo picks the home page and one page per section and measures them in the lab on a smartphone.
- 02
Lab and real users
The lab values sit next to CrUX data from real Chrome users over the last 28 days, rated against Google's thresholds.
- 03
Diagnostics and tickets
The Performance page gathers the LCP diagnosis, the layout shift map and the resources to fix; the AI development ticket turns them into fixes.
Use cases
Site Performance: when to use it
- Diagnose slow pages before they affect rankings
- Verify Core Web Vitals after a technical fix
- Include performance data in the technical report shared with the client
Questions about site performance
From two sources that complement each other: Lighthouse simulates the load in a lab and gives you the technical detail, while CrUX (Chrome User Experience Report) collects what real Chrome users actually experienced on that page over the past few weeks.
LCP measures how fast the main content loads, INP measures responsiveness to interactions, and CLS measures visual stability.
With every new audit, which you can run manually or schedule. Field data (CrUX) covers the last 28 days of real browsing.
Mobile only: the lab test simulates a smartphone on a slow connection, the toughest scenario. A page that holds up there usually does better on desktop.
The Performance page shows the data from the latest audit: after a fix, a new audit is run and the new values are read. Lab scores can vary by 20-30% even when the site has not changed, so the most reliable signal is the real-user data, which updates over the following 28 days.
Yes, Core Web Vitals are a Google ranking factor. Improving them helps both rankings and user experience.
Related tools
Site Audit Miraqo crawls your site and gives you a health score with actions sorted by impact. Analytics & Traffic Sessions, users and conversions from Google Analytics 4 or Matomo next to your ranking data, in a single view. Automated Reports PDF reports with your branding, built from the project data and sent to clients automatically, every week or every month. See all featuresSite Performance: step-by-step guides
Start monitoring
your projects today.
Create a project, add keywords, see real positions. Free to start.
Start free