Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼2.72ms] Passed 4 tests
Analyzing server-side resources used by Pepper Connector
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 42.01 ▼4.62 |
Dashboard /wp-admin | 3.32 ▲0.02 | 48.49 ▼4.89 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 54.56 ▲4.87 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 88.95 ▲0.57 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.41 ▼1.95 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 9 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-posts |
widget_recent-comments |
widget_theysaidso_widget |
pepper_settings_option_name |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Pepper Connector
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,826 ▲65 | 14.35 ▼0.18 | 1.89 ▲0.02 | 45.06 ▲0.01 |
Dashboard /wp-admin | 2,204 ▲24 | 5.57 ▼0.10 | 109.01 ▲17.89 | 41.65 ▲2.53 |
Posts /wp-admin/edit.php | 2,115 ▲15 | 1.99 ▲0.01 | 35.35 ▼1.01 | 31.82 ▼3.02 |
Add New Post /wp-admin/post-new.php | 1,536 ▲8 | 23.66 ▲0.62 | 669.78 ▲41.03 | 55.83 ▲7.13 |
Media Library /wp-admin/upload.php | 1,412 ▲9 | 4.18 ▼0.03 | 97.69 ▼4.39 | 41.66 ▼1.09 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
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
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 5× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pepper-connector/includes/get_apis.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/pepper-connector/includes/settings.php:135
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pepper-connector/includes/webhooks.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pepper-connector/includes/post_apis.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function register_uninstall_hook() in wp-content/plugins/pepper-connector/pepper.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
5 plugin tags: pepperconnector, share content, pepper, peppercontent, blog
pepper-connector/pepper.php 77% from 13 tests
The main file in "Pepper Connector" v. 2.0.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("pepper-connector.php" instead of "pepper.php")
- Domain Path: The domain path points to a folder that does not exist ("/languages")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Success! There were no dangerous files found in this plugin991 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 170 | 51 | 990 |
Markdown | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.27 |
Average class complexity | 11.00 |
▷ Minimum class complexity | 11.00 |
▷ Maximum class complexity | 11.00 |
Average method complexity | 2.25 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 5.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 8 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 8 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 55 | |
▷ Named functions | 23 | 41.82% |
▷ Anonymous functions | 32 | 58.18% |
Constants | 2 | |
▷ Global constants | 2 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
There are no PNG files in this plugin