Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.12ms] Passed 4 tests
This is a short check of server-side resources used by Post Cloner
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 37.80 ▲3.21 |
Dashboard /wp-admin | 3.32 ▼0.02 | 49.18 ▼11.96 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 46.63 ▲4.64 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 90.70 ▼2.63 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.58 ▲2.89 |
WP Post Cloner /wp-admin/options-general.php?page=wp-post-cloner-settings | 3.24 | 29.52 |
Server storage [IO: ▲0.12MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
Post Cloner: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,829 ▲83 | 13.67 ▼0.72 | 5.16 ▲3.52 | 39.37 ▼1.28 |
Dashboard /wp-admin | 2,207 ▲16 | 5.80 ▲0.95 | 96.10 ▼4.94 | 37.90 ▼0.26 |
Posts /wp-admin/edit.php | 2,097 ▲11 | 1.99 ▼0.06 | 39.53 ▲4.33 | 35.19 ▼0.49 |
Add New Post /wp-admin/post-new.php | 1,545 ▲11 | 18.30 ▼4.88 | 586.78 ▼77.55 | 47.78 ▼10.02 |
Media Library /wp-admin/upload.php | 1,392 ▲7 | 4.21 ▲0.02 | 92.79 ▼5.64 | 41.73 ▼4.48 |
WP Post Cloner /wp-admin/options-general.php?page=wp-post-cloner-settings | 933 | 2.01 | 37.16 | 32.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- 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)
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/post-cloner/wp-post-cloner.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function current_user_can() in wp-content/plugins/post-cloner/includes/wp-post-duplicator-settings.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
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
Attributes that require attention:
- Tags: You are using too many tags: 24 tag instead of maximum 10
post-cloner/wp-post-cloner.php 92% from 13 tests
The main file in "Post Cloner" v. 0.1.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("post-cloner.php" instead of "wp-post-cloner.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected782 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 1 | 125 | 26 | 557 |
PHP | 2 | 36 | 77 | 196 |
Markdown | 1 | 16 | 0 | 21 |
JavaScript | 2 | 5 | 15 | 8 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.44 |
Average class complexity | 28.00 |
▷ Minimum class complexity | 28.00 |
▷ Maximum class complexity | 28.00 |
Average method complexity | 3.70 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 16.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 | 10 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 10 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
2 compressed PNG files occupy 0.00MB
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
includes/css/select2.png | 0.60KB | 0.99KB | 0.00% |
includes/css/select2x2.png | 0.83KB | 0.77KB | ▼ 6.15% |