Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲0.33MB] [CPU: ▼1.45ms] Passed 4 tests
Server-side resources used by Boostsite Planner
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.80 ▲0.34 | 50.25 ▼22.55 |
Dashboard /wp-admin | 3.66 ▲0.36 | 57.42 ▲6.21 |
Posts /wp-admin/edit.php | 3.69 ▲0.34 | 65.46 ▲15.27 |
Add New Post /wp-admin/post-new.php | 6.22 ▲0.33 | 101.92 ▼4.72 |
Media Library /wp-admin/upload.php | 3.52 ▲0.29 | 53.70 ▲20.40 |
Server storage [IO: ▲8.38MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 76 new files
Database: no new tables, 8 new options
New WordPress options |
---|
theysaidso_admin_options |
settings_form |
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
settings_api |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
Boostsite Planner: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,817 ▲71 | 14.46 ▲0.09 | 1.63 ▼0.72 | 39.28 ▼23.23 |
Dashboard /wp-admin | 2,224 ▲36 | 5.82 ▲0.01 | 102.29 ▼5.69 | 72.73 ▲31.37 |
Posts /wp-admin/edit.php | 2,104 ▲15 | 1.97 ▼0.04 | 36.65 ▲0.09 | 32.75 ▼4.14 |
Add New Post /wp-admin/post-new.php | 1,680 ▲147 | 22.11 ▼1.22 | 750.59 ▲124.55 | 59.69 ▼3.35 |
Media Library /wp-admin/upload.php | 1,406 ▲21 | 4.24 ▲0.06 | 97.38 ▼10.37 | 47.60 ▲3.85 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- This plugin did not uninstall without warnings or errors
- > Deprecated in wp-includes/class-wp-hook.php+310
Non-static method Boostsite\AI_Plugin\PluginLoader::uninstall() should not be called statically
- The uninstall procedure has failed, leaving 8 options in the database
- theysaidso_admin_options
- settings_api
- widget_recent-posts
- widget_theysaidso_widget
- settings_form
- widget_recent-comments
- can_compress_scripts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/media.php' (include_path='.:/usr/share/php') in wp-content/plugins/boostsite-seo-audit-tool/plugin/Src/RestApi.php on line 8
- > PHP Warning
require_once(ABSPATHwp-admin/includes/media.php): failed to open stream: No such file or directory in wp-content/plugins/boostsite-seo-audit-tool/plugin/Src/RestApi.php on line 8
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/boostsite-seo-audit-tool/plugin/Src/RestApi.php on line 8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that require attention:
- Screenshots: These screenshots lack descriptions #1, #2, #3, #4 in boostsite-seo-audit-tool/assets to your readme.txt
boostsite-seo-audit-tool/boostsite.php 85% from 13 tests
The entry point to "Boostsite Planner" version 2.1 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("boostsite-seo-audit-tool.php" instead of "boostsite.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin54,989 lines of code in 46 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 17 | 3,319 | 129 | 40,962 |
JavaScript | 8 | 1,216 | 1,846 | 12,230 |
PHP | 18 | 499 | 557 | 1,665 |
PO File | 1 | 43 | 43 | 109 |
JSON | 2 | 0 | 0 | 23 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 22.20 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 96.00 |
Average method complexity | 3.19 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 22.00 |
Code structure | ||
---|---|---|
Namespaces | 5 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 10 | 100.00% |
▷ Final classes | 3 | 30.00% |
Methods | 93 | |
▷ Static methods | 14 | 15.05% |
▷ Public methods | 91 | 97.85% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 2.15% |
Functions | 6 | |
▷ Named functions | 2 | 33.33% |
▷ Anonymous functions | 4 | 66.67% |
Constants | 8 | |
▷ Global constants | 8 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 compressed PNG files occupy 0.01MB
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
asset/boostsite-logo.png | 10.75KB | 11.39KB | 0.00% |
asset/boostsite-icon.png | 1.44KB | 1.01KB | ▼ 29.77% |