> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Page Load to First Interaction, FullStory

> Page Load to First Interaction for FullStory stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained)  •  **Category:** [Page Analysis](/nerve-centre/connectors#connectors-by-type)

## At a glance

> **Page Load to First Interaction** measures how long a visitor waits, from the page beginning to load, before they take their first action on it. FullStory captures this from the session timeline. It is a real-world responsiveness measure: not a synthetic lab score but the actual lag your visitors felt before they could engage. A rising value means pages feel sluggish, and sluggish pages quietly shed engagement and conversion well before anyone files a complaint.

|                       |                                                                                                                                                                  |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**    | The typical elapsed time between page load starting and the visitor's first interaction, captured by FullStory across sessions in the period.                    |
| **Sample type**       | Backend API data from FullStory, refreshed on the standard data refresh.                                                                                         |
| **Why it matters**    | It is felt responsiveness, the delay real visitors experienced before they could act. Slow first interaction correlates with higher bounce and lower conversion. |
| **Reading the value** | Compare the current period to the prior period. A rising time points to heavier pages, slower scripts, or render-blocking resources.                             |
| **Currency**          | count                                                                                                                                                            |
| **Time window**       | `30D vsP`                                                                                                                                                        |
| **Alert trigger**     | `-`                                                                                                                                                              |
| **Sentiment key**     | `fs_page_load_to_first_interaction`                                                                                                                              |
| **Roles**             | owner, marketing                                                                                                                                                 |

## Calculation

Calculated automatically from your FullStory data. Vortex IQ reads the interval between page-load start and the first captured interaction on the session timeline and summarises it across sessions for the period. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

## Worked example

*A representative reading of **Page Load to First Interaction** for a typical merchant on FullStory.* Suppose the metric drifts from 1.4 seconds to 2.6 seconds over a month. The change tracks a new hero-video block on the homepage that blocks interaction until it buffers. Lazy-loading the video restores responsiveness. The slowdown never threw an error, so only a felt-experience metric like this one would have caught it. For deeper investigation, use Vortex Mind to see which templates slowed; for natural-language exploration, ask Ask Viq which pages feel slowest to visitors.

## Sibling cards merchants should reference together

| Card                                                                                                             | Why merchants reach for it                                |
| ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
| [`fs_rage_click_rate`](/nerve-centre/kpi-cards/fullstory/rage-click-rate)                                        | Slow pages drive impatient repeat clicks.                 |
| [`fs_worst_frustration_pages`](/nerve-centre/kpi-cards/fullstory/worst-frustration-pages)                        | Slow pages often top the frustration ranking.             |
| [`fs_xc_landing_page_perf_vs_bounce`](/nerve-centre/kpi-cards/fullstory/landing-page-performance-vs-frustration) | Ties page speed to frustration at the landing-page level. |
| [`fs_scroll_depth_avg`](/nerve-centre/kpi-cards/fullstory/avg-scroll-depth)                                      | A companion page-engagement signal.                       |

## Reconciling against the vendor's own dashboard

**Where to look in FullStory's own dashboard:**

FullStory exposes timing on the session timeline and through its performance-oriented reporting. Confirm period boundaries and page scope match the Vortex IQ profile to reconcile cleanly.

**Why the Vortex IQ value may legitimately differ:**

| Reason                                                                                                                  | Direction | What to do                              |
| ----------------------------------------------------------------------------------------------------------------------- | --------- | --------------------------------------- |
| **Summary statistic.** A median and a mean of the same interval can read very differently when a few sessions are slow. | Variable  | Confirm which statistic each view uses. |
| **Period boundary.** Vortex IQ uses 30-day rolling by default; FullStory dashboards may use calendar periods.           | Variable  | Match the period range.                 |
| **Device and network mix.** A shift toward slower devices or networks moves the figure independent of code.             | Variable  | Check the device split.                 |

**Cross-connector reconciliation:** complement with the landing-page performance and frustration cards. For divergence investigations, use Vortex Mind.

## Known limitations / merchant FAQs

**Q: How often does Page Load to First Interaction update?**
The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard.

**Q: Is this the same as a Core Web Vitals score?**
No. Core Web Vitals are lab and field web-performance metrics; this is FullStory's observed time to first real interaction. They are related but measured differently, so treat them as complementary.

**Q: Why does my FullStory dashboard show a different number?**
The most common reasons are which summary statistic is used, period boundaries, and device or network mix. Match these before assuming a real divergence.

**Q: Can I customise the alert threshold?**
Sensitivity thresholds are configurable per profile in the Sensitivity tab. Set a threshold that reflects acceptable responsiveness for your audience.

***

### Tracked live in Vortex IQ Nerve Centre

*Page Load to First Interaction* is one of hundreds of KPI pulses Vortex IQ tracks across FullStory and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

[Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.
