Performance
Performance reports show load measurements from actual page visits. Use them to find affected pages and changes over time before deciding what to optimize. Pintelly measures the experience; it does not speed up your site automatically.
Start an investigation
- Confirm analytics collection is enabled and installed on the affected page.
- Open Performance, select a period with observations and compare the same page and available device/connection breakdowns.
- Identify the metric that changed, then check whether the issue affects one page, a device group or the site more broadly.
- After a fix, compare new observations with the earlier period using equivalent filters. Feedback can show performance near a report when matching data exists.
Read measurements
| Metric | Meaning |
|---|---|
| FCP | Time until the first content is painted |
| LCP | Time associated with the largest observed content paint |
| TTFB | Wait for the first byte of the page response |
| Load | Available page load timing |
| p75 | 75% of the measured observations are at or below this value |
A p75 value is not an average. Missing metrics are not zero; browser support, page visibility and observation timing affect availability. The report reflects collected visits, not every possible connection or device.
How Pintelly behaves
Supported numeric performance measurements can continue without behavioral consent; identity and journey context require consent. A page's measurements are reported when available, and the dashboard may not reflect a change immediately. Enabling collection does not recreate historical timings.
A slow response and slow visible content are different findings. Review the affected response, content and assets with your site's developer instead of assuming that one cause explains every timing. A traffic/device mix change can also change the report without a code change.
If data is missing
Check the project, date range, page filter, analytics setting, browser support and retained history. Confirm recent visits occurred. For linked feedback context, matching data must exist; an item without performance details is not proof that the page was fast.
See SEO Analysis for how performance can contribute to page checks, or AI agents for assistant access to aggregate performance.