Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.03MB] [CPU: ▼9.68ms] Passed 4 tests
A check of server-side resources used by Show Next Upcoming Post
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 37.88 ▼5.24 |
| Dashboard /wp-admin | 3.33 ▼0.01 | 41.33 ▼21.01 |
| Posts /wp-admin/edit.php | 3.46 ▲0.11 | 45.95 ▼0.82 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 84.02 ▼11.66 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.05 | 34.84 ▲1.10 |
Server storage [IO: ▲1.77MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 25 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_snup_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
Show Next Upcoming Post: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,845 ▲99 | 13.33 ▼0.96 | 1.69 ▼0.22 | 40.84 ▼2.18 |
| Dashboard /wp-admin | 2,249 ▲61 | 4.88 ▼1.02 | 105.63 ▼8.52 | 42.55 ▲0.10 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 1.97 ▼0.02 | 40.38 ▲4.58 | 33.97 ▲0.05 |
| Add New Post /wp-admin/post-new.php | 6,257 ▲4,738 | 18.70 ▼4.59 | 901.09 ▲197.33 | 66.13 ▲0.14 |
| Media Library /wp-admin/upload.php | 1,382 ▼3 | 4.24 ▲0.04 | 101.54 ▲0.10 | 44.38 ▼0.11 |
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
- This plugin did not uninstall successfully, leaving 7 options in the database
- db_upgraded
- widget_snup_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
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
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/show-next-upcoming-post-snup-widget/snup-widget.php:48
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
4 plugin tags: preview, post, next, upcoming
show-next-upcoming-post-snup-widget/snup-widget.php 85% from 13 tests
Analyzing the main PHP file in "Show Next Upcoming Post" version 1.3.1
Please take the time to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: Name the main plugin file the same as the plugin slug ("show-next-upcoming-post-snup-widget.php" instead of "snup-widget.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected5,741 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| HTML | 1 | 435 | 3 | 5,326 |
| PO File | 4 | 62 | 62 | 208 |
| PHP | 2 | 102 | 87 | 194 |
| CSS | 1 | 3 | 0 | 13 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.21 |
| Average class complexity | 4.00 |
| ▷ Minimum class complexity | 4.00 |
| ▷ Maximum class complexity | 4.00 |
| Average method complexity | 1.75 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.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 | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 11 | |
| ▷ Named functions | 11 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
6 PNG files occupy 0.71MB with 0.44MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/banner-1544x500-rtl.png | 262.95KB | 106.11KB | ▼ 59.64% |
| assets/images/icon-128x128.png | 7.34KB | 2.64KB | ▼ 64.10% |
| assets/images/icon-256x256.png | 12.56KB | 4.51KB | ▼ 64.10% |
| assets/images/banner-1544x500.png | 262.95KB | 106.11KB | ▼ 59.64% |
| assets/images/banner-772x250-rtl.png | 90.70KB | 32.37KB | ▼ 64.31% |