Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
It is recommended to fix the following installer errors
- The plugin cannot be installed
- > Warning in wp-includes/class-wp-hook.php+310
call_user_func_array() expects parameter 1 to be a valid callback, class 'ppinger' does not have a method 'activate'
Server metrics [RAM: ▲0.03MB] [CPU: ▼3.80ms] Passed 4 tests
This is a short check of server-side resources used by PPinger
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 35.18 ▼6.08 |
| Dashboard /wp-admin | 3.34 ▲0.04 | 46.95 ▼3.23 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 44.79 ▼1.76 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 91.71 ▼4.11 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 37.01 ▲0.18 |
| PPinger /wp-admin/options-general.php?page=ppinger | 3.23 | 32.26 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| ppinger_lastmessage |
| db_upgraded |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for PPinger
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲69 | 13.27 ▼1.13 | 4.59 ▲2.91 | 40.28 ▼4.02 |
| Dashboard /wp-admin | 2,213 ▲25 | 5.86 ▲1.03 | 98.59 ▼18.94 | 37.31 ▼21.12 |
| Posts /wp-admin/edit.php | 2,090 ▲1 | 2.00 ▼0.00 | 36.15 ▼2.48 | 31.21 ▼1.37 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲3 | 23.41 ▲2.63 | 598.27 ▼9.48 | 56.81 ▼4.94 |
| Media Library /wp-admin/upload.php | 1,392 ▲4 | 4.22 ▼0.01 | 102.20 ▼6.49 | 40.77 ▼4.28 |
| PPinger /wp-admin/options-general.php?page=ppinger | 806 | 2.06 | 30.01 | 25.36 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- ppinger_lastmessage
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
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
The following issues need your attention
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/ppinger/ppinger.php:61
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need to be fixed:
- Plugin Name: Please specify the plugin name on the first line (
=== ppinger ===) - Screenshots: These screenshots do not have images: #1 (This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from), #2 (This is the second screen shot)
ppinger/ppinger.php Passed 13 tests
The main file in "PPinger" v. 3.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
44 characters long description:
Pings your blog to Pingomatic automatically.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin152 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 60 | 58 | 111 |
| PO File | 1 | 11 | 20 | 41 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.08 |
| Average class complexity | 5.00 |
| ▷ Minimum class complexity | 5.00 |
| ▷ Maximum class complexity | 5.00 |
| Average method complexity | 1.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.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 | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| cleverpluginslogo.png | 9.69KB | 4.33KB | ▼ 55.29% |