Improving Universal Editor performance in AEM as a Cloud Service under poor network conditions
This article provides steps to diagnose and improve Universal Editor performance in Adobe Experience Manager as a Cloud Service when delays or unresponsiveness occur due to poor network conditions.
Description description
Environment
Adobe Experience Manager as a Cloud Service with Universal Editor
Issue/Symptoms
- Universal Editor responds slowly, the canvas updates late, or timeout dialogs appear when authors use a high-latency or low-bandwidth network, such as a remote-office or VPN connection.
- The same page responds differently when tested over a different network path.
- Complex pages or custom project code also need to be checked during diagnosis.
Cause
A difference in responsiveness between network paths establishes a correlation, not proof that the network is the only cause. Request timings in a HAR help distinguish network delays from slow page or project responses. Complex pages and custom extensions should also be reviewed. Adobe’s Universal Editor documentation lists supported browsers but does not publish a numerical minimum network bandwidth or latency requirement.
Resolution resolution
Follow these steps to investigate Universal Editor slowness:
- Test the same page and authoring action over the affected network and a different network path, such as a non-VPN connection where your organization permits it. Record whether the delay occurs on one path or both.
- Capture a HAR while reproducing the issue. Review request timing to identify slow or pending requests. Before sharing the file, review it for session cookies, authorization headers, credentials, and sensitive request or response data. Remove or redact sensitive values unless Adobe Support requests them through an approved secure channel.
- Review the page and project implementation for complex content, custom blocks, or Universal Editor extensions. Compare the request timings before changing project code, then test any approved optimization in a lower environment.
- Confirm that you use a browser supported for Universal Editor. Adobe does not publish a numerical minimum bandwidth or latency requirement; ask your network administrator to review the affected network path if the same page performs better elsewhere.
- If the issue remains reproducible, open an Adobe Support case with the steps, affected page, test network paths, timestamps, and a sanitized HAR. Compare responsiveness after any approved network or project change.
To verify the investigation, repeat the same authoring action under the same test conditions and compare the request timings and editor response.