Identify issues with core web vitals in real time and improve SEO.
Use Marfeel’s core web vitals module to track the performance of your site in the areas that most affect Google rankings, including LCP, CLS, INP, and more. Use this module to prioritize the most damaging issues impacting your score.
Never lag behind: access core web vitals data in real time without waiting for an updated CrUX report. Marfeel bases core web vitals data on real user sessions as opposed to synthetic traffic or server simulations. All user pageviews are tracked using the Performance Observer API.
RUM data is especially important for INP, the newest Core Web Vital introduced by Google, which will replace FID in March 2024. INP is measured based on RUM. This introduces complexity, variability, and difficulty in diagnosing issues. A page may perform just fine on your high-end laptop, but your site visitors may not be as lucky.
Gathering more feedback through a RUM solution like Marfeel provides contextual data that highlights what specific interaction was responsible for the INP value. Whereas Google Search Console groups pages and gives a consolidated INP value with sample URLs, Marfeel provides granular data down to the CSS selector [link to Offenders]. Similarly, PageSpeed Insights often lacks enough specific URL data to show real user information and falls back on consolidated data that lacks actionable insights.
Core web vitals insights are located under Site Technology → Web Vitals.
The time it takes for a page’s largest image or text block to render relative to when the page first loads. A good LCP score is under 2.5 seconds.
Layout shifts are reported when an element that is visible within the viewport changes its start position between two frames. A good CLS score is less than 0.1.
INP surfaces frozen, glitchy, or low-quality experiences during a user’s visit to a page by measuring the time from when a user clicks or types on a page until the page is next able to update. It measures the slowest action on the page, which should not exceed 200 ms to be considered a good INP score.
A really, really, REALLY important thing about INP is it is measured from real users RUM. A page may seem fine on your high-end desktop computer, or even your high-end phone, but your site visitors may not be as lucky or may be using the site differently. That does introduce complexity, variability, and difficulty in diagnosing issues. Gathering more feedback through a RUM solution helps get more fine grain information.
The time between when a user attempts to interact with a page, for example, by clicking a link, and when the browser starts processing event handlers in response to the request. A good FID score is under 100 ms.
The time between the request for a resource and when the first byte of a response begins to arrive. Although not considered a core web vital, it is a foundational metric that precedes every other loading metric for navigation requests, including LCP. A good TTFB score is under 800 ms.
The DOM (Document Object Model) defines the logical structure of documents, and the DOMContentLoaded fires when all the nodes in the page have been constructed in the DOM tree without waiting for images and CSS to finish loading.
It’s a useful event in terms of the speed of your page because there’s less to load before the event fires. For SEO purposes, note that Google does not consider this a reliable metric for page performance.
When an object has been loaded. Onload is most often used within the element to execute a script once a web page has completely loaded all content such as images and iframe.