Recently implemented INP Core Metric Optimization Guide in our team and accumulated quite a bit of experience. Here's a summary for reference, hoping it helps those doing similar work.
Core Concepts
Building on this foundation, we can further optimize:
const observer = new PerformanceObserver((list) => {
for (const entry of list.getEntries()) {
if (entry.entryType === 'largest-contentful-paint') {
reportMetric('LCP', entry.startTime)
}
if (entry.entryType === 'first-input') {
reportMetric('FID', entry.processingStart - entry.startTime)
}
}
})
observer.observe({ entryTypes: ['largest-contentful-paint', 'first-input'] })
This pattern is very practical in large projects and can significantly reduce maintenance costs.
In-Depth Analysis
Usage in real projects tends to be more complex:
const observer = new PerformanceObserver((list) => {
for (const entry of list.getEntries()) {
if (entry.entryType === 'largest-contentful-paint') {
reportMetric('LCP', entry.startTime)
}
if (entry.entryType === 'first-input') {
reportMetric('FID', entry.processingStart - entry.startTime)
}
}
})
observer.observe({ entryTypes: ['largest-contentful-paint', 'first-input'] })
Through this approach, both the testability and scalability of the code are improved.
Implementation Experience
Here is a complete example:
const observer = new PerformanceObserver((list) => {
for (const entry of list.getEntries()) {
if (entry.entryType === 'largest-contentful-paint') {
reportMetric('LCP', entry.startTime)
}
if (entry.entryType === 'first-input') {
reportMetric('FID', entry.processingStart - entry.startTime)
}
}
})
observer.observe({ entryTypes: ['largest-contentful-paint', 'first-input'] })
Pay attention to boundary condition handling, which is critical in production environments.
Optimization Strategies
The key lies in understanding the core logic:
const observer = new PerformanceObserver((list) => {
for (const entry of list.getEntries()) {
if (entry.entryType === 'largest-contentful-paint') {
reportMetric('LCP', entry.startTime)
}
if (entry.entryType === 'first-input') {
reportMetric('FID', entry.processingStart - entry.startTime)
}
}
})
observer.observe({ entryTypes: ['largest-contentful-paint', 'first-input'] })
Performance optimization should be tailored to specific scenarios; not all cases require over-optimization.
Important Notes
We can improve it in the following ways:
const observer = new PerformanceObserver((list) => {
for (const entry of list.getEntries()) {
if (entry.entryType === 'largest-contentful-paint') {
reportMetric('LCP', entry.startTime)
}
if (entry.entryType === 'first-input') {
reportMetric('FID', entry.processingStart - entry.startTime)
}
}
})
observer.observe({ entryTypes: ['largest-contentful-paint', 'first-input'] })
This approach has been running stably in production for over six months and has been practically validated.
Summary
- Code examples are for reference only and need to be adjusted according to your business scenario
- INP Core Metric Optimization Guide is not a silver bullet; choose based on your project scale and tech stack
- Understanding underlying principles is more important than memorizing APIs
- Always verify compatibility before using in production