Plugin analysis for website. Problem: Jetpack. Solution: GET RID OF JETPACK.

This is analysis from P3 Plugin Profiler plugin that I’ve installed to identify which plugin/s are consuming heavy resources (particularly MySQL). [See this for a list of plugins that check WordPress resource use]

FIRST TEST

DISABLE ALL JETPACK FEATURES AND TEST 

This site identifies Jetpack features that may hog resources (memory/CPU/SQL).

Disabled all Jetpack options. This is the result:

Even after disabling ALL Jetpack features, it hogs a lot of resources. Conclusion: BIN IT.

DELETE JETPACK AND TEST

[Note, I’ve reactivated “Add to Footer” for this test]

Removing Jetpack has reduced SQL queries by 10 (or more, since I’ve added back ‘add to footer’] and helped reduce load time.

There’s only good stuff that can come out of deleting Jetpack. All statistics monitoring can be done through google/ quantify, anyway.

SOLUTION: DELETE JETPACK FROM ALL INSTALLATIONS. This could dramatically reduce the memory/400/500 errors I keep getting.

And I’ve also deleted P3 Plugin Profiler.

MAKE SURE you clear the wordfence cache since cached copies of the site still contain references to jetpack and not finding it, slow down the site DRAMATICALLY