Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.23MB] [CPU: ▼3.78ms] Passed 4 tests
This is a short check of server-side resources used by WP Client Reports
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.69 ▲0.22 | 36.50 ▼4.58 |
| Dashboard /wp-admin | 3.54 ▲0.24 | 45.50 ▼2.08 |
| Posts /wp-admin/edit.php | 3.66 ▲0.30 | 48.09 ▼3.13 |
| Add New Post /wp-admin/post-new.php | 6.12 ▲0.24 | 86.79 ▼5.33 |
| Media Library /wp-admin/upload.php | 3.47 ▲0.24 | 38.33 ▲1.14 |
| Reports /wp-admin/index.php?page=wp_client_reports | 3.44 | 33.67 |
| WP Client Reports /wp-admin/options-general.php?page=wp_client_reports | 3.44 | 35.34 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 10 new files
Database: 1 new table, 9 new options
| New tables |
|---|
| wp_update_tracking |
| New WordPress options |
|---|
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
| wp_client_reports_enable_content_stats |
| wp_client_reports_enable_updates |
| wp_client_reports_version |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP Client Reports
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,873 ▲111 | 14.63 ▼0.08 | 1.63 ▼0.13 | 31.30 ▼12.37 |
| Dashboard /wp-admin | 2,281 ▲100 | 5.63 ▼0.04 | 92.49 ▼18.76 | 42.42 ▼1.45 |
| Posts /wp-admin/edit.php | 2,107 ▲4 | 1.97 ▼0.04 | 38.63 ▼2.75 | 34.57 ▼12.43 |
| Add New Post /wp-admin/post-new.php | 1,534 ▲8 | 23.21 ▲0.27 | 694.19 ▲79.85 | 51.92 ▼0.05 |
| Media Library /wp-admin/upload.php | 1,413 ▲10 | 4.18 ▼0.02 | 96.31 ▼3.61 | 40.13 ▼1.28 |
| Reports /wp-admin/index.php?page=wp_client_reports | 1,516 | 2.23 | 53.15 | 43.01 |
| WP Client Reports /wp-admin/options-general.php?page=wp_client_reports | 1,105 | 2.23 | 35.16 | 26.60 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- The plugin did not uninstall successfully, leaving 1 table in the database
- wp_update_tracking
- Zombie WordPress options detected upon uninstall: 9 options
- wp_client_reports_enable_content_stats
- widget_recent-posts
- widget_recent-comments
- wp_client_reports_enable_updates
- can_compress_scripts
- wp_client_reports_version
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
Smoke tests 50% 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 0% 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
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/wp-client-reports/email/report-email-header.php
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_plugin_active() in wp-content/plugins/wp-client-reports/email/report-email-footer.php:19
- > 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 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Screenshots: Please describe screenshot #5 in wp-client-reports/assets to your readme.txt
wp-client-reports/wp_client_reports.php 92% from 13 tests
"WP Client Reports" version 1.0.21's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("wp-client-reports.php" instead of "wp_client_reports.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Everything looks great! No dangerous files found in this plugin6,653 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 783 | 347 | 4,874 |
| PHP | 3 | 296 | 191 | 1,274 |
| CSS | 1 | 14 | 12 | 505 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.23 |
| 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 | 50 | |
| ▷ Named functions | 50 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
There were not PNG files found in your plugin