Help Center
Go back to application
Help Center
Go back to application
Dashboard
KPI Dashboard
Events
Events DashboardEvents APIEvents App
Sessions
Session Analytics
Technology
Technology OverviewLoad TimeJavascript ErrorsFailed Calls
Segmentation
Segments ReportSegmentation Definitions
Impacted Revenue
Impacted Revenue
Frustration
Frustration Signals
Acquisition
Acquisition Tagging - dataLayerAcquisition Tagging - Open Graph and Schema.org
Integrations
Integrating Slack with Webeyez

Load Time

Load Time Report Overview

The Load Time Report is a powerful tool designed to help you monitor, analyze, and optimize your website’s performance. Here's how to make the most of it:

Navigating the Report

Left Side: Page Breakdown

By default, the left-hand panel displays individual page URLs. Each number next to a page represents the total number of sessions during your selected date range.

Need a faster way to analyze?

Group By: Use the dropdown to group pages by:

  • Device type
  • Browser used
  • Country of the visitor

Search Bar: Quickly locate a specific page by entering keywords or URLs.

Report Details

The right-hand side of the screen is where the magic happens. It gives you a full picture of your website’s load performance, including:

  • Largest Contentful Paint (LCP): Measures how long it takes for the largest content element (like an image or text block) to load — a key indicator of perceived load speed.
  • Interaction to Next Paint (INP): Tracks how quickly the site responds after a user interacts. Lower INP values mean a faster, smoother experience.
  • Cumulative Layout Shift (CLS): Measures how visually stable your page is by detecting unexpected layout shifts. Lower values mean fewer jarring movements and a more pleasant experience.
  • SPA Load Time: Focuses on how long it takes for a Single Page Application (SPA) to become fully interactive.
  • Signal Page Application Load Time: Captures the total time it takes for your page to be usable.
  • Load Time Breakdown: Breaks down overall load time into server, browser, and network components for targeted optimization.
  • Load Time Server Breakdown: Digs into the backend to identify server-side factors contributing to slower load times.
  • Load Time Browser Breakdown: Identifies browser-related elements (e.g., rendering, parsing) that may be causing delays.
  • Page Load Time Histogram: Visualizes the distribution of page load times across sessions, making it easy to spot performance spikes or patterns.
  • Number of Page Views: Displays the total count of views for the selected time frame.

These metrics allow you to zero in on areas that may be slowing down your website.

Export & Customize

Click the download arrow on any chart to export the data.
Want to clean up a chart? Click on any legend item to remove that data line from view.

Benchmark Lines: What They Mean

Some charts include green and orange benchmark lines:
Green Line: Represents good performance (aligned with Google’s Core Web Vitals).
Orange Line: Indicates a threshold where performance needs improvement.

📌 Tip: Pages with metrics above the orange line can impact your SEO — so keep an eye out!

Why This Report Matters

The Load Time Report helps you:

  • Spot underperforming pages
  • Understand how different devices and geos affect load speed
  • Take action to improve your site’s speed and SEO rankings

How does Webeyez measure load time metrics?


Google Core Vitals - All collected with Google Web-Vitals library

  • LCP (Largest Contentful Paint):
    This metric tracks when the largest visible content element on the page is fully rendered. Typically, it marks when the main content (such as an image or large block of text) has finished loading.
  • INP (Interaction to Next Paint):
    This measures how long it takes for the page to respond to user interactions, accounting for any delay in rendering the next visual change after an interaction, such as clicking on a button. The value is capped at 10 seconds (10,000 ms) to avoid overly large values.
  • CLS (Cumulative Layout Shift):
    This metric tracks how much the page layout shifts during loading, which affects the visual stability. A shift occurs when elements on the page move around unexpectedly. It is collected using a function that monitors layout changes and reports the total shift.

Load Time Metrics:

  • FCP (First Contentful Paint):
    Measures when the first piece of content (like text or an image) is rendered on the page. This helps assess how soon users see something on the screen after navigating to the page.
  • FID (First Input Delay):
    Measures the delay between a user’s first interaction with the page (like clicking a button or tapping a link) and the time when the browser is actually able to respond to that interaction. This delay is tracked from the user’s input until the browser is ready to handle it.
  • Page Load Time (PLT):
    This metric measures how long it takes for the page to fully load after the navigation starts. It is calculated by taking the difference between the time the page's loadEventEnd and the page's navigationStart (i.e., the time when the browser starts loading the page).
  • Server Time:
    This represents the time spent waiting for the server’s response, calculated as the difference between responseEnd and requestStart.
    • Server Time Breakdown - Content Download:
      This measures how long it takes the server to respond with the requested content. It is calculated by subtracting the responseStart (the start of the server response) from the responseEnd (the end of the response).
      Server Time Breakdown - Response Latency:
    • This is the time spent between when the request was sent to the server and when the server began responding. It’s the difference between the responseStart and requestStart timings.
  • Network Time:
    Measures the time from when the navigation starts to when the browser starts making the network request.
  • Browser Time:
    Measures the time spent by the client (browser) after the server has responded, from the time responseEnd to loadEventEnd.
    • DOM Content Loaded Time:
      This measures the time it takes for the HTML document to be completely loaded and parsed, excluding stylesheets, images, and subframes. It is determined by calculating the difference between the domContentLoadedEventEnd and navigationStart.
    • DOM Processing to Interactive Time:
      Measures the time it takes for the DOM (Document Object Model) to be fully processed and interactive, specifically the time from when the server response finishes to when the DOM becomes interactive.
    • DOM Interactive to Complete Time:
      This measures the time between the point when the DOM is interactive and when the document is fully loaded and parsed.

Browser Support

The load time metrics code has been tested and will run without error in all major browsers as well as Internet Explorer back to version 9. However, some of the APIs required to capture these metrics are currently only available in Chromium-based browsers (e.g. Chrome, Edge, Opera, Samsung Internet).

Browser support for each function is as follows:

  • CLS (Cumulative Layout Shift) - Chromium
  • FCP (First Contentful Paint) - Chromium, Firefox, Safari
  • FID (First Input Delay) -  Chromium, Firefox (Deprecated)
  • INP (Interaction to Next Paint) -  Chromium
  • LCP (Largest Contentful Paint) : Chromium, Firefox

 

If you’re looking to boost site speed, deliver a smoother customer experience, and stay ahead of the SEO game — the Load Time Report is your go-to.

Have questions? Reach out to our support team — we're happy to help!

Was this article helpful?

Powered by Product Fruits