Analyze
Performance and Core Web Vitals
Measure LCP, CLS, INP, FCP and TTFB on any page with Pickode, then find the LCP element, render-blocking resources, heavy images and third parties.
Updated October 20, 2026
The Performance panel measures Core Web Vitals on the page you’re viewing and shows what slows it down. Use it before a redesign, after a change, or to explain to a client why a page feels slow.
Test a page
-
Open the page you want to test in your browser. For a fresh load, use the reload without cache in Debug first.
-
In Pickode’s Analyze section, open Performance.
-
Read LCP, CLS, INP, FCP and TTFB.
-
With Pro, go through the details and suggestions, then add them to a client report with prioritized fixes.
What the panel measures
| Area | Details |
|---|---|
| Metrics | LCP, CLS, INP, FCP, TTFB |
| LCP | The LCP element and whether it uses fetchpriority |
| Page weight | Weight by resource type |
| Blocking | Render-blocking resources and long tasks |
| Images | Oversized, not lazy-loaded, without dimensions, in a legacy format |
| Third parties | Third-party resources loaded by the page |
Reading the three Core Web Vitals
LCP measures loading, INP responsiveness and CLS visual stability. Google considers them good at LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1, measured at the 75th percentile of real visits. Pickode measures the page as it loads in your browser, so treat the numbers as a lab check of that load, and start from the LCP element and the blocking resources when you look for causes.
Fixing heavy images
When the panel flags oversized or legacy-format images, the image optimizer in Debug (Pro) converts them to WebP or JPEG (AVIF where the browser can encode it) and resizes them to the displayed size × screen density, all in your browser, with a ZIP to download.
Free vs Pro
| Free | Pro | |
|---|---|---|
| Scores (LCP, CLS, INP, FCP, TTFB) | ✓ | ✓ |
| Details and suggestions | — | ✓ |
| Speed section in the client report | — | ✓ |
See pricing.
Related
Still stuck?Contact us