ChatGPT + xCloud

Speed up a slow site with ChatGPT on xCloud

Speeding up a slow site with ChatGPT means describing the slowness in a conversation and letting the xcloud developer-mode app read your site and server numbers, then explain the likeliest cause in plain language.

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

Set up ChatGPT All ChatGPT guides

YouUsing the xcloud app, why is shop.example.com slow on mobile?

sites_pagespeed_latestread-only

sites_cacheSettingsread-only

AgentThe latest mobile run is weak on server response, and all three cache layers are off, so every visit runs PHP and the database. That is the most common cause on WordPress. Turning caching on is a dashboard step: Site, WordPress, Caching. Want the link and a look at the server load too?

YouYes, both.

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 to Speed up a slow site on xCloud?

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

1
Turn on developer mode and open Plugins
In ChatGPT on the web, open Settings, Security and login and turn on Developer mode. Then open the Plugins page and select the plus button to create an app. OpenAI lists developer mode for Pro, Plus, Business, Enterprise and Education accounts on the web, but its help center puts full MCP support with write actions in beta on Business, Enterprise and Edu workspaces and gives Pro accounts read and fetch access only, so check your plan before you expect ChatGPT to deploy or update anything. 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 last step.
URL
```
https://chatgpt.com/plugins
```
2
Create the app with the xCloud MCP URL
Name the app xcloud, paste this as the MCP server URL and choose OAuth for authentication. xCloud supports dynamic client registration, so you do not need to create a client ID. Sign in with xCloud when the browser asks, tick the teams and choose Read-only or Full access.
URL
```
https://app.xcloud.host/mcp
```
3
Install the plugin and use it in a Work chat
Open your personal Plugins page, open xcloud and select the plus button to install it. Back on the ChatGPT homepage, switch the tab at the top from Chat to Work, start a new Work chat, type @ and pick xcloud; a plain Chat tab conversation does not offer the plugin. Then type a request like this one.
Prompt
```
Using the xcloud app, who am I on xCloud and which servers do I have?
```

Check it worked

Then ask ChatGPT for the job itself, for example:

Prompt

Using the xcloud app, my store at shop.example.com has been slow on mobile since yesterday. Check the server load, the caches and the latest PageSpeed result, and tell me the most likely cause.

In practice

How Does Performance Work from ChatGPT?

In ChatGPT you pick the xcloud plugin for the conversation with @xcloud in a Work chat, and then write the way you would to a colleague: using the xcloud app, my store at shop.example.com has been slow on mobile since yesterday, can you check the server, the caches and the last PageSpeed result. Naming the app in the sentence matters, because ChatGPT chooses tools message by message, and with the app named it goes to xCloud instead of answering from general advice. It then runs the reads: the site and its server, the status, the monitoring history, the cache settings, PageSpeed and a bounded access-log window.

What comes back is an explanation you can paste into a ticket or forward to a developer: the numbers, the likeliest cause and what to do about it. ChatGPT is also comfortable with the follow-ups a person in a hurry asks, like whether a mobile score is bad or what a stopped Redis means for page loads. When the cause is a cache layer that is off, it does not flip it. It names the dashboard path, Site, WordPress, Caching, and the link xCloud gave it, because that switch lives only in the dashboard.

ChatGPT reaches xCloud from OpenAI's servers and cannot see your repository, so it diagnoses the hosting side only. A new PageSpeed scan and a cache purge are write actions, and developer mode asks for confirmation on those in its own dialog, on top of the heads-up the agent gives about spending a scan or throwing away a warm cache. Choose Read-only on the xCloud approval screen if you only want answers. The whole read chain works without write access.

ChatGPT specific: Two plans are in play, and they limit different things. Developer mode depends on your ChatGPT plan, while monitoring history depends on your xCloud plan: on a free xCloud team the history request is refused as a plan limit even though ChatGPT works fine. If the reply says history is unavailable, that is xCloud's plan limit, not a connection fault, and the other reads still work. The app sits under Drafts in ChatGPT's settings, where you can refresh its tool list if a read seems to be missing.

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 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 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 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

Using the xcloud app, my store at shop.example.com has been slow on mobile since yesterday. Check the server load, the caches and the latest PageSpeed result, and tell me the most likely cause.

Prompt

Using the xcloud app, is Redis object cache switched on for shop.example.com? If it is not, where do I turn it on?

Prompt

Using the xcloud app, look at the access log for shop.example.com and tell me whether a bot or a traffic spike could explain the slowdown.

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 and Performance: Frequently Asked Questions

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

Do I need to name the xcloud app when I ask ChatGPT about a slow site?

It helps. Pick the plugin with @xcloud in a Work chat, and start the message with using the xcloud app. ChatGPT picks tools per message, so naming the app makes it read your real site and server numbers instead of giving general speed advice.

Can ChatGPT purge my cache or start a PageSpeed scan?

Yes, if the app was approved with Full access, but both are write actions. ChatGPT asks you to confirm them in developer mode, and the agent tells you first that a scan is spent or a warm cache is thrown away. With Read-only access, neither can run.

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