Skip to main content

Site Audit results

Review detailed audit metrics, track performance over time, and inspect Lighthouse findings for a specific URL.

A
Written by Admin account

The Site Audit details page shows the full results for a specific audit run.

To open it, go to Websites and click the site you want to manage. Then go to Performance > Site Audit and click See Details for an audit result.

Use this page to review detailed performance metrics, compare results over time, and inspect the Lighthouse report for the audited URL.

Sections included

  • Audit URL

  • Audit type and device

  • Audit date

  • Performance metric cards

  • Progress over time chart

  • Page weight

  • Total requests

  • Lighthouse report

  • Audit history

Audit context

At the top of the page, you can see the audited URL, audit type, device type, and audit date.

Use this information to confirm that you are reviewing the correct audit result.

You can also use:

  • Back to All Audits to return to the Site Audit list.

  • Date selector to view a different audit result.

  • See Audit History to jump to previous audit runs.

Performance metrics

The metric cards summarize the selected audit result.

Each card shows the measured value, status, and change compared with the previous relevant result when available.

The page includes:

  • First Contentful Paint (FCP)

  • Largest Contentful Paint (LCP)

  • Cumulative Layout Shift (CLS)

  • Time to First Byte (TTFB)

  • Total Blocking Time (TBT)

  • Speed Index

First Contentful Paint (FCP)

First Contentful Paint (FCP) measures how long it takes the browser to render the first piece of DOM content after a user navigates to the page.

Status ranges:

  • Good: below 1.8s

  • Needs improvement: 1.8s3.0s

  • Poor: above 3.0s

Largest Contentful Paint (LCP)

Largest Contentful Paint (LCP) measures when the largest content element in the viewport is rendered to the screen.

This approximates when the main content of the page is visible to users.

Status ranges:

  • Good: below 2.5s

  • Needs improvement: 2.5s4.0s

  • Poor: above 4.0s

Cumulative Layout Shift (CLS)

Cumulative Layout Shift (CLS) measures the largest burst of layout shift scores for unexpected layout shifts during the lifecycle of a page.

Status ranges:

  • Good: below 0.10

  • Needs improvement: 0.100.25

  • Poor: above 0.25

Time to First Byte (TTFB)

Time to First Byte (TTFB) measures how quickly your server responds to requests.

Lower values indicate faster server performance.

Status ranges:

  • Good: below 800ms

  • Needs improvement: 800ms1800ms

  • Poor: above 1800ms

Total Blocking Time (TBT)

Total Blocking Time (TBT) measures the total amount of time that a page is blocked from responding to user input, such as mouse clicks, screen taps, or keyboard presses.

Status ranges:

  • Good: below 200ms

  • Needs improvement: 200ms600ms

  • Poor: above 600ms

Speed Index

Speed Index measures how quickly content is visually displayed during page load.

Lower values indicate faster visual rendering.

Status ranges:

  • Good: below 3.4s

  • Needs improvement: 3.4s5.8s

  • Poor: above 5.8s

Progress over time

The Progress over time chart shows historical results for the selected metric.

Use the filters to change the view:

  • Device filters results by device type.

  • Metric selects the performance metric shown in the chart.

Use this chart to compare audit results before and after changes to caching, optimization settings, plugins, themes, or page content.

Page weight, requests, and CO2 emissions

This section shows how much data the audited page loads, how many network requests it makes, and the estimated CO2 emissions for the page load.

Use these metrics to identify pages that may be heavy because of large images, scripts, stylesheets, fonts, third-party tools, embeds, or other assets.

Page weight

Page weight shows the total size of the resources loaded during the audit.

A larger page weight can increase load time, especially for visitors on slower networks or mobile devices.

If page weight is high, review large images, videos, fonts, JavaScript files, CSS files, and third-party assets.

Total requests

Total requests shows the number of network requests made while loading the page.

A high request count can slow down rendering because the browser needs to download and process more resources.

If total requests are high, review unnecessary scripts, duplicate assets, third-party tags, plugin assets, and resources loaded on pages where they are not needed.

Estimated CO2 emissions

Estimated CO2 emissions shows the estimated carbon impact of loading the audited page.

Use this metric as a directional indicator of page efficiency. Heavier pages and pages with more requests usually require more data transfer and processing, which can increase the estimated emissions.

Lighthouse report

The Diagnose Performance Problems – Lighthouse Report section shows the detailed Lighthouse audit for the selected page.

Use this report to review:

  • Performance score

  • Accessibility score

  • Best Practices score

  • SEO score

  • Detailed metric results

  • Filmstrip or load timeline

  • Page-level findings and recommendations

For a deeper explanation of Lighthouse and how to use it when reviewing performance results, read Analyzing Website Performance Tools: Lighthouse.

Audit history

The Audit History table shows previous audit runs for the same URL.

It includes:

  • Type

  • Display

  • Date

  • Score

Use this table to compare past results for scheduled or manual audits across desktop and mobile.

Click See Details to open another audit result.


Best practices

  • Confirm the audited URL, device type, and audit date before comparing results.

  • Compare metrics across similar audit types, such as desktop with desktop or mobile with mobile.

  • Use Progress over time to evaluate trends instead of relying on a single audit.

  • Review the Lighthouse report for page-level findings and recommendations.

  • Rerun an audit after cache, optimization, plugin, theme, or content changes.

Did this answer your question?