chrome_page_load_summary
Summarizes each page navigation in a Chrome trace, returning navigation ID, URL, and key timings (FCP, LCP, DCL, load) to compare load performance across navigations.
Instructions
Summarize each page navigation in a Chrome trace: navigation id, URL, raw boundary timestamps, FCP / LCP / DCL / load timings in ms. Read-only.
Use when: comparing page-load timings across navigations, finding slow loads, baselining web-vitals before/after a change. Prefer over hand-joining chrome.page_loads — schema is already correct.
Don't use for: non-Chrome traces (will error). For sub-event timings inside one navigation, drop to execute_sql against the chrome.page_loads module.
Parameters: optional limit (default 100, capped at 5000) and max_string_len. Operates on the loaded trace.
Output: metadata-first JSON; row_count exact; truncated=true means more rows exist; string_truncated=true means shortened text.
Empty result: no navigations occurred during capture (e.g. trace started after the page was already loaded).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Optional max rows to return. Defaults to 100 and is capped at 5000. Must be > 0 when set; accepts both numbers and numeric strings. | |
| trace_id | No | Optional trace id returned by `load_trace`. Omit to use the active trace. | |
| max_string_len | No | Optional per-string-cell character cap applied to returned Chrome-tool rows only. Unset preserves full strings for precision; accepts both numbers and numeric strings. Must be > 0 when set. |