After years of supporting Sitecore sites for agencies and businesses, I see the same problems again and again. The details change from site to site, but the causes repeat. If your team is frustrated with Sitecore, the problem is very likely on this list, and it's very likely fixable.
Below is each problem in one paragraph: what it looks like, why it usually happens, and where to find the full fix.
1. Pages are slow
What you see: pages take two seconds or more to start loading, the site gets slower under traffic, or the first visit after a deploy is painfully slow.
Usual cause: HTML caching switched off on renderings, code that loops over large parts of the content tree, too many database or search queries per page, and caches that are too small.
Fix: The Sitecore performance checklist.
2. Publishing is slow or gets stuck
What you see: publishing takes hours, the publish dialog sits on the same number, or editors queue up waiting for each other.
Usual cause: full-site republishes used as a habit, very large EventQueue and PublishQueue tables, and index rebuilds triggered by each publish.
Fix: Why Sitecore publishing is slow, and how to speed it up.
3. Content doesn't update after publishing
What you see: the editor publishes, gets a success message, and the live site still shows the old content. Sometimes only one server is out of date.
Usual cause: items not in a final workflow state, caches that don't clear on every server, remote events not being processed, or a CDN caching the old page.
Fix: Sitecore content not updating after publish.
4. Search is broken or results are missing
What you see: site search returns old or missing results, listing pages are empty, or an index rebuild never finishes.
Usual cause: Solr indexes that are out of sync, the wrong index update strategy, a Solr schema that wasn't updated, or a Solr server that's out of memory.
Fix: Sitecore Solr index problems and how to fix them.
5. xConnect and xDB errors fill the logs
What you see: the logs are full of xConnect errors, forms or analytics stop working, or the Experience Profile is empty.
Usual cause: expired certificates, Windows services that stopped, and xDB switched on even though nobody uses it.
Fix: Fixing Sitecore xConnect and xDB errors.
6. Databases keep growing
What you see: disks fill up, backups take longer every month, and SQL Server gets slower.
Usual cause: cleanup tasks that aren't keeping up, SQL transaction logs that are never backed up, unused media still stored in the database, and no regular SQL index maintenance.
Fix: Sitecore database growth: what to clean up and how.
7. The Experience Editor is slow or broken
What you see: the Experience Editor takes ages to load, components disappear, editors can't add components, or JavaScript errors stop it working.
Usual cause: renderings that throw errors in editing mode, missing placeholder settings, placeholder keys that changed during an upgrade, and front-end scripts that clash with Sitecore's own.
Fix: Sitecore Experience Editor problems and fixes.
8. Deployments break things
What you see: a setting works on the test server but not in production, a deployment overwrites content, or the site fails with an assembly error after a release.
Usual cause: config patches applied in the wrong order or to the wrong server role, serialization overwriting content items, and Sitecore DLLs replaced by different versions during a build.
Fix: Sitecore deployment and configuration problems.
9. Security patches are behind
What you see: nothing at all, until a penetration test or an attack finds it.
Usual cause: security hotfixes never applied, admin pages reachable on public servers, and default settings left in place.
Fix: Sitecore security: patching and hardening basics.
10. The version is old and the upgrade feels too big
What you see: the site runs Sitecore 9.x, support is ending or has ended, and every upgrade quote looks huge.
Usual cause: years of customizations nobody documented, and upgrades put off until they became projects.
Fix: Sitecore 9.3 to 10.x upgrade checklist.
The pattern behind most of these
Very few of these problems are caused by Sitecore being "bad". Most come from small things that build up over the years: cleanup tasks nobody watches, settings copied from an old project, patches that were never applied, and knowledge that left with a developer. That's good news, because it means a focused health check usually finds the causes in days, not months.
What to do next
Pick the problem that hurts your team the most and read the full guide. If you'd like a second pair of eyes, I offer a fixed-price Sitecore health check that covers everything on this list and gives you a written, prioritized report. Book a free 20-minute call to talk it through.
