Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.03MB] [CPU: ▼2.41ms] Passed 4 tests
A check of server-side resources used by Pic Ignite
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 35.71 ▼5.88 |
| Dashboard /wp-admin | 3.34 ▲0.04 | 44.99 ▼8.28 |
| Posts /wp-admin/edit.php | 3.39 ▲0.04 | 49.61 ▲5.14 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 94.10 ▲2.22 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 35.08 ▲2.30 |
Server storage [IO: ▲0.57MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| can_compress_scripts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Pic Ignite
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲80 | 13.23 ▼1.23 | 1.89 ▼0.04 | 41.50 ▼12.58 |
| Dashboard /wp-admin | 2,224 ▲36 | 4.90 ▼0.91 | 100.96 ▼19.12 | 70.49 ▲16.42 |
| Posts /wp-admin/edit.php | 2,107 ▲18 | 2.01 ▲0.01 | 41.13 ▲3.56 | 34.34 ▼0.43 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲22 | 23.21 ▲5.54 | 698.18 ▲97.66 | 52.77 ▼7.94 |
| Media Library /wp-admin/upload.php | 1,400 ▲12 | 4.16 ▼0.07 | 100.45 ▼3.74 | 74.95 ▲28.62 |
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
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
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 | 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
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/picignite/picignite.php:91
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need your attention:
- Screenshots: Screenshot #2 (Examples of links in your content) image not found
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== picignite ===)
picignite/picignite.php 92% from 13 tests
The primary PHP file in "Pic Ignite" version 0.5 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Description: Keep the plugin description shorter than 140 characters (currently 164 characters long)
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
No dangerous file extensions were detected170 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 2 | 8 | 170 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.20 |
| 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 | 5 | |
| ▷ Named functions | 5 | 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 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
2 PNG files occupy 0.56MB with 0.43MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 571.16KB | 182.25KB | ▼ 68.09% |
| images/logo_pi.png | 4.18KB | 0.61KB | ▼ 85.38% |