Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▼1.20MB] [CPU: ▼39.60ms] Passed 4 tests
This is a short check of server-side resources used by = limecall-widget
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.77 ▼0.69 | 14.09 ▼24.09 |
| Dashboard /wp-admin | 2.81 ▼0.49 | 17.37 ▼28.13 |
| Posts /wp-admin/edit.php | 2.81 ▼0.54 | 15.60 ▼29.89 |
| Add New Post /wp-admin/post-new.php | 2.81 ▼3.07 | 17.87 ▼76.29 |
| Media Library /wp-admin/upload.php | 2.81 ▼0.42 | 17.20 ▼17.35 |
| LimeCall /wp-admin/options-general.php?page=limecall-widget | 2.82 | 16.11 |
Server storage [IO: ▲1.03MB] [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: 62 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| widget_recent-comments |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for = limecall-widget
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,797 ▲51 | 14.67 ▲0.32 | 1.65 ▼0.00 | 43.14 ▲1.86 |
| Dashboard /wp-admin | 2,200 ▲23 | 5.50 ▼0.12 | 83.66 ▼6.92 | 36.77 ▼4.29 |
| Posts /wp-admin/edit.php | 2,108 ▲11 | 1.98 ▼0.02 | 32.50 ▼2.69 | 33.08 ▼3.71 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲5 | 23.16 ▼0.04 | 646.74 ▼28.21 | 69.40 ▲13.05 |
| Media Library /wp-admin/upload.php | 1,411 ▲8 | 4.23 ▲0.06 | 99.15 ▲0.65 | 44.98 ▼1.01 |
| LimeCall /wp-admin/options-general.php?page=limecall-widget | 872 | 1.99 | 24.62 | 40.53 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin did not uninstall without warnings or errors
- > Notice in wp-content/plugins/limecall-widget/public/class-limecall-widget-public.php+28
Trying to access array offset on value of type bool
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- can_compress_scripts
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
These errors were triggered by the plugin
- > GET request to /wp-admin/options-general.php?page=limecall-widget
- > Notice in wp-content/plugins/limecall-widget/public/class-limecall-widget-public.php+28
Trying to access array offset on value of type bool
SRP 0% 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 items
- 2× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/limecall-widget/public/parts/limecall-public-display.php
- > /wp-content/plugins/limecall-widget/limecall/public/parts/limecall-public-display.php
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/limecall-widget/limecall/admin/parts/limecall-admin-display.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/limecall-widget/admin/parts/limecall-admin-display.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that need to be fixed:
- Tags: You are using too many tags: 11 tag instead of maximum 10
limecall-widget/limecall-widget.php 92% from 13 tests
The primary PHP file in "= limecall-widget" version 1.0 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
No dangerous file extensions were detected547 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 13 | 61 | 229 | 290 |
| CSS | 2 | 0 | 2 | 182 |
| PO File | 2 | 23 | 24 | 75 |
| JavaScript | 1 | 0 | 1 | 0 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.15 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 9.00 |
| Average method complexity | 1.47 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 14 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 14 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 60 | |
| ▷ Static methods | 4 | 6.67% |
| ▷ Public methods | 50 | 83.33% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 10 | 16.67% |
| Functions | 6 | |
| ▷ Named functions | 6 | 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 50% from 2 tests
Image compression 50% from 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
10 PNG files occupy 0.93MB with 0.53MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| limecall/assets/screenshot-1.png | 389.83KB | 101.07KB | ▼ 74.07% |
| limecall/assets/screenshot-2.png | 84.58KB | 23.80KB | ▼ 71.86% |
| admin/imgs/insert-limecall.png | 0.27KB | 0.22KB | ▼ 19.27% |
| assets/screenshot-2.png | 84.58KB | 23.80KB | ▼ 71.86% |
| admin/imgs/find-limecall-icon.png | 0.81KB | 0.41KB | ▼ 49.04% |