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 gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.90ms] Passed 4 tests
This is a short check of server-side resources used by Nirror
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 32.56 ▼7.18 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 45.74 ▼5.77 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 49.38 ▲4.83 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 84.94 ▼4.22 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 34.01 ▲1.57 |
| Nirror /wp-admin/options-general.php?page=nirror | 3.21 | 30.12 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 6 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| nirror_site_id |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Nirror
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,833 ▲76 | 13.23 ▼1.02 | 2.39 ▲0.21 | 41.25 ▼1.56 |
| Dashboard /wp-admin | 2,207 ▲22 | 5.83 ▼0.07 | 100.53 ▼12.61 | 39.06 ▼7.60 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 1.98 ▼0.06 | 39.78 ▲4.64 | 34.47 ▲0.04 |
| Add New Post /wp-admin/post-new.php | 1,536 ▼2 | 23.30 ▲0.02 | 640.80 ▲46.92 | 60.79 ▼2.18 |
| Media Library /wp-admin/upload.php | 1,392 ▲1 | 4.26 ▲0.05 | 100.54 ▲0.84 | 43.75 ▼0.27 |
| Nirror /wp-admin/options-general.php?page=nirror | 791 | 2.03 | 22.61 | 26.13 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
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 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
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 get_option() in wp-content/plugins/nirror/nirror.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_nonce_field() in wp-content/plugins/nirror/options.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 97% 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
Attributes that require attention:
- Screenshots: These screenshots require images: #1 (Modified settings panel with Nirror.), #2 (Nirror settings page.)
nirror/nirror.php Passed 13 tests
The entry point to "Nirror" version 0.0.1 is a PHP file that has certain tags in its header comment area
28 characters long description:
Enables Nirror on all pages.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected77 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 20 | 8 | 77 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| 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 | 6 | |
| ▷ Named functions | 6 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 6.99KB | 3.39KB | ▼ 51.45% |
| screenshot-1.png | 27.36KB | 9.75KB | ▼ 64.37% |