Asterpath · Revision 4
Supporting evidence
Explain the mobile wait with a bounded lab example.
The fictional landing page has a mobile LCP of 5.1 seconds and a desktop LCP of 2.0 seconds.
Fictional, not a scanner result. FICTIONAL ILLUSTRATIVE SAMPLE. Asterpath, its product, evidence, findings and measurements are invented. No Asterpath application was inspected and no scanner was executed. These are original GadirLabs illustrations, not native vendor exports.
What the fictional evidence shows
| Measure | Illustrative value | Evidence boundary |
|---|---|---|
| Mobile lab LCP | 5.1 seconds | Median of three invented cold runs using an emulated throttled profile. |
| Desktop lab LCP | 2.0 seconds | Separate invented desktop profile. |
| Mobile lab CLS | 0.04 | Lab layout shift; not a field distribution. |
| Field INP / real-user data | Unavailable | No real-user dataset is represented. |
| Main content asset | 2.4 MB hero image, requested late | An invented bottleneck, not a real request waterfall. |
What it means
F06 ties the delayed main content to an actionable image/loading change. Neither these invented numbers nor a lab score establishes actual conversion loss.
What would establish a fix
Repeat equivalent profiles against a new candidate and meet the agreed mobile LCP budget of 2.5 seconds or less without introducing layout shift; report field data separately when available.
This page and its JSON are two views of the same original illustration. They are not separate findings or independent corroboration. A real client record would identify actual versions, inputs, outputs and evidence limits.