Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.68ms] Passed 4 tests
Server-side resources used by TKC Sliced Post Helper
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 37.42 ▼3.27 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 49.35 ▼0.33 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.26 ▼0.10 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 85.76 ▼11.00 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 38.95 ▲4.43 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
TKC Sliced Post Helper: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲53 | 14.64 ▲0.25 | 2.13 ▲0.34 | 44.49 ▼4.97 |
| Dashboard /wp-admin | 2,195 ▲21 | 5.62 ▼0.09 | 83.98 ▼12.28 | 39.94 ▲0.62 |
| Posts /wp-admin/edit.php | 2,097 ▼3 | 2.05 ▼0.00 | 37.39 ▼4.82 | 36.70 ▼1.97 |
| Add New Post /wp-admin/post-new.php | 1,545 ▼0 | 23.34 ▲0.34 | 664.79 ▲46.07 | 57.26 ▲8.39 |
| Media Library /wp-admin/upload.php | 1,397 ▼0 | 4.22 ▼0.06 | 100.68 ▼6.54 | 45.87 ▼2.75 |
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
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
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)
The smoke test was a success, however most plugin functionality was not tested
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
Almost there! Just fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/tkc-sliced-post/tkc-sliced-post.php:17
- > 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 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== tkc-sliced-post ===) - Screenshots: A description for screenshot #1 is missing in tkc-sliced-post/assets to your readme.txt
tkc-sliced-post/tkc-sliced-post.php 92% from 13 tests
The main PHP script in "TKC Sliced Post Helper" version 1.0.0 is automatically included on every request by WordPress
The following require your attention:
- 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
No dangerous file extensions were detected29 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 1 | 1 | 0 | 15 |
| PHP | 1 | 4 | 12 | 14 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.00 |
| 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 | 3 | |
| ▷ Named functions | 3 | 100.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 PNG files occupy 0.06MB with 0.02MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 59.94KB | 26.81KB | ▼ 55.28% |
| tkc-sliced-post.png | 0.28KB | 0.29KB | 0.00% |