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.03MB] [CPU: ▼4.20ms] Passed 4 tests
An overview of server-side resources used by Elegant Category Posts
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.44 ▼0.03 | 24.69 ▼15.27 |
Dashboard /wp-admin | 3.36 ▲0.05 | 50.18 ▼2.57 |
Posts /wp-admin/edit.php | 3.41 ▲0.05 | 54.43 ▲1.01 |
Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 97.57 ▲1.15 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 36.63 ▲0.03 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 6 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_ecats_posts |
db_upgraded |
widget_recent-posts |
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
Elegant Category Posts: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,792 ▲31 | 14.34 ▼0.18 | 1.84 ▲0.20 | 43.12 ▲2.31 |
Dashboard /wp-admin | 2,195 ▲15 | 5.55 ▼0.01 | 94.19 ▲2.69 | 37.86 ▼3.41 |
Posts /wp-admin/edit.php | 2,100 ▼3 | 2.00 ▲0.03 | 42.87 ▼1.06 | 36.04 ▼4.49 |
Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.20 ▲0.01 | 631.77 ▼25.40 | 57.94 ▲0.60 |
Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.21 ▲0.06 | 98.33 ▼3.04 | 41.65 ▼3.83 |
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
- Zombie WordPress options detected upon uninstall: 7 options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_ecats_posts
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
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
The following issues need your attention
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/elegant-category-posts/ecat-posts.php:13
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Please fix the following attributes:
- Screenshots: Please a description for screenshot #3 in elegant-category-posts/assets to your readme.txt
elegant-category-posts/ecat-posts.php 92% from 13 tests
The primary PHP file in "Elegant Category Posts" version 1.0.2 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("elegant-category-posts.php" instead of "ecat-posts.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected191 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 22 | 11 | 173 |
Markdown | 1 | 8 | 0 | 18 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
Average class complexity | 29.00 |
▷ Minimum class complexity | 29.00 |
▷ Maximum class complexity | 29.00 |
Average method complexity | 8.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 14.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 4 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 4 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 3 | |
▷ Named functions | 1 | 33.33% |
▷ Anonymous functions | 2 | 66.67% |
Constants | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
3 PNG files occupy 0.06MB with 0.06MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
(invalid) assets/screenshot-1.png | 17.10KB | 0.00KB | ▼ 100.00% |
(invalid) assets/screenshot-2.png | 15.79KB | 0.00KB | ▼ 100.00% |
(invalid) assets/screenshot-3.png | 32.70KB | 0.00KB | ▼ 100.00% |