Requirements and responsibilities
Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: An owner wants faster WordPress pages and is considering a cache change.
xCloud agent capability boundaries · WordPress roles and capabilities
Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: One speed score cannot isolate cache, network and content effects.
Illustrative situation
Illustrative scenario, not a customer case study: An owner wants faster WordPress pages and is considering a cache change. A repeatable baseline distinguishes server delay from page weight.
Choose the approach
Measure representative public and authenticated pages before deciding. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · xCloud WordPress caching overview
Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Choose urls, test region, device and traffic window
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Choose urls, test region, device and traffic window; exact site identity, named approver and controlled sample data.
- Action
- Choose public and authenticated URLs, device, network and traffic window that represent the reported slowdown.
- Expected result
- Measurements can be compared later.
- Verify
- Measurements can be compared later. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the selected URL is atypical, add a representative business page.
Sources: WordPress roles and capabilities · xCloud WordPress caching overview
Step 2 of 5
Record current cache, PHP and resource settings
- Where
- xCloud team/site resource read and planning sheet
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Record current cache, php and resource settings; exact site identity, named approver and controlled sample data.
- Action
- Read current xCloud cache, PHP and server resource settings and note CDN or plugin layers; do not change them in a measurement-only task.
- Expected result
- The baseline includes relevant context.
- Verify
- The baseline includes relevant context. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a layer is unknown, label it rather than attributing delay to it.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · xCloud WordPress caching overview
Step 3 of 5
Collect repeated public and logged-in timings
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Collect repeated public and logged-in timings; exact site identity, named approver and controlled sample data.
- Action
- Take repeated timings for public and logged-in sessions, noting response behavior and page weight.
- Expected result
- There is a repeatable baseline for each state.
- Verify
- There is a repeatable baseline for each state. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If results vary widely, repeat under controlled conditions before recommending a change.
Sources: WordPress roles and capabilities · xCloud WordPress caching overview
Step 4 of 5
Inspect slow requests and application behavior
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Inspect slow requests and application behavior; exact site identity, named approver and controlled sample data.
- Action
- Inspect whether delay comes from server response, large assets or external scripts, and compare the dynamic path separately.
- Expected result
- The team has a plausible bottleneck hypothesis.
- Verify
- The team has a plausible bottleneck hypothesis. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If evidence does not distinguish causes, run a narrower test.
Sources: WordPress roles and capabilities · xCloud WordPress caching overview
Step 5 of 5
Select one candidate change and preserve baseline
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Select one candidate change and preserve baseline; exact site identity, named approver and controlled sample data.
- Action
- Write one proposed cache or resource experiment with rollback setting and the same measurements to repeat later.
- Expected result
- The owner can approve a controlled change separately.
- Verify
- The owner can approve a controlled change separately. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- Do not edit cache settings until the experiment and acceptance criteria are agreed.
Sources: WordPress roles and capabilities · xCloud WordPress caching overview
Maintenance
Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: A repeatable baseline distinguishes server delay from page weight. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · Vulnerability Checker in xCloud
Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone.
Recovery decisions
This review does not change production settings. Keep the original measurements and configuration, then write a separately approved experiment and rollback criterion before any cache, PHP or capacity change.
xCloud WordPress caching overview · xCloud agent capability boundaries
AI handoff
Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Review a WordPress business journey app · manual
Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence.
Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision.
Copyable agent brief
Manual checkpoints
- The named site, business or provider owner supplies application evidence the connected hosting reads cannot observe.
- A separately approved operator performs any later configuration, staging, update, restore or publication described in the decision sheet.
- The owner accepts the review finding and proposed checks without treating the unexecuted change as completed.
Feature coverage
- business-acceptance (covered): A repeatable baseline distinguishes server delay from page weight. Inspect slow requests and application behavior
- recovery (covered): One speed score cannot isolate cache, network and content effects. Select one candidate change and preserve baseline
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- xCloud MCP documentation and connection profiles
- xCloud WordPress caching overview
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud