Skip to main content

Site Audit

Run and review page-level performance, including Core Web Vitals

T
Written by Team Pressidium

The Site Audit feature helps you review page-level performance metrics for your site, including Core Web Vitals and related loading metrics.

We are gradually rolling out this feature across our user base. If the related page is not yet visible in your Dashboard, please check back in a few days while we activate the feature for your account.

Use Site Audits to check how important pages perform, confirm whether recent changes improved performance, or investigate pages that need optimization.

You can run audits for specific URLs, schedule recurring audits, compare desktop and mobile results, and review previous audit results.

Audit scores give you a quick way to compare page performance across URLs and devices. A higher score usually indicates a better result, while lower scores may point to pages that need optimization.

Access the Site Audit page

  1. Log in to the Pressidium Dashboard.

  2. Select the website you want to audit.

  3. Select the correct environment.

  4. Open the Site Audit tab.

Section Overview

  • Site Audits, where you can run your first audit if no audit results exist yet

  • Performance metric cards, with the latest scheduled audit metrics (when data is available)

  • Search and filter controls, for finding audits by URL and filtering results by device type

  • Audit history table, where completed audits are listed after audits have been created

Site Audits

If this is what you see when you enter the page, it means that no audits have been created yet.

The page shows an empty state with the option to run your first audit.

Run your first audit

Use Run your first Audit to open the modal.

  1. Select the mapped domain.

  2. Enter the page path you want to audit.

  3. Select Mobile, Desktop, or both.

  4. Select the audit location, when available.

  5. Click Run Audit.

When the audit completes, the result appears in the audit history table.

Performance metrics

The metric cards at the top of the page show the latest Site Audit results.

Displayed metrics reflect the latest test run.

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: 800ms – 1800ms

  • Poor: above 1800ms

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 your page.

Status ranges:

  • Good: below 1.8s

  • Needs improvement: 1.8s – 3.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.5s – 4.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.10 – 0.25

  • Poor: above 0.25

Use the individual metrics, not only the score, when deciding what to improve. For example, a page may have a good TTFB but still need improvement in LCP or CLS.

Search and audit controls

Use the controls above the audit history table to find audit results, filter by device type, export results, configure scheduled audits, or run a new audit.

Search by URL

Use Search by URL to find audit results for a specific page.

Enter the full URL or part of the URL path to narrow the audit history table.

Show filter

Use the Show filter to display audit results by device type.

Available options include:

  • All

  • Desktop

  • Mobile

Export list

Click Export list to download the audit history table as a CSV file. Useful when you need to share audit results with your team, compare results offline, or include audit data in a support request.

Settings

Click Settings to configure scheduled audit URLs. In Scheduled Audits Settings, you can select which URLs to include in scheduled automated site audits.

The primary domain homepage is always included. You can add up to three web page URLs. Only mapped, non-redirect domains are supported.

To update scheduled audit settings:

  1. Click Settings.

  2. Add the URL path you want to include.

  3. Click the + button.

  4. Click Update Settings.

Audit history table

After at least one audit has been created, the audit history table shows previous Site Audit results for tested URLs.

Each row includes the tested URL, audit type, device type, performance metrics, audit date, score, and available actions.

The table includes the following information:

URL

Shows the page that was audited. Labels below the URL show whether the audit was Manual or scheduled, and whether it ran for Desktop or Mobile.

Performance metrics

The metric columns show the measured results for that audit run:

  • TTFB shows Time to First Byte.

  • LCP shows Largest Contentful Paint.

  • TBT shows Total Blocking Time.

  • CLS shows Cumulative Layout Shift.

  • FCP shows First Contentful Paint.

Use these values to compare audit runs and identify whether performance improved or declined over time.

Date

Shows when the audit was completed. Use this column to compare results before and after site changes, cache changes, or optimization updates.

Score

Displays the audit score for that result. Use the score as a quick summary, then review the individual metric values for more detail.

Rerun

Click Rerun to repeat the audit for the same URL and device type. Use this after making performance, cache, plugin, theme, or content changes.

See details

Click See Details to open the detailed report for that audit result. Use the detailed report to review page-level findings and recommendations.

Common questions

Why do the metric cards show dashes?

The metric cards may show dashes when no scheduled test has run yet or when there is not enough data to display the metric.

Run an audit or wait for the next scheduled test, then check the page again.

Why are desktop and mobile results different?

Desktop and mobile audits use different conditions. Mobile pages may load different layouts, images, scripts, or third-party resources. Review both views when optimizing important pages.

Should I use the homepage only?

No. The homepage is important, but you should also audit key landing pages, product pages, checkout flows, forms, and high-traffic content pages.

Does rerunning an audit change the site?

No. Rerunning an audit tests the URL again. It does not change your site settings or content.

Common issues and solutions

The audit was unsuccessful

Symptom: The audit row shows an unsuccessful audit message.

Likely causes:

  • The URL is invalid

  • The page is not publicly accessible

  • The page returned an error

  • The request was blocked by a security rule

  • The page took too long to respond

Resolution steps:

  1. Open the URL in a private browser window.

  2. Confirm the page loads without requiring a login.

  3. Check that the URL belongs to the selected site and environment.

  4. Rerun the audit.

  5. If the issue continues, use Contact Support.

The page score is lower than expected

Likely causes:

  • Large images

  • Render-blocking scripts or styles

  • Third-party scripts

  • Slow origin response

  • Layout shifts from images, ads, fonts, or embedded content

  • Cache bypass for the tested URL

Resolution steps:

  1. Open the audit details.

  2. Identify which metric needs attention.

  3. Check whether the page is cacheable.

  4. Review large assets and third-party scripts.

  5. Rerun the audit after making changes.

The audit result did not improve after changes

Likely causes:

  • Cached assets still reflect the previous version

  • The tested URL is bypassing cache

  • The change did not affect the measured metric

  • Third-party scripts are still slowing the page

  • Mobile and desktop results are being compared incorrectly

Resolution steps:

  1. Confirm you are reviewing the correct URL and device type.

  2. Purge cache if needed.

  3. Rerun the audit.

  4. Compare the same metric before and after the change.

  5. Review the audit details for remaining issues.

Verification

After running or rerunning an audit:

  1. Confirm the audit appears in the Site Audits list.

  2. Check that the URL and device type are correct.

  3. Review the score and metric values.

  4. Open See Details for a deeper review.

  5. Rerun the audit after making performance changes.

Best practices

Audit more than the homepage. Include pages that matter to users and business outcomes, such as landing pages, product pages, checkout pages, forms, and high-traffic articles.

Compare the same page, device type, and metric when measuring progress. This makes before-and-after results easier to understand.

Run a new audit after major changes, including plugin updates, theme changes, cache setting changes, DNS changes, or deployment work.

Use audit results together with cache analytics and performance analytics. Site audits show page-level performance, while analytics help you understand broader traffic and caching behavior.

Need help?

Contact Support if audits keep failing, results look inconsistent, or you need help interpreting a performance issue.

Include:

  • Site name

  • Environment

  • URL being audited

  • Device type

  • Audit date and time

  • Screenshot of the audit result

  • Any recent changes to plugins, theme, caching, DNS, or security settings

Did this answer your question?