Kelly Creative Help Centre
Practical WordPress help, without the guesswork
Clear guides for understanding WordPress problems, maintaining an established website and knowing when it is safe to fix something yourself — and when it is better to stop and investigate first.
You do not need to be a developer to use these guides. The aim is to help you understand what may be happening, what you can safely check and what the sensible next step is.
A useful starting point
Start with the symptom, not the solution
A slow, broken or difficult website can have several causes. Good troubleshooting narrows the problem before changing things.
- Understand what the symptom may mean
- Check the safest things first
- Avoid changes that make diagnosis harder
- Escalate when the website needs direct investigation
01
Plain English
Technical detail without unnecessary jargon
02
Safe steps first
Reversible checks before invasive changes
03
Evidence led
Diagnosis before another plugin or guess
04
Clear next steps
Know when DIY is enough and when it is not
Start with what you can see
Different website problems call for different questions
The guides cover the situations that usually cause uncertainty: something has broken, a site feels slow or fragile, routine care is unclear, or you are deciding whether a larger change is justified.
01
Something is broken
Errors, lockouts, failed updates, broken forms and other behaviour that needs calm troubleshooting.
02
The site feels slow
Performance symptoms, common bottlenecks and what measurements can — and cannot — tell you.
03
Keeping WordPress healthy
Updates, backups, maintenance and the routine checks that reduce avoidable website risk.
04
Making a website decision
When to repair, investigate, optimise, leave something alone or consider a larger technical change.
Latest WordPress guides
Read the problem before reaching for the fix
These articles are pulled automatically from the existing Help Centre category. Publish a new guide there and it becomes available here without rebuilding this page.
-
Slow Elementor Website Rebuilt for Speed and Stability Case Study
Read guide →: Slow Elementor Website Rebuilt for Speed and Stability Case StudyA slow website isn’t just annoying — it costs real money. When pages take too long to load, customers bounce, online orders drop, and Google quietly moves you…
-
WordPress White Screen of Death (Case Study)
Read guide →: WordPress White Screen of Death (Case Study)Few WordPress problems are as stressful as the dreaded White Screen of Death. One minute, your website is working great. Next, everything is gone — no dashboard, no…
-
Hacked WordPress Site Rescue in Under 3 Hours
Read guide →: Hacked WordPress Site Rescue in Under 3 HoursWhen a hacked website takes your business offline, every minute counts. This case study walks through how I restored a local Sunshine Coast company’s WordPress site after it…
-
Emergency Website Rescue: What to Do When Your Site Breaks
Read guide →: Emergency Website Rescue: What to Do When Your Site BreaksThis Emergency Website Rescue guide walks you through what to do in the first hour, how to avoid making things worse, and when it’s time to call in…
Knowing where to stop
A guide can explain the problem. It cannot inspect your website.
General advice is useful until the next safe step depends on your actual theme, plugins, hosting, data or recent changes.
Usually safe to self-check
The evidence is visible and the action is reversible
Checking an error message, testing another browser, reviewing a recovery email or confirming whether a backup exists can provide useful information without changing the system.
Time to investigate
The next change could affect data, access or website stability
If the fix requires editing production files, changing DNS, restoring data, disabling unfamiliar components or guessing at the cause, direct investigation is usually the safer next step.
Can’t find the answer you need?
Start with what is happening, not a diagnosis
Tell me which website is involved, what you expected to happen and what you can see instead. I can then work out whether the sensible next step is a simple answer, a bounded repair or a broader technical investigation.