Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
It is recommended to fix the following installer errors
- Install procedure had errors
- > User notice in wp-includes/functions.php+5905
Function register_uninstall_hook was called incorrectly. Only a static class method or function can be used in an uninstall hook. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.)
Server metrics [RAM: ▼1.90MB] [CPU: ▼59.19ms] Passed 4 tests
An overview of server-side resources used by WP Fading Content Slider
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.10 ▼1.36 | 5.13 ▼36.65 |
| Dashboard /wp-admin | 2.12 ▼1.23 | 6.62 ▼58.52 |
| Posts /wp-admin/edit.php | 2.12 ▼1.24 | 5.81 ▼47.02 |
| Add New Post /wp-admin/post-new.php | 2.12 ▼3.77 | 5.38 ▼94.55 |
| Media Library /wp-admin/upload.php | 2.12 ▼1.11 | 6.56 ▼30.74 |
| WP Fading Content Slider /wp-admin/options-general.php?page=wp-fading-content-slider/views/admin.php | 2.12 | 5.77 |
Server storage [IO: ▲0.35MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 15 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Fading Content Slider
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,904 ▲143 | 13.64 ▼0.67 | 5.92 ▲3.85 | 43.03 ▼2.51 |
| Dashboard /wp-admin | 2,224 ▲24 | 5.80 ▼0.07 | 100.78 ▼3.54 | 38.13 ▼3.02 |
| Posts /wp-admin/edit.php | 2,103 ▲3 | 2.05 ▲0.03 | 37.16 ▼6.67 | 32.37 ▼6.11 |
| Add New Post /wp-admin/post-new.php | 6,247 ▲4,716 | 19.27 ▼3.91 | 848.27 ▲155.98 | 57.01 ▲0.70 |
| Media Library /wp-admin/upload.php | 1,409 ▲12 | 4.32 ▲0.08 | 100.39 ▼3.75 | 46.50 ▲0.44 |
| WP Fading Content Slider /wp-admin/options-general.php?page=wp-fading-content-slider/views/admin.php | 1,074 | 2.15 | 24.71 | 33.03 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- The plugin did not uninstall gracefully
- > User notice in wp-includes/functions.php+5905
Function register_uninstall_hook was called incorrectly. Only a static class method or function can be used in an uninstall hook. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.)
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Almost there, just fix the following server-side errors
- > GET request to /wp-admin/options-general.php?page=wp-fading-content-slider/views/admin.php
- > User notice in wp-includes/functions.php+5905
Function register_uninstall_hook was called incorrectly. Only a static class method or function can be used in an uninstall hook. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=wp-fading-content-slider/views/admin.php
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- > GET request to /wp-admin/options-general.php?page=wp-fading-content-slider/views/admin.php
- > Notice in wp-content/plugins/wp-fading-content-slider/views/admin.php+2
Undefined variable: options_page
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
The following issues need your attention
- 3× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/wp-fading-content-slider/views/admin.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-fading-content-slider/wp-fading-content-slider.php:25
- > PHP Notice
Undefined variable: options_page in wp-content/plugins/wp-fading-content-slider/views/admin.php on line 2
- > 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
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: Add images for these screenshots: #1 (The slider displayed on [MBA Multimedia's blog](http://blog.mba-multimedia.com/)), #2 (The new box in the post/page edit screen), #3 (The plugin admin panel)
wp-fading-content-slider/wp-fading-content-slider.php Passed 13 tests
The primary PHP file in "WP Fading Content Slider" version 0.2.2 is used by WordPress to initiate all plugin functionality
76 characters long description:
A customizable JQuery content slider with CSS3 animations and fading effects
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected733 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 83 | 93 | 375 |
| CSS | 2 | 45 | 19 | 255 |
| PO File | 1 | 34 | 35 | 98 |
| JavaScript | 1 | 0 | 1 | 5 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.23 |
| Average class complexity | 22.00 |
| ▷ Minimum class complexity | 22.00 |
| ▷ Maximum class complexity | 22.00 |
| Average method complexity | 2.24 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 17.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 | 17 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 17 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
4 PNG files occupy 0.30MB with 0.12MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 24.38KB | 9.05KB | ▼ 62.86% |
| images/sprite.png | 2.71KB | 1.71KB | ▼ 36.87% |
| screenshot-3.png | 134.70KB | 48.97KB | ▼ 63.65% |
| screenshot-1.png | 150.44KB | 149.67KB | ▼ 0.51% |