> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/run-and-update-your-store/store-speed.md).

# Keep your store fast

A slow store loses sales before a shopper ever sees a product. Most of what makes a Shopify store slow is not the theme itself: it is oversized images, apps that keep loading scripts long after you stopped using them, and heavy content stacked at the top of the home page. This page shows you how to measure your speed, what to fix first, and how to keep it from creeping back.

### Before you start <a href="#before-you-start" id="before-you-start"></a>

* Your store is live, or at least has a preview link, because speed tests need a real page to load.
* You have a few real products with real images published.
* You can access **Analytics** and **Apps** in your Shopify admin.
* Measure before you change anything, so you can tell whether your changes actually helped.

### Step 1: Measure your current speed <a href="#step-1-measure" id="step-1-measure"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Shopify admin > Analytics > Reports**.
2. Open the **Online store speed** report.
3. Note your score and the date, and note how it compares with other stores on the same plan.
4. Come back to this report a few days after making changes, since it updates on a delay.
   {% endhint %}

*Result:* you have a starting number for your store, measured on your own pages with your own content.

{% hint style="info" %}
The Shopify report scores your home page, one collection page, and one product page. It is a trend indicator, not a per page audit. For a page by page breakdown, use Google PageSpeed Insights on the exact URL you care about.
{% endhint %}

### Step 2: Test a single page in detail <a href="#step-2-pagespeed" id="step-2-pagespeed"></a>

{% hint style="success" %}
**Steps:**

1. Copy the URL of the page you want to test, usually your home page or your best selling product.
2. Open Google PageSpeed Insights and paste the URL.
3. Run the test and read the **Mobile** results first, because most shoppers arrive on a phone.
4. Look at the **Opportunities** and **Diagnostics** lists, not only at the score.
5. Run the same test twice, since a single run can be affected by network conditions.
   {% endhint %}

*Result:* you get a concrete list of what is slowing that page down, usually images, third party scripts, and unused code.

### Step 3: Fix your images <a href="#step-3-images" id="step-3-images"></a>

Images are the single biggest cause of slow storefronts, and the easiest thing to fix without touching code.

{% hint style="success" %}
**Steps:**

1. Export or review the images you use in banners and on product pages.
2. Resize anything wider than about 2000 pixels before uploading. A 5000 pixel photo does not look better on a phone, it only weighs more.
3. Re-upload the resized versions in **Content > Files** or in the product editor.
4. Replace autoplaying background videos on the home page with a still image where you can.
5. Fill in the alt text while you are there, which helps both accessibility and search.
   {% endhint %}

*Result:* pages transfer far less data, which improves loading on mobile connections most of all.

### Step 4: Remove the apps you no longer use <a href="#step-4-apps" id="step-4-apps"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Shopify admin > Apps**.
2. List every app and write down what it does for you today.
3. Uninstall any app you no longer use.
4. After uninstalling, check your theme for leftover code the app left behind, and ask the app support to remove it if you are not sure.
5. Keep a note of the ones you keep, so the next review is faster.
   {% endhint %}

*Result:* fewer external scripts run on every page load, which is often a bigger win than any theme setting.

{% hint style="info" %}
Uninstalling an app does not always remove the code it injected into your theme. If a feature disappears but the page still loads its script, that leftover code is now pure weight.
{% endhint %}

### Step 5: Keep the top of the page light <a href="#step-5-above-the-fold" id="step-5-above-the-fold"></a>

{% hint style="success" %}
**Steps:**

1. Open **Online Store > Themes > Customize**.
2. Look at what loads first on your home page: a slideshow with many slides, a video, and an animated banner all compete for the same seconds.
3. Reduce the number of slides, or replace the slideshow with a single image.
4. Move heavy sections such as long product grids or embedded feeds further down the page.
5. Click **Save**, then measure again with Step 2.
   {% endhint %}

*Result:* the first screen appears sooner, which is what shoppers and speed tools both react to.

### Step 6: Review your fonts and tracking scripts <a href="#step-6-fonts-scripts" id="step-6-fonts-scripts"></a>

{% hint style="success" %}
**Steps:**

1. In the theme settings, count how many font families you use. Two is usually enough.
2. Prefer the system and Shopify hosted fonts over externally loaded ones.
3. Review the tracking and marketing scripts pasted into your theme or into **Settings > Customer events**.
4. Remove any script belonging to a tool you stopped using.
   {% endhint %}

*Result:* the browser downloads fewer external files before it can render your text.

### What you should see <a href="#what-you-should-see" id="what-you-should-see"></a>

* The **Online store speed** report moves in the right direction over the following days.
* Your PageSpeed Insights mobile score improves, especially the image related opportunities.
* The home page shows its first screen quickly on a phone, on a normal mobile connection.
* You still recognise your store. Speed work that strips out your brand is not a win.

### If something goes wrong <a href="#if-something-goes-wrong" id="if-something-goes-wrong"></a>

* **The score did not change after your fixes.** The Shopify report is calculated over time. Wait several days, and use PageSpeed Insights in the meantime for immediate feedback.
* **Your score is much lower than the theme demo.** Demo stores run without extra apps, with optimized images, and with light content. The gap is usually your apps and your images, not the theme.
* **Scores differ every time you test.** That is normal. Compare trends across several runs rather than single numbers.
* **A page got faster but a feature stopped working.** You removed a script that was still in use. Put it back and look for a lighter alternative.
* **Speed dropped suddenly with no changes on your side.** A recently installed app is the usual cause. Check what was added in the last few days.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Recommended apps](/velare/buy-and-install/apps/recommended-apps.md): choosing apps deliberately rather than accumulating them
* [Apps](/velare/buy-and-install/apps.md): the apps the theme works with
* [Update Vélare](/velare/run-and-update-your-store/update-velare.md): performance fixes often arrive with a new version
* [Release notes](/velare/run-and-update-your-store/release-notes.md): what changed in each version
* [Layout](/velare/set-up-your-store/layout.md): page width and spacing
* [Header](/velare/set-up-your-store/header-group/header.md): the first section every page loads
* [Footer](/velare/set-up-your-store/footer-group/footer.md): a common place for unused scripts and links


---

# 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://uxsmart.gitbook.io/velare/run-and-update-your-store/store-speed.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.