Speed up a slow site with Grok Bot on xCloud

Slow is a vague complaint, and the first thing a Bot does with it is turn it into numbers. Ask @xcloud why shop.example.com is slow and the Bot finds the site and the server it runs on, because a neighbour on the same server is often the cause. It reads sites_status, then sites_monitoring_history for the 24-hour or 7-day series to see whether the slowdown is new, looking at disk early because a nearly full disk slows the database first. It then reads sites_cacheSettings before it says anything about caching, so it can tell you whether page cache, object cache and Cloudflare edge cache are on. Monitoring history is a paid-plan feature, so on the free plan expect it to say plan limit and work from the samples that remain.

PageSpeed and traffic come next. sites_pagespeed_latest returns the latest mobile and desktop results for free, and the Bot should read it before it starts a new scan with sites_pagespeed_scan, telling you it is spending one. A 409 means a scan is already running, so the Bot polls it rather than starting another. The access log, read through sites_access-logs in a bounded window, shows spikes, crawls and one client hammering a path. What you want back is the most likely cause with its numbers. Whatever the Bot recommends, enabling Redis or another cache layer is a dashboard switch under Site, WordPress, Caching, so it gives you the path and the dashboard link instead of offering to flip it. It can purge caches, and on a live site it asks first, since a purge throws away a warm cache.

Routines make the second half possible, which is tracking. Ask for a weekly one: every Monday at 8:00 AM, read the latest PageSpeed results for the shop and blog sites and post the mobile and desktop scores. Each routine keeps up to 20 run records, so you can open Routines under View conversation details and read the last few weeks side by side. That turns a fix into something you can check: change the PHP version or switch on the cache in the dashboard, then watch the next two Mondays instead of trusting a single scan.

Grok Bot specific: Read before you scan. A PageSpeed scan runs without an xCloud prompt, which means a routine told to scan every morning starts a scan every morning, and each scan runs both mobile and desktop. Tell the Bot to read the latest result on the routine and to start a new scan only when there is none or the site has changed. Do not let it present a change of the server's default PHP version as a fix for one slow site either. That setting changes the command-line php and the version new sites get, and it moves no existing site. One site's PHP version is a dashboard setting under Site, Site Settings.