IMC 2026 Meet Provis at India Mobile Congress · 7-10 Oct · Yashobhoomi, New Delhi 7-10 Oct, Delhi Book 15 min

Free store speed audit

Find What's Slowing Your Store, And What To Fix First.

Send your store URL. We test your key pages on a phone, find the apps, scripts, images and code that slow them down, and send back a written fix list in order, with who can do each fix. You can read a full sample below first.

Prefer WhatsApp? Send us your store URL there.

  • Just your store URLno staff account or passwords
  • Tested on a phonewhere most of your visitors are
  • No call neededa call only if you want one

The sample audit

Read A Speed Audit Before You Ask For Yours

This is the format you will receive, filled in for Example Living Co., a fictional Shopify store selling homeware and wellness products. It shows what real visitors get and what our tests show, each page type on a phone, every app and script, images and theme, a light look at mobile buying, and the fixes in order.

One difference: your report names your own apps, pages and numbers. Every figure in this sample is invented to show the format.

Store speed audit

What is slowing Example Living Co., and what to fix first

Five page types tested on a mid-range phone, with Google's data from real visitors, every app and script, and a fix list in order.

Prepared for
Example Living Co. (fictional)
Store
shop.example.com · Shopify
Tested
14 to 15 Sept 2026, phone first

Illustrative sample. Example Living Co. is a fictional store and every figure here is invented to show the format. Your report names your own apps, pages and numbers.

Sample audit of a fictional store. Every figure is invented to show the format.Page 1 of 10
Store speed audit · Example Living Co. Illustrative sampleSummary: fix this first

Summary

Fix this first

Real visitors, phone

Failing
Google's Core Web Vitals, from real visitors over 28 days

Slowest page

Product
Main image appears after 6.4 s on a mid-range phone

Apps and scripts

1.6 MB
of the 6.1 MB a product page downloads

The three biggest problems, in plain English

  1. 1Your pictures and video are far too big for a phone. The home page video and product photos are what visitors wait for.
  2. 2Seven apps and scripts load on every page, including three you no longer need and pixels that load twice.
  3. 3Product pages jump while they load. Price and buttons move when a size is chosen, so taps land in the wrong place.

Your first five fixes

FixWho can do itEffort
Replace the home page video with an image; play video on tapYour developerS
Resize and convert product images; serve them at the size shownYour developerM
Remove the upsell popup app and the currency converter appYou, in the adminS
Delete code left by the 2 removed appsYour developerS
Load the pixels once, from the tag manager onlyYour developer, with marketingS
The full plan, with the risk of each fix and how to check it worked, is on page 8.
Sample audit of a fictional store. Every figure is invented to show the format.Page 2 of 10
Store speed audit · Example Living Co. Illustrative sampleReal users and lab tests

Real users and lab tests

What real visitors get, and what our tests show

Real-user data is Google's record of what visitors to your store actually experienced over the last 28 days (the Chrome UX Report, 75th percentile). It is what Google uses in search. Lab tests are our own runs on a simulated phone: useful to find causes, not a measure of what visitors get.

Real-user data, 28 daysPhoneDesktopGoogle's "good"
Largest Contentful Paint (LCP)
How long the main image or text takes to appear
4.1 s Poor2.3 s Good2.5 s or less
Interaction to Next Paint (INP)
How quickly a tap gets a response
310 ms Needs work140 ms Good200 ms or less
Cumulative Layout Shift (CLS)
How much the page jumps while loading
0.18 Needs work0.12 Needs work0.1 or less

If a store has too few visitors for Google to report, we say so and rely on lab tests.

Lab tests: mobile performance score out of 100

Home38
Collection34
Product29
Search results41
Cart52
Don't chase a score of 100. The scores point to causes; what matters is the real-user data above passing on phones.
Sample audit of a fictional store. Every figure is invented to show the format.Page 3 of 10
Store speed audit · Example Living Co. Illustrative samplePage by page, on a phone

Page by page

Each page type, tested on a phone

Tested on a simulated mid-range Android phone over a 4G connection, from London, Virginia and Dubai, where this store sells. Your audit tests near your own customers: for example Virginia, London, Sydney, Dubai or Mumbai. The product page was also opened inside Instagram's in-app browser, where much of the store's traffic arrives.

PageMain content showsWhat visitors wait forMain cause
Home5.8 sHero video (autoplay)A 6.2 MB video plays before anything else
Collection4.9 sFirst product imageFilters load 4 scripts before the grid
Product6.4 sMain product imageA 3.8 MB image and an upsell popup script
Search results4.2 sResults gridSearch waits for the currency app
Cart3.1 sCart summaryFine, apart from the chat widget

Inside Instagram

The product page took 1.2 s longer in Instagram's browser than in Chrome, mostly from the chat widget and pixels.

Google's target

Main content within 2.5 s. Every page type here misses it on a phone.
Sample audit of a fictional store. Every figure is invented to show the format.Page 4 of 10
Store speed audit · Example Living Co. Illustrative sampleApps and scripts

Apps and scripts

Everything that loads besides your store

Weight is what a phone downloads; main-thread time is how long the phone is busy and can't respond to a tap. Your report names each app; this sample names them by type.

App or scriptWeightBusyBlocks the pageVerdictWhy
Reviews widget
Every page
412 KB690 msNoDelayLoad on product pages only, when the reviews scroll into view. It sells, so keep it.
Upsell popup app
Every page
286 KB540 msYesRemoveDuplicates the theme's own "You may also like".
Chat widget (live chat and WhatsApp)
Every page
520 KB410 msNoDelayLoad after the first tap or scroll.
Ad pixels, twice
Every page
180 KB260 msNoRemove duplicatePixels load from the theme and from the tag manager. Remove the theme copy; keep the tag manager one.
Currency converter app
Every page
96 KB120 msYesRemoveYour platform's built-in markets already convert prices.
Code from 2 removed apps
Every page
64 KB90 msYesRemoveThe apps are gone; their code is still in the theme.
Cookie consent banner
Every page
58 KB70 msNoKeepNeeded for UK and EU visitors. Already light.
Together these are 1.6 MB of the 6.1 MB a product page downloads, and 2.2 seconds of a phone's time. Removing four and delaying two keeps every feature you use. Not counted here: a stock check on every product page (0.4 s), which comes from your stock system, not an app (page 9).
Sample audit of a fictional store. Every figure is invented to show the format.Page 5 of 10
Store speed audit · Example Living Co. Illustrative sampleImages, fonts and theme

Images, fonts and theme

Real examples from your store

Product photo

Now

A 4,000-pixel JPEG of 3.8 MB, shown 400 pixels wide on a phone.

Should be

Served in the size each screen needs, as WebP: well under 200 KB.

Home page video

Now

A 6.2 MB video that plays on phones before anything else shows.

Should be

A still image first; the video plays only when tapped.

Fonts

Now

Four font files, two of them weights the store never uses.

Should be

Two files, loaded so text shows at once.

The theme: fix it, don't rebuild

Built on a standard Shopify theme, two major versions behind, with nine sections the store no longer shows. Everything on this page can be fixed in the theme you have. We would only suggest a rebuild if the theme blocked a fix, and it doesn't.
Sample audit of a fictional store. Every figure is invented to show the format.Page 6 of 10
Store speed audit · Example Living Co. Illustrative sampleMobile UX and checkout

Mobile UX and checkout

What gets in the way of buying on a phone

A light pass, written as observations. It is not a conversion audit: we haven't seen your analytics or your sales funnel.

What we sawWhereWhat to change
Email popup covers the product photoFirst visit, after 2 secondsShow it after a scroll, or as the visitor leaves.
Price and buttons jump when a size is chosenProduct pagesReserve the space; this is most of your layout shift.
No add-to-cart button once you scrollLong product pagesAdd a sticky add-to-cart bar on phones.
Filters take about 2 seconds to updateCollection pagesLoad filter results without reloading the page.
Payment options appear only at checkoutProduct and cart pagesShow Klarna and Apple Pay near the price; in the UAE, Tabby and cash on delivery too.
A country and currency popup on arrivalEvery first visitSet the currency from the visitor's location; ask only when unsure.
The consent banner covers add-to-cartSmall phonesMake the banner shorter on phones.
The layout shift on product pages is both a speed problem and a buying problem: taps land on the wrong button when the price block moves.
Sample audit of a fictional store. Every figure is invented to show the format.Page 7 of 10
Store speed audit · Example Living Co. Illustrative sampleThe fix-first plan

The fix-first plan

In order, with who can do each one

#FixWho can do itEffortRiskWhat it should move, and how to check
1Replace the home page video with an image; play video on tapYour developerSLowHome LCP in a lab test
2Resize and convert product images; serve them at the size shownYour developerMLowProduct LCP in a lab test
3Remove the upsell popup app and the currency converter appYou, in the adminSLowScript weight on every page
4Delete code left by the 2 removed appsYour developerSLowNo requests to the old apps
5Load the pixels once, from the tag manager onlyYour developer, with marketingSMediumAd platforms still record purchases
6Delay the reviews widget and the chat widgetYour developer, with the app vendorsMMediumReviews and chat still work
7Reserve space for price and buttons on product pagesYour developerMLowCLS in field data after 28 days
8Sticky add-to-cart on phones; email popup after a scrollYour developerMLowAdd-to-cart rate on phones

Effort

S a setting or one change; M a developer task; L a project that needs testing.

Risk

What could break. Medium means test it on a copy of the theme first.
Every fix can be done by your own team or freelancer. None needs us.
Sample audit of a fictional store. Every figure is invented to show the format.Page 8 of 10
Store speed audit · Example Living Co. Illustrative sampleWhat not to touch, what we couldn't check

Limits

What not to touch, and what we couldn't check

Leave alone

  • The reviews widget. It sells. Delay it; don't remove it for a few points.
  • The consent banner. UK and EU visitors need it.
  • Checkout. Your plan allows few changes there, and it is already fast.
  • A score of 100. It isn't the goal; passing on real phones is.

Couldn't check from outside

  • Checkout internals and pages behind a login.
  • Your ERP or POS stock and order sync. We saw one stock check on every product page (0.4 s) but not the system behind it.
  • App settings in your admin.
  • Your sales and conversion data.

Confidence

High for images, apps and layout shift: we measured them directly. Medium for the stock check: we saw the call, not the system behind it.
Sample audit of a fictional store. Every figure is invented to show the format.Page 9 of 10
Store speed audit · Example Living Co. Illustrative sampleAfter the fixes, and the next step

After the fixes

How to tell it worked, and what next

Watch these

  • Real-user LCP and CLS on phones
  • Lab scores per page type, the same day
  • Shopify's web performance dashboard, after 28 days
  • In GA4, conversion rate by device: phone conversion on product pages, and bounce rate from Instagram

Why there is no money figure

We haven't seen your traffic or conversion rate, so any figure for what slowness costs you would be a guess. The numbers under "Watch these" will show the real effect.

How we tested

Lab tests on a simulated mid-range Android over 4G, three runs per page, the median shown; tests from London, Virginia and Dubai; Google's real-user data for the 28 days to 15 September 2026; public pages only, with no access to the store's admin.

Your next step, your choice

  1. Fix it yourselves. The plan on page 8 is written for your team or freelancer.
  2. Ask us to help with some of it. A separate conversation, only if you want one.
  3. Do nothing yet. The report still tells you where the time goes.
Questions about this report: reply to the email it came with.
Sample audit of a fictional store. Every figure is invented to show the format.Page 10 of 10
Download sample PDF

10 pages. No email needed.

Request Your Audit

What's inside this audit?

  • A summary: what to fix first
  • Real-user and lab speed results
  • Each page type, tested on a phone
  • Every app and script, and its cost
  • Images, fonts and theme findings
  • The fix-first plan and next step

Document details

Pages
10
Format
PDF
Last updated
October 2026

What it is, and what it isn't

A Fix List To Work From,
Not A Sales Call

The audit gives you the fixes in order, with what real visitors get and what our tests show. It needs no call and no access to your store.

A clear fix list
for your store

You get

  • What real visitors get and what our tests show, labelled apart
  • Every app and script on your key pages, with keep, delay or remove
  • Image, font and theme findings, with examples from your store
  • A light look at buying on a phone
  • The fixes in order: effort, who can do each one, how to check it worked
  • What we couldn't check from outside

You are not committing to

  • A call
  • Giving us access to your store
  • Any next step: fixing it with us is a separate decision
  1. No money figure.

    We haven't seen your analytics, so we don't guess what slowness costs you. The report names the numbers to watch in your own analytics instead.

  2. Speed first, with a light look at buying on a phone.

    It is not a full conversion audit.

  3. Worth doing before a big sale.

    A month before Black Friday, Boxing Day, White Friday, Ramadan or Diwali leaves time to fix what it finds.

Who reads it

Read By The Team That
Builds And Fixes Stores

Our team in India (IST) reads every request. We build and fix stores on Shopify, Shopify Plus and WooCommerce.

  • Store rebuild MotionLasers

    Product pages went from 30 to 90+ on Google PageSpeed, other pages to 70+. That came from a full mobile-first rebuild, not from an audit alone.

  • Shopify LGXNDS

    Came to us for Shopify fixes, then kept us on for mobile, custom tools and the launch of its second brand.

  • B2B store TrueWholesale

    A B2B sourcing platform with 200% sales growth and 4 new regions, as reported by TrueWholesale.

Provis Technologies has been an excellent partner for our Shopify work. Their team moved quickly on fixes, improved the experience of the store, and helped us turn ideas into working features without unnecessary delay.
Fernando AriasFounder, LGXNDS

Frequently Asked Questions

Questions Before You Request An Audit

What it costs you, what we need, and what happens next.

Still unsure? Ask us on WhatsApp or send us your question.

It is free. You get a written report by email, and a call only if you want one. If you want help with the fixes, that is a separate conversation.

Your store URL. Everything in the report comes from your public pages and from Google's data on what real visitors to your store experienced.

No staff or collaborator account and no passwords. The audit works from your public pages.

Yes. Each fix says who can do it (you in the admin, your developer or the app vendor) and how to check it worked.

No. We haven't seen your traffic or conversion rate, so a money figure would be a guess. The report names the numbers to watch in your own analytics instead.

Shopify, Shopify Plus and WooCommerce.

What happens next

  1. 1
    We test your storeOur team in India (IST) tests your key pages on a phone, and emails you if anything needs clarifying.
  2. 2
    Your report, by emailWhat real visitors get, every app and script, images and theme, and the fixes in order.
  3. 3
    A call, if you want oneTo talk it through. Nothing to commit to.

Rather pick a time yourself?

Book a 30-min call with Vivek Sharma

CEO & Founder, Provis Technologies

Contact Us

Request Your Free Store Speed Audit.

Or message us on WhatsApp