liveBook · Manning

Frontend load time metric

As explained in AI Model Evaluation

The elapsed time required for a web page to load, often summarized across request-time percentiles.

Frontend load time metrics measure how quickly page content appears to users. Slow loading can weaken engagement or prompt users to leave, so a model with good predictions may still deliver a poor product experience if its results arrive too late. section 4.2.1 section 4.0

Measure the experience users actually see. Time to First Byte (TTFB) is the interval from a client request to the first byte of response data; fully loaded time covers the page and all AI content. High TTFB can indicate delays in inference or feature retrieval, but it does not by itself describe the complete loading experience. section 4.2.1

A 100 ms increase in model inference time does not necessarily add 100 ms to page load time: asynchronous loading, caching, and progressive rendering can change what users perceive. Examine frontend rendering alongside backend, model-serving, and infrastructure metrics to locate the delay before optimizing. section 4.1 section 4.2.4 section 4.4.2

Use load time metrics to guide product decisions:

  • Track averages and percentiles such as p50, p95, and p99, and compare them with a baseline. section 4.4.3 section 4.4.2
  • Pair system measurements with user metrics such as click-through, bounce, abandonment, and downstream consumption. section 4.4.3
  • Consider caching, query optimization, edge delivery, lazy loading, or precomputed predictions according to the bottleneck. Check the effects on model quality, reliability, and cost. section 4.2.1 section 4.2.4

Testing a slower recommendations page

A movie recommendation experiment adds backend delay to one control and five degradation variants, with tests replicated by device type. It tracks load time percentiles and user behavior to find how sensitive the experience is to latency. On mobile, the control averages 1,050 ms with 23.5% click-through; the 500 ms added-delay variant averages 1,552 ms with 8.7% click-through. section 4.4.3

Table 4.4 Latency Degradation Test Results on Mobile
Variant Cell
Added Latency
Avg Page Load Time
CTR
Bounce Rate
Control
0ms
1050ms
23.5%
27.8%
Test Variant 1
100ms
1155ms
22.7%
29.1%
Test Variant 2
200ms
1250ms
20.2%
32.7%
Test Variant 3
300ms
1360ms
16.4%
39.5%
Test Variant 4
400ms
1455ms
12.2%
48.3%
Test Variant 5
500ms
1552ms
8.7%
56.9%

Compare average page load time, click-through, and bounce rate across the mobile experiment variants. section 4.4.3

Latency degradation tests deliberately worsen the experience for some users. Limit exposure and establish guardrails and stop conditions before running them. section 4.6

How AI Model Evaluation covers it

How deep it goes
Defines TTFB and fully loaded time, then develops cross-layer measurement and a latency degradation experiment.
Examples
Uses a streaming recommendations page and a device-specific latency degradation A/B test with mobile results.
What you can do after
Evaluate load-time sensitivity by comparing latency variants with user behavior and identifying bottlenecks across system stages.
How it connects
Connects page load time with model inference latency, caching, rendering, and user engagement.

Also explained in

Compare how 3 books explain frontend load time metric →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of AI Model Evaluation. The section links point to the parts of the book it draws on.