Ask WordPress AI Engineer to investigate a specific slow page or action using measurable evidence. A focused request helps distinguish server processing, database work, external services and browser assets before changes are made.
IN THIS ARTICLE
01 Define the slow experience
Provide the exact URL or administrative action, approximate delay, device and login state. Note whether the first visit is slow but later visits are faster, and whether the issue started after an update or traffic change. Record a baseline with repeatable conditions.
02 Guide the investigation
- Select the correct website and open AI Engineer.
- Ask it to inspect available response timing, logs, WordPress state and relevant resource evidence before changing settings.
- Review whether the delay occurs before the initial response or while the browser loads and executes assets.
- Ask for one prioritised change tied to the evidence and an explanation of its expected effect.
- Test the change on staging where practical and approve the exact production scope only after review.
- Repeat the original measurement and check the affected business function.
What is a useful prompt?
“This product page takes several seconds before responding while logged out. Please inspect the available timing and logs, identify the most likely bottleneck and propose a measurable first change. Do not disable checkout features or install another cache plugin without explaining the compatibility impact.”
Does a speed score identify the root cause?
Not by itself. Scores can reflect different test devices, locations and historical field data. The Engineer's advice should connect a finding to the actual slow workflow. A faster public homepage does not prove that checkout or administration has improved.
Can the AI increase account resources automatically?
Do not assume it can change the hosting plan or exceed service limits. It works through available account tools and permissions. If sustained resource pressure requires a plan review, preserve measurements and discuss that requirement with support.
03 Verify correctness as well as speed
Check forms, navigation, cart and logged-in views after caching or asset changes. Avoid combining many speculative optimisations, because it becomes difficult to identify the cause of a regression. Keep the baseline, exact change and final result in the investigation record, including any unresolved external-service delay.