ChatGPT dots + xCloud

Speed up a slow site with ChatGPT dots on xCloud

Speeding up a slow site with a ChatGPT dot means asking your always-on OpenAI agent to measure your xCloud site, find the most likely cause from real numbers and keep checking it over days instead of guessing once.

Skill: xcloud:performance
Toolsets: pagespeed, sites, servers, broken-links
Free with every xCloud account

Set up ChatGPT dots All ChatGPT dots guides

YouWhy is shop.example.com slow on mobile?

servers_monitoringread-only

sites_pagespeed_latestread-only

sites_cacheSettingsread-only

AgentDisk and load on the server are fine, so this is the site. The latest mobile run is weak on server response, and page cache, object cache and the Cloudflare edge cache are all off, so every visit runs PHP and the database. Turning caching on is a dashboard step: Site, WordPress, Caching. Do you want me to compare the score every Monday?

YouYes, tell me only if it drops.

AgentScheduled for Mondays at 9. I will read the newest result, compare it with the earlier ones and message you only when the mobile score falls.

Last updated: October 2026. Keep a human in the loop: xCloud stops and asks before anything that creates, deploys, updates, reboots, deletes or buys.

Setup

How Do You Set Up ChatGPT dots to Speed up a slow site on xCloud?

Connect ChatGPT dots once; every job on this account uses the same connection. Then ask in plain words.

1
Create the xCloud MCP plugin in ChatGPT
Plugins are shared across your dot, ChatGPT, ChatGPT Work and Codex, so you set xCloud up once. In ChatGPT on the web, turn on Developer mode under Settings, Security and login, open the Plugins page, select the plus button and create an app named xcloud with this MCP server URL and OAuth as the authentication. Sign in with xCloud, tick the teams and choose Read-only or Full access. Then open your personal Plugins page, open xcloud and select the plus button to install it; until it is installed, your dot cannot see it. If ChatGPT already has the xcloud plugin installed, skip this step. That path is for a personal account. In a Business, Enterprise or Edu workspace the controls sit under Apps instead. On Business only an admin or owner can use Developer mode: they turn it on while creating the app from Workspace settings, Apps, Create, and publish it from Workspace settings, Apps. On Enterprise and Edu an admin or owner can also toggle Developer mode under Settings, Apps, Advanced settings, and a member granted developer access under Permissions and Roles turns it on there too and can create and test the app from their own Settings, Apps, Create, but only an admin or owner can publish it. An ordinary member cannot do this, so ask an admin to publish the xcloud app; then open Settings, Plugins, select xcloud, install it if offered and choose Connect, sign in to xCloud and pick the teams and access level, and only then start at the next step.
URL
```
https://app.xcloud.host/mcp
```
2
Check the plugin is connected for your dot
Open your dot's profile, then Customize and Plugins, and make sure xcloud is connected. The screen uses the shared ChatGPT plugin settings, so a plugin connected in ChatGPT appears here too. Then give your dot a first task that names xCloud.
Prompt
```
Using xcloud, who am I on xCloud, and which servers and sites do I have?
```
3
Add a custom rule for hosting changes
Under Customize, Custom rules, describe the action and choose Ask before taking action. Pre-approved means you asked for the action in your prompt. xCloud stops for confirmation on its own before it creates, deploys, updates, reboots or deletes anything, but a rule keeps the approval visible in your conversation and stops a scheduled task from proposing changes you did not ask for.
Prompt
```
Ask before taking action: anything that creates, deploys, updates, reboots or deletes a server or site on xCloud.
```

Check it worked

Then ask ChatGPT dots for the job itself, for example:

Prompt

Why is shop.example.com slow on mobile? Check disk, the site and server load over the last 7 days, the cache layers and the latest PageSpeed result, and give me the most likely cause with its numbers.

In practice

How Does Performance Work from ChatGPT dots?

Slowness is rarely a single reading, which is why a dot fits it. Start with the question, why is shop.example.com slow on mobile, and your dot resolves the site and its server, then reads sites_status, the 24-hour or 7-day series from sites_monitoring_history and servers_monitoringHistory, sites_cacheSettings and the latest mobile and desktop result from sites_pagespeed_latest. It reads disk early, since a nearly full disk slows the database first, and it reads the cache layers before it says anything about caching. Monitoring history is not available on the free xCloud plan, so a dot that tells you there is no data should say that it is a plan limit.

The standing version is where a dot beats a one-off chat. Ask it to check the shop every Monday, read the newest PageSpeed result, compare it with the earlier ones and tell you only when the score drops. Reading results is free. A new scan with sites_pagespeed_scan is worth starting only when there is no result or the site changed, and your dot says it is spending a scan. A 409 means a scan is still running, so it polls instead of starting another. The same report can include the access log, read over SSH for a bounded window, to catch a bot hammering one path, and whether Redis is running next to an object cache that reads as on.

Then it names the cause with its numbers and hands off. Enabling page cache, Redis or the Cloudflare edge cache on an existing site is a dashboard switch under Site, WordPress, Caching, and your dot gives you that path instead of offering to flip it. It can purge caches, but a purge throws away a warm cache, so it asks first on a live site. Changing one site's PHP version is also a dashboard step, and the server default PHP does not move existing sites.

ChatGPT dots specific: A dot reports what it measured, so give it a baseline. Ask for the first PageSpeed result and the monitoring series on the day you start, otherwise a Monday drop has nothing to compare with. OpenAI's help center says Pro accounts connect MCP apps with read and fetch permissions only, so on Pro a dot reads the latest results and history but may not be able to start a new scan or purge a cache, which are actions and not reads. Full MCP support with write actions is in beta on Business, Enterprise and Edu workspaces.

What xCloud does for performance

xCloud reads the site's and the server's CPU, RAM and disk samples, which cache layers are on, the latest PageSpeed result, traffic in the access log, service health and the site's PHP version. The agent names the cause from that data, then hands you the switches that only the dashboard can flip.

Resolve the site and its server. The agent looks up the site and the server it runs on, because the answer often comes from both. A slow site is frequently slow because a neighbour on the same server is.
Check status and monitoring history. A site that is mid-deploy or failed explains slowness without any measurement. Otherwise the agent reads the site's and the server's samples, and a 24-hour or 7-day series to tell whether the slowdown is new. Disk comes early: a nearly full disk slows everything, the database first.
Read the cache layers. The agent reads the cache settings before saying anything about caching: whether page cache, Redis or Object Cache Pro object cache and Cloudflare edge cache are on, and which server stack the site runs. It never reports that no cache configuration is readable without calling it.
Read PageSpeed and traffic. The latest completed PageSpeed run is free to read. A new scan is worth starting only when there is no result or the site changed since, and the agent tells you it is spending a scan. The access log shows spikes, a crawl or one client hammering a path.
Check services and PHP. The agent checks that PHP, the web server, Redis and the database are running, and reads the site's PHP version and pending updates. A stopped Redis next to an object cache that reads as on is a found answer.
Name the cause and hand off. You get the most likely cause with its numbers. The fix is either something the agent can do, such as a purge after you agree, or a dashboard switch it names with the path and the site's dashboard link. If every number looks normal, it says so instead of inventing a cause.

Reference

Performance Settings and Limits on xCloud

The facts ChatGPT dots works within when it speeds up a slow site. Where a row names the dashboard, that step stays yours to take there.

Setting or limit	What applies
Monitoring history	Site and server CPU, RAM and disk samples as a 24-hour or 7-day series. History is not available on the free plan, and the agent says that is a plan limit rather than reporting no data
Cache state	Read through sites.cacheSettings: page cache, object cache (Redis, Object Cache Pro) and Cloudflare edge cache. It returns settings only, never cache contents
Enabling a cache layer	Dashboard-only: Site, WordPress, Caching. The API reads the layers and purges them, and cannot switch one on for an existing site
Page cache details	Cache duration, URL and cookie exclusions and ignored query parameters are dashboard-only and are not returned by the cache settings read
PageSpeed	The latest mobile and desktop results and the history are read for free. One scan runs both strategies
Scan conflicts	A 409 while a scan is running means it is still pending or scanning. The agent polls it instead of starting another, and it is not a cooldown
Cache purge	Purging runs without a confirmation stop but throws away a warm cache, so the agent asks first on a live site and reports each layer as queued or skipped
Traffic	The access log shows spikes and bots. It is read over SSH, so the agent asks for a bounded window
PHP version	Read from the site's status. Changing one site's PHP version is a dashboard step: Site, Site Settings
Server PHP default	Changing the server default PHP changes only the command-line php and the version new sites get. It does not move any existing site
Broken links	A broken-link scan on a WordPress site returns findings grouped by source page, and a truncated scan is reported as partial

Rules ChatGPT dots has to follow

The agent diagnoses from measurements, not guesses, and it calls the cache settings read before it says anything about caching.
It never offers to turn on Redis or any other cache layer itself. Enabling a layer is a dashboard step, and the agent gives you the path and the dashboard link.
It never presents a change of server PHP default as a substitute for changing one site's PHP version.
A cache purge on a live site, a new PageSpeed scan and any server-level PHP change are announced first. Server-level changes also need your explicit yes.
A site that errors rather than loads slowly goes to troubleshooting, and a failed deploy goes to deploy.

Example prompts

What Can You Ask ChatGPT dots to Do for Performance?

Type these as written and swap in your own repository, site and server names. Reads and routine actions such as backups, cache purges, PageSpeed scans and vulnerability scans run straight away; creating, deploying, updating, rebooting, deleting, buying or starting a broken-link scan stops and asks first.

Prompt

Why is shop.example.com slow on mobile? Check disk, the site and server load over the last 7 days, the cache layers and the latest PageSpeed result, and give me the most likely cause with its numbers.

Prompt

Every Monday at 9, read the newest PageSpeed result for shop.example.com, compare it with the earlier ones and message me only if the mobile score dropped. Do not start a new scan unless I ask.

Prompt

Is Redis object cache on for the shop site, and is the Redis service running on its server? If a cache layer is off, tell me the dashboard path and do not try to switch it on.

Prompt

Why is shop.example.com slow? Check the cache, the server load and the latest PageSpeed result.

Prompt

Is Redis object cache on for the shop site? If it is off, tell me where to switch it on.

Prompt

Show CPU, RAM and disk for the shop site over the last 24 hours and tell me whether the slowdown is new.

Prompt

Run a PageSpeed scan on the shop site and compare the score with the previous scans.

Prompt

Look at the access log of the shop site for a traffic spike or a bot hammering one path.

Prompt

Which PHP version is the blog site running, and are there pending updates I should apply?

Prompt

Purge all caches on the shop site.

Prompt

Scan the shop site for broken links and list the pages with the most.

ChatGPT dots and Performance: Frequently Asked Questions

What people ask before they let ChatGPT dots speed up a slow site through xCloud.

Can my ChatGPT dot turn on caching to speed up my site?

No. Enabling page cache, Redis or the Cloudflare edge cache on an existing site is a dashboard switch under Site, WordPress, Caching. Your dot can read which layers are on, purge them and tell you the path, and you flip the switch.

Can my dot alert me when my PageSpeed score drops?

Yes. Ask it to read the newest PageSpeed result on a schedule, compare it with earlier runs and message you only when the score falls. Reading results is free, and it should only start a new scan when there is no result or the site has changed.

Can the agent turn on caching for my slow site?

No. It can read which cache layers are on and purge them, but switching page cache, Redis object cache or Cloudflare edge cache on for an existing site is a dashboard step under Site, WordPress, Caching. The agent tells you the path and gives you the site's dashboard link.

What does a 409 mean when the agent starts a PageSpeed scan?

It means a scan for that site is still pending or running. The agent polls the existing scan instead of starting another, and it is not a cooldown period. A new scan is only worth starting when there is no recent result or the site has changed.

Will changing the server's PHP default speed up my site?

No. The server default changes only the command-line php and the version new sites get, and it does not move any existing site. The PHP version of one site is changed in the dashboard under Site, Site Settings.

Why does the agent say monitoring history is unavailable?

Monitoring history is a paid-plan feature, so on the free plan the request is refused as a plan limit. The agent reports it that way rather than saying there is no data, and it falls back to the samples and measurements the plan does include.

Does purging the cache ask for my confirmation?

xCloud itself runs a purge without a confirmation stop, because it is a routine action. The agent still asks you first on a live site, since a purge throws away a warm cache and the next visitors wait while it rebuilds.

Other agents