Benchmarks
Plugin footprint 48% 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.93MB] [CPU: ▼29.32ms] Passed 4 tests
Server-side resources used by Stopwords for comments
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.03 | 37.67 ▼3.26 |
| Dashboard /wp-admin | 3.02 ▼0.29 | 26.24 ▼22.16 |
| Posts /wp-admin/edit.php | 3.02 ▼0.34 | 25.80 ▼21.10 |
| Add New Post /wp-admin/post-new.php | 3.02 ▼2.87 | 22.68 ▼64.91 |
| Media Library /wp-admin/upload.php | 3.02 ▼0.21 | 23.37 ▼9.12 |
| Stopwords for comments /wp-admin/edit-comments.php?page=stopwords-for-comments/index.php | 3.07 | 23.13 |
| All Comments /wp-admin/edit-comments.php | 3.07 | 23.40 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 7 new files
Database: 1 new table, 6 new options
| New tables |
|---|
| wp_stopwords_for_comments |
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by Stopwords for comments
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,822 ▲76 | 13.30 ▼1.00 | 1.59 ▼0.47 | 41.50 ▼1.65 |
| Dashboard /wp-admin | 2,228 ▲40 | 4.88 ▼0.02 | 110.64 ▲6.79 | 42.42 ▼1.41 |
| Posts /wp-admin/edit.php | 2,114 ▲25 | 2.03 ▼0.02 | 42.05 ▲2.26 | 35.42 ▼1.71 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲22 | 23.42 ▲5.82 | 659.88 ▼7.14 | 46.15 ▼9.20 |
| Media Library /wp-admin/upload.php | 1,410 ▲19 | 4.24 ▲0.03 | 97.11 ▼3.08 | 43.72 ▲0.02 |
| Stopwords for comments /wp-admin/edit-comments.php?page=stopwords-for-comments/index.php | 807 | 2.09 | 28.60 | 34.16 |
| All Comments /wp-admin/edit-comments.php | 1,818 | 2.38 | 44.43 | 31.43 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 25% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- Uninstall procedure had uncaught errors
- > User notice in wp-includes/functions.php+5905
Function add_submenu_page was called incorrectly. The seventh parameter passed to add_submenu_page() should be numeric representing menu position. Please see Debugging in WordPress for more information. (This message was added in version 5.3.0.)
- Zombie tables were found after uninstall: 1 table
- wp_stopwords_for_comments
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
Smoke tests 0% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
These server-side errors were triggered
- 2 occurences, only the last one shown
- > GET request to /wp-admin/edit-comments.php
- > User notice in wp-includes/functions.php+5905
Function add_submenu_page was called incorrectly. The seventh parameter passed to add_submenu_page() should be numeric representing menu position. Please see Debugging in WordPress for more information. (This message was added in version 5.3.0.)
SRP 0% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following items
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/stopwords-for-comments/index.php
- 3× PHP files trigger server errors when accessed directly:
- > PHP Warning
require_once(ABSPATHwp-admin/includes/post.php): failed to open stream: No such file or directory in wp-content/plugins/stopwords-for-comments/functions.php on line 18
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/stopwords-for-comments/functions.php on line 18
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/post.php' (include_path='.:/usr/share/php') in wp-content/plugins/stopwords-for-comments/functions.php on line 18
- > PHP Warning
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Please fix the following user-side errors
- > GET request to /wp-admin/edit-comments.php?page=stopwords-for-comments/index.php
- > Network (severe)
https://okuke73wiq.a.trbcdn.net/l.woff2 - Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
3 plugin tags: wordpress, stopwords, comment
stopwords-for-comments/functions.php 92% from 13 tests
The main PHP file in "Stopwords for comments" ver. 1.1 adds more information about the plugin and also serves as the entry point for this plugin
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("stopwords-for-comments.php" instead of "functions.php")
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
No dangerous file extensions were detected335 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 1 | 40 | 0 | 166 |
| PHP | 2 | 113 | 27 | 120 |
| JavaScript | 1 | 26 | 9 | 49 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.13 |
| 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 | 11 | |
| ▷ Named functions | 11 | 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
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.06MB with 0.03MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| cover.png | 56.76KB | 24.84KB | ▼ 56.23% |