Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼7.61ms] Passed 4 tests
Server-side resources used by WhatCX Widget
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.02 | 39.97 ▼9.43 |
Dashboard /wp-admin | 3.33 ▲0.03 | 48.59 ▼9.27 |
Posts /wp-admin/edit.php | 3.38 ▲0.03 | 51.75 ▲2.44 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 91.05 ▼8.84 |
Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 37.91 ▼2.89 |
Server storage [IO: ▲0.37MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 23 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WhatCX Widget
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲43 | 14.24 ▼0.02 | 1.63 ▼0.44 | 48.26 ▲4.95 |
Dashboard /wp-admin | 2,207 ▲27 | 5.54 ▼0.13 | 88.43 ▼8.88 | 75.30 ▲30.77 |
Posts /wp-admin/edit.php | 2,118 ▲18 | 1.98 ▼0.02 | 36.03 ▼0.38 | 31.05 ▼5.01 |
Add New Post /wp-admin/post-new.php | 1,692 ▲157 | 22.35 ▲4.02 | 787.34 ▲162.97 | 61.90 ▼5.03 |
Media Library /wp-admin/upload.php | 1,412 ▲12 | 4.15 ▼0.01 | 99.99 ▼10.15 | 80.75 ▲31.38 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check 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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following items
- 3× 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/whatcx-widget/api-action.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_enqueue_style() in wp-content/plugins/whatcx-widget/form.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/whatcx-widget/api-action.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
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
2 plugin tags: whatsapp, widget
whatcx-widget/whatcx-widget.php 92% from 13 tests
The main file in "WhatCX Widget" v. 1.0.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 236 characters long)
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
Good job! No executable or dangerous file extensions detected880 lines of code in 13 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 34 | 17 | 352 |
CSS | 5 | 5 | 15 | 301 |
JavaScript | 5 | 6 | 34 | 227 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.22 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 7 | |
▷ Named functions | 6 | 85.71% |
▷ Anonymous functions | 1 | 14.29% |
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
9 PNG files occupy 0.04MB with 0.01MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/icon2.png | 0.65KB | 0.81KB | 0.00% |
assets/img/logo.png | 4.70KB | 3.28KB | ▼ 30.19% |
assets/img/scanner.png | 0.40KB | 0.28KB | ▼ 31.40% |
assets/img/icon.png | 0.68KB | 0.88KB | 0.00% |
assets/img/bg.png | 21.70KB | 9.74KB | ▼ 55.09% |