Very slow in initializing / opening
Hi,
I have a SfTextBox on a Blazor page of WASM App. It opens quickly. When I replace the SfTextBox with SfRIchTextEditor, it take more than 20 seconds to open. It does not matter if there is only one SfRichTextEditor or 5. It takes same time. Typing is slower too. But that I solved with suggestions from your site.
Do you have any suggestions?
Thanks
Harshad
Hi Harshad,
Rendering a single Editor in Blazor WASM should not take 20 seconds. However, if multiple instances are used, such delays can occur. This is actually a fairly common characteristic of the SfRichTextEditor in Blazor WASM rather than a typical misconfiguration. The observed behavior, such as long initial load times, similar delays regardless of the number of instances, and slower typing performance, generally stems from how the control is architected and loaded
- Enable Script/CSS Isolated Loading (Most Important)
<head> ... ..... <script src="https://cdn.syncfusion.com/blazor/33.2.3/sf-richtexteditor.min.js" type="text/javascript"></script> </head> |
- Use Custom Resource Generator (CRG) 🚀
- Select only RichTextEditor + required dependencies
- Download the optimized JS/CSS bundle
- This can reduce bundle size from ~10MB to ~500KB
- Only import required Editor features:
<PropertyGroup> <BlazorWebAssemblyLoadAllGlobalizationData>false</BlazorWebAssemblyLoadAllGlobalizationData> <BlazorEnableCompression>true</BlazorEnableCompression> <BlazorWebAssemblyPreserveCollationData>false</BlazorWebAssemblyPreserveCollationData> </PropertyGroup> |
Hi Vinitha,
I read your reply earlier but failed to respond quickly. Sorry for that.
Thank you for your solution. For now, I have switched to plain HTML for RichTextEditor and moving on with my project. I am planning to revert to SfRichTextEditor when time permits.
Thanks
Harshad
Hi Harshad,
No worries at all, thank you for getting back to us!
I’m glad to hear that switching to plain HTML has helped you continue making progress with your project. That sounds like a good practical approach for the time being.
Whenever you’re ready to revisit SfRichTextEditor, please feel free to reach out. We’ll be happy to assist you further and help ensure a smooth transition back, whether it’s troubleshooting, optimization, or implementation guidance.
Wishing you all the best with your current development, and we look forward to supporting you again when needed!
Hi,
I just wanted to let you know that I was using OnAfterRender() method to get some value from the database. While the database returned the data very quickly, actual display of components (paiting the screen) was taking too long. I switched to OnAfterRenderAsync method and it painted quickly. This resolves my issue.
Once again, very good component, like any other components from Syncfusion!
Thank you for your support!
Best regards,
Harshad
Hi Harshad,
Thank you for the update!
We're delighted to hear that switching from OnAfterRender() to OnAfterRenderAsync() resolved the rendering performance issue and improved the component's display time. It's great to know that the data retrieval was already performing well and that you've identified the rendering lifecycle as the key factor.
We truly appreciate your kind words about our components and your continued support of Syncfusion products. Feedback like yours means a lot to us and motivates us to keep improving our offerings.
Thank you again, and happy coding!
- 5 Replies
- 2 Participants
-
HA Harshad
- May 11, 2026 07:34 PM UTC
- Jul 2, 2026 07:44 AM UTC