Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.02MB] [CPU: ▼5.60ms] Passed 4 tests
An overview of server-side resources used by DX Category Reports
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.01 | 41.28 ▼5.21 |
Dashboard /wp-admin | 3.32 ▲0.02 | 49.20 ▼3.08 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 45.91 ▼4.49 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 85.37 ▼9.63 |
Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 40.47 ▲3.54 |
DX Category Reports /wp-admin/options-general.php?page=dx-category-reports | 3.22 | 33.46 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for DX Category Reports
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲47 | 14.37 ▲0.03 | 1.74 ▼0.05 | 43.26 ▲1.37 |
Dashboard /wp-admin | 2,196 ▲38 | 5.50 ▼0.19 | 83.61 ▼18.27 | 40.15 ▼1.34 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 1.97 ▼0.04 | 34.73 ▼1.41 | 35.26 ▼3.57 |
Add New Post /wp-admin/post-new.php | 1,530 ▼5 | 23.04 ▲4.67 | 676.45 ▲19.63 | 66.00 ▼5.46 |
Media Library /wp-admin/upload.php | 1,404 ▲4 | 4.17 ▼0.01 | 96.54 ▼8.62 | 45.07 ▲1.53 |
DX Category Reports /wp-admin/options-general.php?page=dx-category-reports | 822 | 2.03 | 24.40 | 30.90 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% 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
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however 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
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/dx-category-reports/inc/templates/admin-template.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/dx-category-reports/dx-category-reports.php:41
- > 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)
No browser issues were found
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:
- Screenshots: These screenshots require images: #1 (DX Category Reports Settings page), #2 (Count of posts submitted under Post Formats over time)
dx-category-reports/dx-category-reports.php 92% from 13 tests
Analyzing the main PHP file in "DX Category Reports" version 1.0
Please take the time to fix the following:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
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
No dangerous file extensions were detected208 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 35 | 73 | 121 |
CSS | 1 | 7 | 0 | 87 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.22 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 2.00 |
Average method complexity | 1.29 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 2.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 7 | |
▷ Static methods | 3 | 42.86% |
▷ Public methods | 7 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
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-1.png | 26.12KB | 10.40KB | ▼ 60.20% |