Could not reproduce the issue. See images on thsi case.

I have reduced the image size on Helpdesk to 200kb.

Possible reasons listed below:

Most likely the image is being loaded or embedded through the ASPxHtmlEditor as Base64 content. Once images exceed a size threshold, the editor’s callback/postback payload becomes very large, so the UI stays in its “busy” state while the browser uploads, decodes, renders, or saves it.

Common causes:

• Images are inserted as Base64 instead of stored as files/URLs.
• Very large pixel dimensions—even if the file size seems reasonable—make browser decoding and editor rendering slow.
• The Helpdesk app resizes or scans images synchronously during upload.
• IIS/ASP.NET request-size or execution-time limits are being approached, causing retries/timeouts.
• The editor content is stored in a database field, with image data included in the HTML, making load/save queries and page responses large.

The Height and Width settings shown are unlikely to be the cause; they only control the editor’s displayed dimensions.

The usual fix is to resize/compress images on upload and store them separately (file storage/object storage), inserting a normal image URL into the editor rather than embedding image bytes in the HTML. Also inspect browser Network timing and server logs for the slow request—this will quickly distinguish upload latency from server-side image processing or a database/save bottleneck.