How do I turn on Core Web Vitals collection?
Performance data is collected only when you add thedata-web-vitals attribute to your tracking script — it’s off by default. Add it once and re-deploy:
What are the five Core Web Vitals?
Each metric captures a different part of the loading and interaction experience. tinyanalytics collects all five and marks each against its standard “good” threshold:
LCP, INP, and CLS are the three official Core Web Vitals; FCP and TTFB are supporting diagnostics that help explain a poor LCP.
Why does tinyanalytics show percentiles instead of an average?
Performance is reported at percentiles because averages hide your slowest experiences. A single very slow page load barely moves an average but is exactly the experience you want to find. tinyanalytics reports four percentiles for every metric:- p50 — the median visit. Half of loads were faster than this.
- p75 — the headline percentile Google uses to grade Core Web Vitals. This is the default.
- p90 and p99 — your slowest 10% and 1% of loads.
How do I read the performance chart?
The chart plots your selected metric over time, with one line per visible percentile so you can watch p75 and p99 move independently. Threshold lines mark the “good” and “needs improvement” boundaries, so a line crossing into the upper band is an at-a-glance regression. Use the bucket selector to switch between hourly, daily, weekly, and monthly points.How do I find which pages or devices are slow?
The breakdown table splits your selected metric and percentile across six dimensions, one tab each: Pages · Countries · Regions · Browsers · Operating Systems · Devices This is how you find what is slow. A high p75 LCP overall might trace to one heavy landing page, one country far from your servers, or one browser. Click a row to filter the whole dashboard to it — the same drill-down a breakdown or map click performs.How do I spot a performance regression?
Turn on period comparison to add a baseline and a change indicator to each metric card. Performance comparison is aware that lower is better for Core Web Vitals: a rising LCP is a regression, so its change indicator turns red with an up arrow, not green.Because vitals are captured only when a metric actually fires before the visitor leaves, a metric can be missing on some loads (for example, INP needs an interaction). tinyanalytics skips missing values rather than counting them as zero, so each percentile reflects only real measurements.
Frequently asked questions
Why is my tinyanalytics Performance report empty?
Why is my tinyanalytics Performance report empty?
Core Web Vitals collection is off by default. tinyanalytics collects performance data only when you add the
data-web-vitals attribute to your tracking script and re-deploy. Until data arrives, the Performance report shows a notice explaining how to enable collection.Which percentile should I use for Core Web Vitals?
Which percentile should I use for Core Web Vitals?
Use p75, the headline percentile Google uses to grade Core Web Vitals. It is also the tinyanalytics default, alongside LCP. Read p50 for the median visit, and p90 and p99 to see your slowest 10% and 1% of loads.
Why does a rising LCP show as a red increase instead of green?
Why does a rising LCP show as a red increase instead of green?
Because lower is better for Core Web Vitals. tinyanalytics period comparison knows this, so a rising LCP is treated as a regression and its change indicator turns red with an up arrow rather than green. Turn on period comparison to add a baseline to each metric card.
What are the good thresholds for each Core Web Vital?
What are the good thresholds for each Core Web Vital?
tinyanalytics marks each metric against its standard good threshold: LCP ≤ 2,500 ms, INP ≤ 200 ms, CLS ≤ 0.1, FCP ≤ 1,800 ms, and TTFB ≤ 800 ms. LCP, INP, and CLS are the three official Core Web Vitals; FCP and TTFB are supporting diagnostics that help explain a poor LCP.
Related
Configure the tracking script
Add
data-web-vitals to start collecting performance data.Dashboard overview
Your traffic metrics and breakdowns alongside performance.
Compare periods
Add a baseline to spot performance regressions.
Filter your data
Narrow performance to one page, country, or device.