> For the complete documentation index, see [llms.txt](https://help.appplaza.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.appplaza.app/speed-optimizer/speed-audit.md).

# Speed audit

{% hint style="info" %}
**Who can use this feature?**

Speed audit is available on **all plans**. The number of audits you can run depends on your plan:

* **Free / Basic** — 1 audit every 7 days
* **Pro** — 1 audit every 24 hours
* **Expert** — unlimited
  {% endhint %}

### What is Speed audit?

Different from [Analytics](https://app.gitbook.com/o/J4yqZKSNdRshQVCe8UnM/s/e2UyZIDUxUYqjZFfFANX/~/edit/~/changes/20/speed-optimizer/analytics) (which keeps a continuous tab on your real visitor data), Speed audit is a deep **on-demand scan**. You click **Run audit**, and the app analyzes your store using Google's PageSpeed engine plus your Shopify Analytics data.

The result is a complete diagnostic: where the slowdowns are, how much faster you could be, and a direct link to the feature (or service) that fixes each issue.

It's the best way to find specific problems and know exactly what to do next.

### Why use Speed audit?

* **Pinpoints exact problems** — not just a score, but the specific issues dragging your store down.
* **Shows the cost of slowness** — each issue tells you what it's costing you and how much you'd save by fixing it.
* **Links fixes directly to the solution** — every issue points to the feature (or specialist) that resolves it.
* **Combines real and simulated data** — see both how customers actually experience your store and how a browser test rates it.
* **On-demand, whenever you need it** — run a fresh diagnostic right after making changes.

### ⚙️ How to run a Speed audit

#### Step 1: Run the audit

Go to **Speed audit** in the Avada Speed menu and click **Run audit**.

<figure><img src="/files/InYvpNCYQgOKDmM5OPev" alt=""><figcaption></figcaption></figure>

#### Step 2: Wait for the scan

Wait while the scan runs (about 45 seconds). You'll see each step happening in real time. <br>

<figure><img src="/files/mf6ZZdbGegWYOfJGYR2f" alt=""><figcaption></figcaption></figure>

#### Step 3: Review your Audit summary

Once it's done, you'll see your **Audit summary** at the top:

* **Overall score** (0–100) — your speed grade.
* **Estimated savings** — how much faster your store could be.
* **Issues found** — total problems detected.

<figure><img src="/files/mVxQPxUTYwcM1CIz0v7v" alt=""><figcaption></figcaption></figure>

#### Step 4: See how visitors experience your store

**How visitors experience your store** shows two views:

* **Real visitor data** — how your actual customers experience your store (page load speed, click responsiveness, layout stability).
* **Simulated test** — how a browser test sees your store right now.

#### Step 5: Check Performance by page

**Performance by page** breaks down the speed by page type (Product, Collection, Home, etc.) so you can spot where the problem really lives.

#### Step 6: Review what's slowing your store down

**What's slowing your store down** lists every issue, grouped by what's causing it:

* Pages start slowly
* Images weigh too much
* Code is doing too much work
* Fonts and externals

Each issue tells you the problem in plain language, why it matters, what it's costing your store, and how much you could save by fixing it.

#### Step 7: Choose how to fix it

**How to fix this** gives you two ways forward:

* **Done-for-you** — let our Expert specialist handle the trickier fixes.
* **Do it yourself** — turn on the right Self-optimize features. Each issue links straight to the feature that fixes it (or to an upgrade if the fix needs a higher plan).

#### &#x20;Step 8: Take action

Use the **Next steps** buttons at the bottom to take action — apply DIY fixes right away or upgrade to Expert to get hands-on help.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.appplaza.app/speed-optimizer/speed-audit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.