Performance use case
Speed up WordPress with ChatGPT, one measured change at a time.
Connected through GoBuildWP Pro, ChatGPT can inspect supported detected cache layers, measure server-side delivery, propose one setting change and compare repeated runs. Experiment recovery covers captured restorable settings; check the returned per-layer outcomes and the public site separately.
GoBuildWP Pro, Works in ChatGPT, Runs under Production Safe, Pricing
Illustrative ability sequence for GoBuildWP Free 1.18.6 and Pro 1.12.4. IDs, results and recovery outcomes are examples, not a recorded client or WordPress test. Select Read Only explicitly for the initial reads; Production Safe is the default. Connection management requires manage_options on a single site or superadmin on multisite.
The problem
Why a chat window alone cannot fix a slow WordPress site
Most speed advice starts from a PageSpeed report and ends with someone ticking every box in a cache plugin. That is how sites end up with combined JavaScript that breaks the checkout, and nobody sure which of the twelve settings did it.
The version that works is slower and a little boring: know which layers exist, take a baseline, change one thing, measure again. ChatGPT is good at the reasoning in that loop. GoBuildWP supplies what it lacks: the list of layers on your site, a server-side measurement, typed settings writes and a snapshot to return to.
What ChatGPT can do here
- List every page-cache, asset, object-cache and edge layer on the site, with which settings each one can read and write
- Measure time to first byte over repeated requests, HIT or MISS headers, HTML weight, compression and render-blocking files
- Change one mapped setting on any of the 10 drivers with a shared settings map, such as LiteSpeed Cache, WP Rocket or WP-Optimize, then purge that layer
- Warm up to ten URLs after a purge, so the next measurement reads cache delivery rather than a cold page build
- Request recovery of captured restorable settings in one call, then inspect restored, skipped and failed layers
What it cannot do
- Measure LCP, CLS or INP from the server. Those exist in a browser; the Lighthouse scores come from Google PageSpeed Insights, through Free's pagespeed-check or a report you open
- Switch on combine, defer, delay, critical CSS or logged-in caching without confirm: true on the call. The client sets that flag itself, so the prompt asks it to stop for your OK first
- Purge a CDN or WAF in front of WordPress, such as Cloudflare or a host edge, that has its own control panel
- Fix slow hosting, a heavy theme or an unindexed database by changing a cache setting
The prompt
The prompt to paste into ChatGPT
Paste this into a ChatGPT conversation with the GoBuildWP app selected. It keeps ChatGPT in a measure, change, re-measure loop and tells it to ask before every write; check that it does.
- Two URLs matter: a home page and a shop or checkout page break in different ways.
- Step 4 keeps you in the loop. ChatGPT asks before each write instead of batching five of them.
- Step 6 is the honest part: GoBuildWP's own numbers are server-side. A PageSpeed score comes from Google, through pagespeed-check or a report you open.
Audit the speed of https://your-site.com/ and https://your-site.com/shop/.
1. Run cache-check-setup and list every layer you find, including edge layers you cannot purge.
2. Measure both URLs three times. Give me TTFB, HIT or MISS, HTML size and render-blocking files as a baseline.
3. Start a cache experiment before changing anything.
4. Propose the single lowest-risk change and wait for my OK.
5. Apply only that change, purge, warm both URLs, and measure again.
6. Run cache-verify-in-browser and give me the browser checks and PageSpeed links. Do not claim a score you did not see.
7. If anything got worse or a check fails, revert the experiment.
Never enable combine, defer or delay settings without asking me first.Under the prompt
The abilities ChatGPT will call
Registered GoBuildWP abilities, each with its own schema and permission check. The live ability list on your site is the final word; the tool map lists every group.
cache-check-setupEvery page, asset, object-cache and edge layer, and the purge scopes each supports
cache-begin-experimentSnapshots settings across all layers before tuning; changes nothing itself
cache-measure-pageServer-side delivery: TTFB, HIT or MISS, bytes, compression, render-blocking files
cache-get-settingsOne layer's settings in a shared vocabulary, with the risky keys marked
cache-set-settingsWrites mapped settings, purges the layer and stores a before-image
cache-purgePurges every detected WordPress layer, for the whole site, one URL or one post
cache-warmRequests up to ten URLs so the cache is rebuilt before you measure
cache-verify-in-browserNames likely breakage and returns browser checks plus PageSpeed report links
cache-revert-experimentAttempts captured settings recovery and declared purges; reports per-layer outcomes
Safety and recovery
Profile, change record and the way back
- Safety profile
- Read Only covers the audit: setup, settings and measurements are all reads. cache-begin-experiment stores a snapshot, so it is a write and starts the Production Safe half. There, the confirmation-gated keys are refused unless the call carries confirm: true, which the client sets itself; turn on the Pro approval queue if a person must approve each setting.
- Change ledger
- Each cache-set-settings call lands in the change ledger with the acting credential, the keys changed and a before-image of the old values.
- Rollback
- rollback-change covers supported before-images. cache-revert-experiment attempts recovery of the captured restorable settings across drivers; not_captured layers are excluded. Recovery can overwrite later edits and does not recreate generated files or external state. Verify storage readback and the public pages independently.
- #2290Experiment exp_7, 3 layers capturedSnapshot
- #2291LiteSpeed: images.lazyload onRollback available
- #2294Revert experiment exp_7Restored
What to check yourself
- Server timings move with host load. Compare runs taken minutes apart, three at a time, never a single request.
- A setting can read back as applied and still do nothing on the wire when the host or CDN overrides it. cache-verify-in-browser lists those blockers.
- Reverting writes option rows back directly. A plugin that generates rewrite rules or a config file may need one re-save in its own screen.
- Cache actions that delete rows, such as database cleanup, need confirmation and cannot be rolled back.
- Only the newest five experiments are kept.
How profiles, confirmations and rollback fit together: safety profiles and the change ledger.
Setup
Connect ChatGPT for a speed session
ChatGPT reaches your site from OpenAI's servers, which shapes two of these steps.
GoBuildWP Free includes performance-audit, bounded server-side checks with no synthetic score, system-status, and pagespeed-check, which asks Google PageSpeed Insights for a page's lab scores and any field data Google has. Enough to see whether caching is even on.
Pro adds the cache module: detection of 26 layers, the shared settings map, purge, warm, experiments and browser verification.
Install GoBuildWP Free and Pro
The cache module ships in Pro and only loads when a supported cache or optimisation plugin is active.
Use a public HTTPS address
A localhost or password-protected staging site cannot be reached by ChatGPT. Use a public staging copy for the first run.
Open custom MCP setup
On ChatGPT web, open Plugins, select the plus button, then Create custom MCP server. Your account and workspace must allow custom plugins.
Create the GoBuildWP plugin
Paste your site's GoBuildWP MCP URL, choose OAuth, review the trust warning and create the plugin. Install it and approve the connection in WordPress, then select it with @ in a new chat.
Audit in Read Only, tune in Production Safe
Run steps 1 and 2 of the prompt under Read Only. Switch to Production Safe before step 3, because starting the experiment saves a snapshot.
FAQ
Questions about how to speed up WordPress with ChatGPT
Can ChatGPT make my WordPress site faster on its own?
Not without access to the site. Connected through GoBuildWP Pro it can read your cache layers, measure delivery and change supported settings, so the gain comes from settings your plugins already offer. Hosting, theme weight and heavy plugins are outside what a cache setting can fix.
Will it give me a PageSpeed score?
Not from its own measurements, which are server-side. Free's pagespeed-check asks Google PageSpeed Insights and returns its scores, lab metrics and any field data, saying which service answered; the page URL is sent to Google, and possibly through GoBuildWP Cloud or Site Kit. cache-verify-in-browser returns report links and browser checks. A lab score is one simulated load, not what visitors experienced.
Which cache plugins does it work with?
26 layers are recognised. 10 of them, including LiteSpeed Cache, WP Rocket, WP-Optimize and SiteGround Speed Optimizer, have mapped settings; the rest are detected with their native options, purge callbacks or read-only evidence.
Which ChatGPT plans can connect?
Check whether Create custom MCP server is available on your ChatGPT Plugins page. Account access and workspace policy determine whether you can create and install a custom plugin.
What if a change breaks the layout?
Inspect the experiment's captured drivers before requesting cache-revert-experiment. It attempts supported settings recovery and purges, reports per-layer outcomes and records the action. Re-save generated configuration where required and independently check layout, forms and checkout; a stored-value match is not functional recovery.
Try it on staging first.
Install the free plugin, connect ChatGPT, and run the read-only half of this prompt before anything on the site changes.