Record the symptom
Note the exact error, affected URL, time, browser and whether the problem affects visitors, administrators or both.
Slow pages and errors can come from hosting, plugins, themes, databases, images, caching, DNS or external services. Diagnose the symptom in a controlled order before changing multiple things at once.

Note the exact error, affected URL, time, browser and whether the problem affects visitors, administrators or both.
Updates, new plugins, theme edits, DNS changes, PHP changes and content imports are common clues when a problem appears suddenly.
A slow page can be caused by oversized media or JavaScript, while a 500 error or database error points to a different diagnostic path.
Conflicts are easier to identify in a staging or maintenance window. Do not disable production components blindly on an active store or business site.
PHP errors, web-server logs, database errors, CPU, memory and process limits can show whether the bottleneck is code, traffic or capacity.
Make a controlled change, test the same symptom and keep a rollback path. Multiple simultaneous changes make root-cause analysis harder.
Backups, DNS, email, testing and rollback.
Read the guide →Recovery, access, updates and shared responsibility.
Read the guide →Updates, access, monitoring and recovery planning.
Read the guide →Product pages, categories, technical SEO and measurement.
Read the guide →Build costs, running costs and extras.
Read the guide →Choose the right amount of work.
Read the guide →Find the cause before choosing a fix.
Read the guide →Use the Hosting Plan Finder → · Open the customer help centre →
No. Large images, uncached pages, plugins, database queries, third-party scripts and configuration can all cause slowness. Measure first.
Not blindly. Updates can fix known issues but can also introduce compatibility changes. Back up first and use a controlled test when possible.
Preserve the error details, check recent changes and review application/server logs. Avoid repeated random edits that remove useful evidence.
Yes. Share the URL and symptom first. Diagnostic access, scope and repair charges are confirmed before changes are made.