WorkDaddy for Cloudflare
Speed is a conversion input and a ranking input. Cloudflare is where the Ops agent does something about it — at the edge, continuously, per route.
Store performance decays quietly: an app is installed, a campaign script is added and never removed, an image ships unoptimised. The Ops agent connects to Cloudflare to monitor real-user performance per template, tune caching per route rather than with one blanket rule, and manage bot protection so your analytics reflect people rather than scrapers.
Performance measured on real users
Lab scores are easy to game and easy to misread. Ops works from real-user Core Web Vitals, segmented by device and template, so a regression that only affects mobile product pages is visible as exactly that.
Real-user LCP, INP, and CLS by device and template
Per-route cache rules instead of a single global policy
Third-party script inventory — what was added, what it costs
Image and asset delivery optimisation across the catalogue
Bot traffic, handled deliberately
Scrapers and abusive traffic inflate sessions and distort every downstream decision. Ops manages bot protection and rate limiting at the edge while deliberately keeping legitimate crawlers — including the AI crawlers you want indexing you — unblocked.
Fix at the edge, or escalate
When a regression can be solved with configuration, Ops solves it there. When it is a page problem — a bloated template, a render-blocking block of content — it hands a specific task to Builder rather than papering over it with caching.
How it works
Connect your zone
Ops takes over caching and protection configuration and records the current state as a baseline.
Baseline performance
Real-user metrics are captured per template so later changes are comparable rather than anecdotal.
Maintain continuously
Regressions are caught against the baseline and either fixed at the edge or escalated to Builder.
What you get
Core Web Vitals tracked on real users, segmented by template
Cache behaviour tuned per route rather than one global rule
Bot traffic separated out before it corrupts analytics
AI crawlers explicitly allowed, so you stay retrievable
Handled by these agents
Frequently asked questions
Do I have to move DNS to Cloudflare?
For edge caching and bot protection, yes — those operate at the network layer. Without it, Ops still monitors performance and maintains the audit layer, with fewer levers available.
Will it break my existing Cloudflare rules?
It records your current configuration as a baseline before changing anything, and every change is logged and reversible.
Does it block AI crawlers by default?
No. Being retrievable by AI engines is a growth channel, so those crawlers stay allowed while scrapers and abusive traffic are blocked. You control the list.
Does this work for non-Shopify stores?
Yes. Cloudflare sits in front of whatever you run — WooCommerce, a headless front end, a custom build — so Ops works the same way regardless of platform.
Keep reading
Site speed optimisation
Find what actually slows real users down, fix it, and stop the regressions that undo it.
Improve store page speed
A field-data-first speed programme: measure real users, fix by layer, prevent regression.
Ops
Keeps the store fast and secure, and keeps every agent working from the same record.
Supabase
The shared memory and audit log that lets five agents work without stepping on each other.
Put the team to work on your store
Connect your storefront, analytics, and email stack, set a goal, and let the agents run the work end to end. Start on the free plan with your own model key.