Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.17ms] Passed 4 tests
A check of server-side resources used by Mobile Contact Buttons
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 34.27 ▼4.92 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 44.09 ▼4.49 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.77 ▼4.62 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 87.34 ▼2.66 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.48 ▲1.18 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Mobile Contact Buttons
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,833 ▲87 | 14.48 ▼0.11 | 1.62 ▼0.58 | 37.48 ▼7.80 |
| Dashboard /wp-admin | 2,206 ▲21 | 5.90 ▲0.79 | 107.93 ▼9.45 | 43.19 ▼5.65 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 1.97 ▼0.05 | 38.83 ▲2.46 | 36.57 ▲0.57 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲19 | 23.11 ▲5.69 | 628.31 ▼51.76 | 51.64 ▼10.42 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.28 ▲0.02 | 97.05 ▼4.66 | 41.21 ▼4.65 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means an exhaustive test
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 take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_deactivation_hook() in wp-content/plugins/mobile-contact-buttons/mobile-contact-buttons.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% 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
Attributes that need to be fixed:
- Tags: Please reduce the number of tags, currently 12 tag instead of maximum 10
mobile-contact-buttons/mobile-contact-buttons.php 92% from 13 tests
"Mobile Contact Buttons" version 1.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
You should first fix the following items:
- Description: Keep the plugin description shorter than 140 characters (currently 171 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected208 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 18 | 7 | 145 |
| CSS | 1 | 1 | 0 | 63 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.04 |
| 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 | 5 | |
| ▷ Named functions | 5 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
There were not PNG files found in your plugin