Menu
INP Debugger
DebugBear's INP Debugger is a tool complementary to the new change within Google. Namely, Google made the switch from First Input Delay(FID) to Interaction to Next Paint (INP) in March 2024.
Why use INP Debugger?
Google made the March 2024 adjustment to make website responsiveness more accurate. In other words, it allows Google to better gauge how responsive a Web site is. INP Debugger measures how long a page takes to respond when a button or link is clicked. If this takes too long, users may think the button or link is not working, making it more likely that they will leave the site.
What does DebugBear's INP score tell you?
The score shows in milliseconds how long it takes for a button or link to respond and which of these two elements takes the longest to respond. Are there multiple elements on the page? Then they are shown separately from each other. It is also good to know that the INP Debugger shows two scores:
- Real User Google Data
- INP Debugger Result
They do this because there are always other factors that affect the speed of buttons and links. A user may have a slow computer or navigate the page in a different way.
A good INP score
To ensure that your website is responsive, the best guideline is that 75% of pages load quickly, on both mobile devices and computers:
- If a page responds in 200 milliseconds or less, that's fast.
- If a page responds between 200 and 500 milliseconds, the speed could be better.
- If it takes longer than 500 milliseconds for a page to respond, it is slow and needs work.
Tip from OMA: always set the test site to mobile