Skip to content

Store speed tune up with before and after numbers

Speeds up a live store page with a method: measure a baseline several times, find the real causes, make small reversible changes on a copy, and compare before and after. A second skill checks the buy button and tracking still work before anything goes live.

Ecommerce and resaleWorks with Claude Code · Claude Desktop with MCPCommunity example
Build your promptSee requirements

What it does

  • Takes a baseline from several page speed runs, not one
  • Separates what is the theme, what can be switched off and what is outside your control
  • Makes small reversible changes on a theme copy, one file at a time
  • Compares before and after numbers and writes a report including what got worse
  • Checks the buy button, pixels and forms by render before publishing

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Publishing any change to the live theme
  • Creating a test order

You decide what happens next.

More about this workflow

This setup is for online sellers and resale shops juggling listings, orders and buyers. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it takes a baseline from several page speed runs, not one. Next, it separates what is the theme, what can be switched off and what is outside your control. Then it makes small reversible changes on a theme copy, one file at a time. After that, it compares before and after numbers and writes a report including what got worse. Finally, it checks the buy button, pixels and forms by render before publishing. It works with your store admin and web fetch, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before publishing any change to the live theme and creating a test order, and says plainly if a step cannot be undone.

juancaaa11 juancaaa11 on GitHub · Oct 9, 2026
Before you startStore admin · Web fetch accessScoped permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • Shopify

    Handles the store admin part of this job. Grant read orders and products.

    API required: Yes. Needs a Shopify app with an access token and the admin scopes you approve.

    Sign up: Shopify

  • Web fetch

    Handles the web fetch part of this job. Grant public pages, no logged-in sessions.

    API required: No. Built into most agent harnesses. It reads public pages with no login.

    No sign-up needed

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Gemini 3.8 Flash

Built for agent workflows, with a free tier to test on.

$0.75 per million input tokens and $3.75 per million output tokens through December 31, 2026. $1.50 and $7.50 from January 1, 2027.

Google docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for many listings at once.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

paste them

sections to leave alone

2Your prompt

4 of 4 still empty
Fill these in before you run it: [STORE URL AND SLOW PAGE] [PAGE SPEED ERRORS: paste them] [WHAT THE OWNER EDITS: sections to leave alone] [TRACKING PIXELS THAT MUST KEEP COUNTING] You are the Store speed tune up with before and after numbers agent. Speeds up a live store page with a method: measure a baseline several times, find the real causes, make small reversible changes on a copy, and compare before and after. A second skill checks the buy button and tracking still work before anything goes live. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Takes a baseline from several page speed runs, not one - Separates what is the theme, what can be switched off and what is outside your control - Makes small reversible changes on a theme copy, one file at a time - Compares before and after numbers and writes a report including what got worse - Checks the buy button, pixels and forms by render before publishing What you must never do without a yes from a person: - Publishing any change to the live theme - Creating a test order Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Shopify with its own login, not yours. Grant read orders and products.
  2. 2Set up Web fetch. Keep it to public pages, no logged-in sessions.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: publishing any change to the live theme, creating a test order.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Run it on one tool only, with its own login that can see just what this job needs +2

Do all of these to reach 91, up from 80.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Store speed tune up with before and after numbers](https://trustcase.dev/badge/store-speed-tune-up-with-before-and-after-numbers.svg)](https://trustcase.dev/use-cases/store-speed-tune-up-with-before-and-after-numbers)
HTML
<a href="https://trustcase.dev/use-cases/store-speed-tune-up-with-before-and-after-numbers"><img src="https://trustcase.dev/badge/store-speed-tune-up-with-before-and-after-numbers.svg" alt="Trustcase trust score for Store speed tune up with before and after numbers" height="20"></a>

More ecommerce and resale workflows

Other workflows that use the same tools

  • Refund checker

    Support. Checks refund requests against your policy and lays out the facts.

  • Competitor watch

    Marketing. Keeps an eye on what competitors change on their sites.

  • Morning AI news brief

    Personal. Gathers the day's AI news with simple scripts, then has the agent pick the best items and write a short PDF brief. It lands in your chat app before 7 AM.