Performance Troubleshooting for <Site Name>
This is backend audit sample for your site, check out the frontend audit sample.
π οΈ Fixes Attempted During Session
This section outlines any fixes we attempted during the troubleshooting session. This helps us all know the positive or negative effects of our changes.
1. Fix 1 for problem X
- What we hoped it would fix with evidence β hopeful outcome
- Results β actual outcome
- Any cautions/warnings for the future
2. Fix 2 for problem Y
- What we hoped it would fix with evidence β hopeful outcome
- Results β actual outcome
- Any cautions/warnings for the future
π¦ Special Considerations
Special considerations like particular landing pages that are key to the user journey of the site.
Any specific user actions like adding to the cart, signing up on a registration page etc
π§ Areas of Concern
Specific areas of concern in executive summary format
β± Short Term Solutions
These are action items which can generally be completed in a matter of days after testing on a staging site and can provide positive results.
β° High Priority
1. Issue 1
β
Advantages
- Reduces API calls
β Disadvantages
- Have to remember it is configured there (document in changelog) and working
2. Issue 2
β³ Low Priority
1. Clean database tables: X, Y and Z
β
Advantages
- Reduces database backup and restore times
- Makes database queries faster and uncached responses faster
β Disadvantages
- Can be time-consuming and wrong data can be deleted
π Exception(s)
- Test thoroughly on a staging website
π Long Term Solutions
These are action items which can take weeks or months to test thoroughly but they should be done if there is enough time and budget.
β° High Priority
1. Remove X and replace with Y
β
Advantages
- Removes bloat from the website and reduces TTFB
β Disadvantages
- Can be time-consuming
π Exception(s)
- Test thoroughly on a staging website
β³ Low Priority
1. Separate the environments
β
Advantages
- Avoids a lot of native performance issues
β Disadvantages
- Generally requires SSO to make the UX smooth
- Can be time-consuming and expensive
π Exception(s)
- Can cause unexpected behavior on the site
π Future Investigation
Section for areas that deserve a special audit devoted especially to them
ποΈ Overview
Screenshots of application processing time
π’ Potential Bottlenecks
Summary of different processes tracked as taking a long time to complete.
Slow Transaction 1
Evidence of slow action
What is responsible for the slow action
Suggestions on how to resolve
π₯οΈ Hosting and Infrastructure
This section covers the suitability of your DNS, hosting and infrastructure.
ποΈ Hosting
Evaluation of hosting environment and recommendations of any changes.
π Infrastructure
Feedback on
- CDN and CDN-like services
- Reverse Proxy
- Server structure feedback
π Plugins
Plugins causing issues with evidence where possible
Suggested solutions
Recommended alternatives
ποΈ Theme
Theme recommendations and feedback
π¨ Design
Design feedback and recommendations performance where relevant
Explanation of why the element is slow and how it can be improved
Element on this is taking Y time to load and delaying the page load time or key performance metric
πΎ Database
Slow query with evidence and exact query where possible
Whatβs responsible for the slow query
How it can be fixed
Reported to plugin/theme developers
Database table issues
βͺοΈ External Services
External Service 1
Problems and evidence
Suggested solutions
π Appendix
<site-name> Audit Script Raw Data β WP Bullet
Auditing <site-name>
WordPress Core Version 5.9.1
β¦ (10 pages more)