Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
You still need to fix the following installer errors
- Install procedure had errors
- > Notice in wp-content/plugins/wp-like-button/crudlab-fb-like-button.php+186
Undefined variable: user_id
Server metrics [RAM: ▲0.17MB] [CPU: ▲1.76ms] Passed 4 tests
This is a short check of server-side resources used by WP Like Button
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.64 ▲0.17 | 48.09 ▲7.19 |
Dashboard /wp-admin | 3.47 ▲0.17 | 55.95 ▼2.70 |
Posts /wp-admin/edit.php | 3.59 ▲0.23 | 54.76 ▲3.27 |
Add New Post /wp-admin/post-new.php | 6.06 ▲0.17 | 102.00 ▼0.72 |
Media Library /wp-admin/upload.php | 3.40 ▲0.17 | 46.59 ▲9.34 |
Server storage [IO: ▲0.21MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 16 new files
Database: 1 new table, 8 new options
New tables |
---|
wp_fblb |
New WordPress options |
---|
wpfblike_db_version |
crudlab_fblb_install |
db_upgraded |
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Like Button
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,821 ▲60 | 14.04 ▼0.31 | 41.14 ▲39.20 | 46.03 ▲0.07 |
Dashboard /wp-admin | 2,201 ▲24 | 5.58 ▲0.01 | 85.68 ▼9.97 | 72.47 ▲25.76 |
Posts /wp-admin/edit.php | 2,124 ▲24 | 1.98 ▼0.04 | 39.36 ▲2.95 | 34.42 ▼2.58 |
Add New Post /wp-admin/post-new.php | 1,695 ▲169 | 21.91 ▼1.87 | 691.41 ▼21.05 | 52.17 ▼8.68 |
Media Library /wp-admin/upload.php | 1,412 ▲12 | 4.20 ▲0.02 | 105.98 ▼3.98 | 70.73 ▲25.81 |
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
- Zombie WordPress options were found after uninstall: 8 options
- widget_recent-posts
- wpfblike_db_version
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- crudlab_fblb_install
- 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 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/wp-like-button/crudlab-fb-like-button.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Tags: There are too many tags (15 tag instead of maximum 10)
wp-like-button/crudlab-fb-like-button.php 92% from 13 tests
This is the main PHP file of "WP Like Button" version 1.7.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please make the necessary changes and fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-like-button.php" instead of "crudlab-fb-like-button.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
No dangerous file extensions were detected2,811 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 3 | 44 | 59 | 1,613 |
PHP | 3 | 58 | 16 | 1,026 |
JavaScript | 2 | 27 | 6 | 172 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.49 |
Average class complexity | 62.00 |
▷ Minimum class complexity | 37.00 |
▷ Maximum class complexity | 87.00 |
Average method complexity | 4.94 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 36.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 31 | |
▷ Static methods | 2 | 6.45% |
▷ Public methods | 25 | 80.65% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 6 | 19.35% |
Functions | 1 | |
▷ Named functions | 1 | 100.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
7 PNG files occupy 0.07MB with 0.05MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/ico1.png | 3.53KB | 0.63KB | ▼ 82.20% |
images/off - Copy.png | 3.74KB | 1.14KB | ▼ 69.52% |
images/off.png | 3.75KB | 1.07KB | ▼ 71.38% |
images/help.png | 4.56KB | 1.57KB | ▼ 65.61% |
images/ico.png | 3.11KB | 0.67KB | ▼ 78.53% |