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: ▼7.92ms] Passed 4 tests
Server-side resources used by Jelly: A Simple Responsive Slideshow
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.03 | 40.55 ▲1.62 |
| Dashboard /wp-admin | 3.35 ▼0.00 | 42.17 ▼19.18 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 44.78 ▼3.40 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 80.82 ▼10.70 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 35.93 ▲2.64 |
| Jelly Settings /wp-admin/options-general.php?page=jelly_settings | 3.27 | 34.98 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Jelly: A Simple Responsive Slideshow
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,793 ▲32 | 14.40 ▼0.16 | 1.62 ▼0.05 | 43.34 ▲1.87 |
| Dashboard /wp-admin | 2,202 ▲25 | 5.64 ▲0.08 | 90.52 ▲3.62 | 40.56 ▼1.78 |
| Posts /wp-admin/edit.php | 2,101 ▲1 | 1.96 ▼0.04 | 38.93 ▲2.89 | 36.05 ▼0.18 |
| Add New Post /wp-admin/post-new.php | 1,540 ▲12 | 18.36 ▼4.75 | 614.82 ▼65.52 | 64.69 ▼2.22 |
| Media Library /wp-admin/upload.php | 1,407 ▲7 | 4.18 ▲0.02 | 103.46 ▲2.83 | 44.27 ▼2.99 |
| Jelly Settings /wp-admin/options-general.php?page=jelly_settings | 1,000 | 3.02 | 38.48 | 25.91 |
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
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
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 applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/jelly/jelly.php:37
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
10 plugin tags: gallery, slide show, responsive, slideshow, javascript...
jelly/jelly.php Passed 13 tests
This is the main PHP file of "Jelly: A Simple Responsive Slideshow" version 1.2, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
42 characters long description:
Slideshow designed and developed by Lumne.
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
Good job! No executable or dangerous file extensions detected286 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 37 | 32 | 136 |
| JavaScript | 2 | 50 | 11 | 94 |
| CSS | 2 | 11 | 1 | 56 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.21 |
| 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 | 12 | |
| ▷ Named functions | 12 | 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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/delete.png | 1.38KB | 0.71KB | ▼ 48.52% |