What You’ll Learn
- Performance test methodology used
- Detailed results from three testing tools
- How the Child plugin handles requests
Test Results Summary
| Tool | Without MainWP Child | With MainWP Child | Difference |
|---|---|---|---|
| Pingdom | 241 ms | 221 ms | -20 ms |
| Lighthouse | 0.33 s | 0.33 s | 0 ms |
| GTMetrix | 933 ms | 951 ms | +18 ms |
Detailed Test Results
Pingdom
Without MainWP Child:| Run | Load Time |
|---|---|
| 1 | 299 ms |
| 2 | 187 ms |
| 3 | 237 ms |
| Average | 241 ms |
| Run | Load Time |
|---|---|
| 1 | 244 ms |
| 2 | 187 ms |
| 3 | 234 ms |
| Average | 221 ms |
Lighthouse
Without MainWP Child:| Run | Load Time |
|---|---|
| 1 | 0.3 s |
| 2 | 0.4 s |
| 3 | 0.3 s |
| Average | 0.33 s |
| Run | Load Time |
|---|---|
| 1 | 0.4 s |
| 2 | 0.3 s |
| 3 | 0.3 s |
| Average | 0.33 s |
GTMetrix
Without MainWP Child:| Run | Load Time |
|---|---|
| 1 | 979 ms |
| 2 | 927 ms |
| 3 | 893 ms |
| Average | 933 ms |
| Run | Load Time |
|---|---|
| 1 | 977 ms |
| 2 | 901 ms |
| 3 | 974 ms |
| Average | 951 ms |
Why There’s No Performance Impact
The MainWP Child plugin is designed to have minimal footprint on frontend performance:- Backend-only processing - The plugin primarily handles admin-side operations
- No frontend scripts - No JavaScript or CSS added to public-facing pages
- Request-based activation - Code only runs when the Dashboard communicates with the site
- Optimized queries - Database interactions are minimized and optimized
Related Resources
- How Secure is the MainWP Plugin - Security considerations
- MainWP System Requirements - Requirements for optimal performance