If large size image (or multiple images), say 7 MB, is embedded into email body and email is sent. Listener processes those and displays it Rich text editor in Inbound Corr case. But its taking time to render those images on UI, any suggestions for this ?
According to my knowledge, the web page performance is dependent on the amount of data we carry in a single request to render at browser. So, the time to load content is directly proportional to size of the content.
As you have images with huge size it will take time to render the content at browser end. Hence, please consider splitting the data size of each request.
I foresee following choices would give you some relief.
1) In pega, we can use "defer load content" option on dynamic layout where the correspondence exist to improve the performance.
2) (Design suggestions ) my choice - Consider processing the .Corrbody content (HTML code) and identify <img or <image> tags using string utility functions and replace them to show only the image name in correspondence instead of image content. To see full image you can give an link to open a popup to show the entire content of email or delegate the task to render the content in local email client window