Measure a representative visit

Choose one page and a realistic screen size. Record a baseline in the browser Network and Performance panels. Note the cache state and any throttling, then repeat under the same conditions. A local trace is useful for debugging. Field metrics summarize actual visits and can differ because devices, networks and routes differ.

Identify what the trace is showing. LCP measures when the largest eligible content candidate is painted. INP concerns interaction responsiveness and CLS describes unexpected layout movement. A short page-load trace alone does not establish the site's field results.

Find which part of the visit is waiting

If the main document response is late, inspect redirects, cache headers and comparable server requests. WebToolspire's TTFB Checker reports a Worker-side response-header observation and needs a configured API. Use the browser document request to diagnose the visit you are tracing.

If the document arrives quickly but the largest visible image begins loading late, inspect how the browser discovers it. If the image arrives and paint is still late, examine stylesheet and main-thread work around that point. Reducing file size cannot fix every delay.

Try the TTFB Checker →

Match a heavy image to its display slot

Suppose a 2400-pixel image is downloaded for a hero that renders at about 640 CSS pixels. Check the actual received resource and device pixel ratio, then generate variants and compare their visual quality. Describe the layout slot accurately in sizes so the browser can choose an appropriate resource. Keep aspect ratio predictable with width and height.

Prefer discovery at initial HTML for a likely LCP image. Reserve lazy loading for images farther down the page. The Image Size Analyzer reports local dimensions and bytes. Encoding and evaluating new variants is a separate step.

<img src="/hall-640.webp"
     srcset="/hall-640.webp 640w, /hall-1280.webp 1280w"
     sizes="(max-width: 672px) calc(100vw - 32px), 640px"
     width="640" height="360" alt="North Hall with tables set for a workshop">

Try the Image Size Analyzer →

Make one change and rerun the same trace

For heavy CSS or JavaScript, look for unused bundles, duplicated code, and work triggered before it is needed. Minifiers can shrink individual files but do not replace bundling, deferral, or testing. Review the output and compare actual network transfer, which also depends on compression and caching.

Record the selected image or script, transferred bytes, and the trace event you meant to improve. Repeat on another representative viewport. If the asset is smaller but the wait is unchanged, follow the next longest dependency before making more edits.

Try the CSS Minifier →

References and further reading