The Experience Editor is where many content authors spend their day. When it's slow or unreliable, editors lose trust in Sitecore and fall back on the Content Editor, or stop updating the site. The causes are usually in the site's code and configuration, not in Sitecore itself, which means they can be fixed.
1. A rendering fails only in editing mode
Renderings run differently in the Experience Editor. Data sources may be empty, fields are wrapped in editing markup, and the context database is master rather than web. Code that works perfectly on the live site can throw errors here, for example when it assumes a data source always exists or a field always has a value.
Fix: check the Sitecore log while opening the page in the Experience Editor. Ask developers to handle empty data sources and empty fields gracefully, and to show a helpful message to editors instead of an error, such as "Choose a data source for this component".
2. Editors can't add components
If the "Add here" buttons don't appear, or a component isn't in the list, the placeholder settings usually don't allow it. Placeholder settings items define which renderings can go in each placeholder. On SXA sites, the available renderings also depend on the site's settings.
Fix: find the placeholder key in the page's layout, open the matching item under /sitecore/layout/Placeholder Settings and add the rendering to Allowed Controls. Also check that the placeholder setting is marked as editable.
3. Components disappeared after an upgrade
This one surprises many teams. Before Sitecore 9, dynamic placeholders were usually provided by community modules. Sitecore 9 introduced built-in dynamic placeholders with a different key format. After an upgrade, page layouts still contain the old keys, so components exist in the layout but no placeholder matches them. They seem to vanish from the page.
Fix: plan a migration of placeholder keys as part of the upgrade. A script can update the keys in layout fields across all pages. Test it on a copy of the content first. See the upgrade checklist for other things to plan for.
4. JavaScript or CSS conflicts
The Experience Editor loads its own scripts and styles on top of your site's. Front-end code that changes the page heavily, loads its own jQuery version, or uses CSS with very broad selectors can break the editing tools. Typical symptoms are a ribbon that doesn't load, buttons that don't respond, or chrome frames in the wrong place.
Fix: open the browser developer console in the Experience Editor and look for errors. Developers can check whether the page is in editing mode and skip scripts that aren't needed there, such as sliders, animations, cookie banners and tracking scripts.
5. The Experience Editor is very slow
Pages render without HTML caching in the Experience Editor, and each component adds editing markup. A page with dozens of components, each running its own queries, can take many seconds to load. Personalization rules and tests on many components add more work.
Fix:
- Profile the page with Sitecore's debug mode to find the slowest renderings.
- Fix renderings that query large parts of the content tree. The same fixes speed up the live site too. See the performance checklist.
- Keep pages to a sensible number of components, and split very long pages.
- Check that the content management server has enough CPU and memory, and that caches there aren't too small.
6. Fields can't be edited
If a field shows on the page but can't be clicked or edited, the rendering probably outputs the value as plain text instead of through Sitecore's field rendering helpers. Only fields rendered through Sitecore's helpers are editable in the Experience Editor.
Fix: ask developers to render editable fields with the Sitecore field helpers, and to use edit frames for settings that aren't visible on the page.
What to do next
Make a short list of the pages and components editors complain about most. Then check the Sitecore log and the browser console on those pages. Most fixes are small code changes. If you'd like help, improving the editing experience is a common part of my support work for agencies and in-house teams.
