Free Core Web Vitals monitoring tools help businesses understand whether their websites load quickly, respond smoothly, and maintain a stable layout for visitors. Rather than relying on impressions or load times measured on your team’s computers, you can use free tools to measure LCP, INP, and CLS with both real-user data and lab data.
These two types of data answer different questions: real-user data shows how people actually experience your website, while lab data helps you test and identify causes in a controlled environment. Using them together helps you prioritize issues, measure the impact of optimizations, and avoid making decisions based on a single test.
What are the Core Web Vitals?
Core Web Vitals are a set of Google metrics used to assess important aspects of the page experience. The current set includes LCP, INP, and CLS. Each metric reflects a different issue, so monitoring all three gives businesses a clearer picture of the experience their website provides.

- LCP (Largest Contentful Paint): Measures how long it takes for the largest visible content element to render. This is often a hero image, video, or large block of text. A good score is 2.5 seconds or less.
- INP (Interaction to Next Paint): Measures how responsive a page is to interactions such as clicking a button, selecting a menu, or entering text. A good score is 200 milliseconds or less. INP replaced FID as a Core Web Vitals metric in March 2024.
- CLS (Cumulative Layout Shift): Measures unexpected movement of page elements during loading or use. A good score is 0.1 or less.
These thresholds are generally assessed at the 75th percentile of experience data, rather than by looking only at the average. Put simply, at least 75% of visits need to meet the good threshold for a page to be considered to pass the relevant metric. Results can differ between mobile and desktop, so you should not check just one user group.
How do real-user data and lab data differ?
Real-user data reflects actual visitors
Real-user data, often called field data, is collected from people’s experiences across different devices, networks, and browsing conditions. A common source is the Chrome User Experience Report (CrUX), an anonymized and aggregated dataset of Chrome user experiences. Google Search Console and PageSpeed Insights can display this data when a website or page has enough eligible data.

The advantage of real-user data is that it gives a picture closer to real-world usage, including on low-end phones and slow connections. However, the data is typically aggregated over a period, such as 28 days, so results will not change immediately after you deploy a fix. Some new or low-traffic pages may also lack detailed data.
Lab data helps identify the cause
Lab data is measured in a simulated environment with specific device and network settings. Lighthouse is a popular tool for generating this type of report. You can run tests multiple times under relatively consistent conditions and review technical recommendations related to images, JavaScript, CSS, or render-blocking resources.
Keep in mind that a single Lighthouse run does not represent every user. Device, network, server location, cache, and page content can all affect the results. Lab data is therefore useful for diagnosis, but it cannot replace real-user data when assessing the experience at scale.
Free tools for monitoring Core Web Vitals
- Google Search Console: Its Core Web Vitals report groups URLs by status—Good, Needs improvement, or Poor—and typically separates mobile and desktop. It is a good choice for tracking issues across multiple pages and identifying groups of URLs with shared problems. The report is based on real-user data when available.
- PageSpeed Insights: Tests a URL and combines real-user data from CrUX with Lighthouse lab results when available. It is a quick way to check how real visitors are faring and get optimization suggestions for a specific page.
- Lighthouse in Chrome DevTools: Runs a lab test for a page and shows performance metrics and opportunities for improvement. It is useful for development teams testing a staging build or identifying resources that delay content.
- Chrome UX Report and CrUX Dashboard: Provide aggregated data about Chrome experiences. For websites with eligible data, the dashboard can help track trends over time, but it does not replace detailed analysis at the individual-user level.
- Web Vitals extension: A Chrome extension that displays Web Vitals metrics as you browse. It is useful for quick checks during your work, but the results from one visit do not represent all visitors.
For many businesses, a good starting point is Search Console, which helps identify groups of URLs with issues. Then use PageSpeed Insights or Lighthouse to check priority pages. If you need deeper analysis by device type, location, or conversion flow, you can implement real-user monitoring (RUM) on your website. LilyTech can help your business choose an approach that fits your website structure and available resources.

An effective process for monitoring LCP, INP, and CLS
- List your most important pages: Prioritize your homepage, category pages, product or service pages, ad landing pages, and checkout steps. You do not need to start with every URL; focus on pages with high traffic or a direct impact on prospective customers.
- Check real-user data first: Review Search Console and PageSpeed Insights, and distinguish between mobile and desktop results. Record metrics, URL groups, and test dates to create a baseline. If CrUX data is not yet available, use lab data for an initial check and wait for real-user data to accumulate.
- Use lab tests to diagnose issues: Run Lighthouse multiple times under relatively similar conditions. For LCP, check the LCP element and resource load time. For INP, examine long JavaScript tasks and interaction responsiveness. For CLS, identify elements that shift, such as images without declared dimensions or ads inserted late.
- Prioritize fixes by impact: Optimize large images and server response times to support LCP; reduce unnecessary JavaScript and address long tasks to improve INP; reserve space for images, ads, and embedded content to limit CLS. Avoid deploying too many changes at once if you need to determine which ones made a difference.
- Retest and monitor regularly: Run lab tests after each round of fixes for quick feedback, then track real-user data over the following weeks. Compare the same device types and URL groups, and remember that changes to campaigns, content, or code can affect results.
This process makes free Core Web Vitals monitoring tools part of continuous improvement rather than a one-off check. Record both the metrics and the changes made so that development, marketing, and management teams can understand the impact of each decision.

Common mistakes to avoid when interpreting results

- Looking only at the Lighthouse score: Lab scores are useful for diagnosis but do not fully reflect real-world experience. Compare them with real-user data when possible.
- Checking only the homepage: Different page templates may use different images, scripts, and layouts. A good score on the homepage does not mean the entire website is performing well.
- Looking at the average instead of the percentile: Core Web Vitals are generally assessed at the 75th percentile. Some slow visits can still have a significant impact even when the average looks good.
- Expecting real-user metrics to update instantly: Aggregated data is delayed and depends on traffic volume. After making a fix, use a lab test to verify the technical change first, then continue monitoring real-user data.
- Chasing scores at the expense of the experience: The goal is to make pages easier to use and quicker to respond, not to pursue a single number. Consider the impact on content, functionality, and conversions.
Conclusion
To monitor LCP, INP, and CLS accurately, businesses should combine real-user data with lab data. Search Console helps identify issues across multiple URLs, PageSpeed Insights provides a combined view, and Lighthouse helps uncover technical causes. Regular measurement, prioritizing important pages, and validating results after each change will make your optimization efforts more informed.
If you need to assess website performance, set up a measurement process, or develop a Core Web Vitals optimization plan, contact LilyTech for advice on a solution that fits your business goals and resources.
Đoàn Lê Minh Anh