Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.12MB] [CPU: ▲0.32ms] Passed 4 tests
An overview of server-side resources used by Lotos Likes
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.59 ▲0.13 | 41.41 ▲0.32 |
Dashboard /wp-admin | 3.43 ▲0.12 | 44.40 ▼4.00 |
Posts /wp-admin/edit.php | 3.54 ▲0.18 | 48.36 ▲3.19 |
Add New Post /wp-admin/post-new.php | 6.01 ▲0.12 | 95.90 ▲3.35 |
Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 37.74 ▲1.78 |
Lotos Likes /wp-admin/admin.php?page=lotos-likes | 3.32 | 31.16 |
Server storage [IO: ▲0.17MB] [DB: ▲0.07MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 14 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_lotos_likes_widget |
theysaidso_admin_options |
widget_theysaidso_widget |
db_upgraded |
widget_recent-comments |
widget_recent-posts |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Lotos Likes
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,926 ▲191 | 14.01 ▼0.39 | 6.06 ▲4.15 | 42.92 ▼3.74 |
Dashboard /wp-admin | 2,221 ▲33 | 4.91 ▲0.07 | 98.07 ▼11.00 | 73.44 ▲29.42 |
Posts /wp-admin/edit.php | 2,110 ▲21 | 2.01 ▼0.03 | 39.03 ▲2.96 | 33.68 ▼2.02 |
Add New Post /wp-admin/post-new.php | 1,527 ▼1 | 17.51 ▼0.69 | 720.24 ▲102.36 | 55.77 ▲3.43 |
Media Library /wp-admin/upload.php | 1,394 ▲6 | 4.18 ▼0.04 | 94.92 ▼4.62 | 66.05 ▲24.89 |
Lotos Likes /wp-admin/admin.php?page=lotos-likes | 917 | 2.19 | 23.71 | 24.86 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 7 options
- theysaidso_admin_options
- widget_lotos_likes_widget
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
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
Good news, no errors were detected
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 fix the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/lotos-likes/lotos-likes.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
6 plugin tags: services, shortcode, likes, template tag, post...
lotos-likes/lotos-likes.php 92% from 13 tests
The entry point to "Lotos Likes" version 1.5 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- 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 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected527 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 88 | 29 | 349 |
PO File | 1 | 40 | 40 | 122 |
JavaScript | 1 | 5 | 0 | 33 |
CSS | 1 | 1 | 0 | 23 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
Average class complexity | 35.00 |
▷ Minimum class complexity | 6.00 |
▷ Maximum class complexity | 64.00 |
Average method complexity | 3.62 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 21.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 | 27 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 27 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 1 | 50.00% |
▷ Anonymous functions | 1 | 50.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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
5 PNG files occupy 0.12MB with 0.09MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/heart_active.png | 1.07KB | 0.29KB | ▼ 73.00% |
images/heart.png | 1.07KB | 0.29KB | ▼ 72.56% |
screenshot-1.png | 99.68KB | 36.19KB | ▼ 63.69% |
images/favicon.png | 20.48KB | 0.63KB | ▼ 96.91% |
images/hearts.png | 0.95KB | 0.48KB | ▼ 48.92% |