Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▼0.11MB] [CPU: ▼18.79ms] Passed 4 tests
Analyzing server-side resources used by Webtocall Newcallcenter
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.08 | 24.91 ▼15.67 |
| Dashboard /wp-admin | 3.23 ▼0.08 | 27.99 ▼19.47 |
| Posts /wp-admin/edit.php | 3.30 ▼0.06 | 30.89 ▼12.85 |
| Add New Post /wp-admin/post-new.php | 5.54 ▼0.35 | 64.29 ▼27.17 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 27.12 ▼8.68 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 22 new files
Database: 1 new table, 6 new options
| New tables |
|---|
| wp_newcallcenter_call_log |
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Webtocall Newcallcenter
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,902 ▲156 | 13.71 ▼0.70 | 6.10 ▲4.21 | 42.48 ▼3.77 |
| Dashboard /wp-admin | 2,215 ▲27 | 5.86 ▲0.94 | 99.16 ▼18.56 | 39.52 ▼3.77 |
| Posts /wp-admin/edit.php | 2,098 ▲9 | 2.01 ▼0.04 | 40.04 ▲2.49 | 34.67 ▼0.29 |
| Add New Post /wp-admin/post-new.php | 1,524 ▲10 | 17.43 ▼0.40 | 638.40 ▲32.60 | 67.44 ▲14.68 |
| Media Library /wp-admin/upload.php | 1,403 ▲15 | 4.19 ▲0.01 | 94.24 ▼5.19 | 41.46 ▼1.30 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- The uninstall procedure failed, leaving 1 table in the database
- wp_newcallcenter_call_log
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, 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
Almost there! Just fix the following items
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/newcallcenter-webtocall/public/partials/newcallcenter-public-display.php
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
4 plugin tags: callcenter, newip, webtocall, ncc3
newcallcenter-webtocall/newcallcenter.php 85% from 13 tests
"Webtocall Newcallcenter" version 1.0.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("newcallcenter-webtocall.php" instead of "newcallcenter.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Success! There were no dangerous files found in this plugin1,162 lines of code in 15 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 11 | 165 | 471 | 467 |
| CSS | 2 | 47 | 17 | 355 |
| JavaScript | 2 | 97 | 9 | 340 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 6.14 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 24.00 |
| Average method complexity | 1.97 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 11.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 7 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 7 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 37 | |
| ▷ Static methods | 2 | 5.41% |
| ▷ Public methods | 32 | 86.49% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 13.51% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.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
1 PNG file occupies 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot/screenshot.PNG | 31.77KB | 15.26KB | ▼ 51.95% |