Benchmarks
Plugin footprint 23% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The following installer errors require your attention
- Install procedure validation failed for this plugin
- > Notice in wp-content/plugins/word-freshener/word-freshener.php+45
Trying to access array offset on value of type bool
Server metrics [RAM: ▼1.89MB] [CPU: ▼53.54ms] Passed 4 tests
Analyzing server-side resources used by Word Freshener
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.10 ▼1.36 | 5.72 ▼29.73 |
| Dashboard /wp-admin | 2.12 ▼1.19 | 7.48 ▼39.81 |
| Posts /wp-admin/edit.php | 2.12 ▼1.24 | 6.92 ▼46.19 |
| Add New Post /wp-admin/post-new.php | 2.12 ▼3.77 | 6.29 ▼96.76 |
| Media Library /wp-admin/upload.php | 2.12 ▼1.11 | 6.10 ▼31.41 |
| Add Words /wp-admin/admin.php?page=wfps_add | 2.12 | 6.32 |
| Word Freshener /wp-admin/admin.php?page=wfps-main | 2.12 | 7.45 |
| Settings /wp-admin/admin.php?page=wfps_settings | 2.12 | 6.62 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 5 new files
Database: 1 new table, 6 new options
| New tables |
|---|
| wp_wfp |
| New WordPress options |
|---|
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Word Freshener
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,826 ▲91 | 13.62 ▼0.75 | 1.76 ▲0.01 | 44.29 ▲5.96 |
| Dashboard /wp-admin | 2,235 ▲53 | 5.84 ▲0.96 | 100.15 ▼3.53 | 79.64 ▲35.05 |
| Posts /wp-admin/edit.php | 2,118 ▲26 | 2.02 ▼0.15 | 37.24 ▼5.85 | 34.97 ▲0.23 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲15 | 23.25 ▼0.02 | 708.33 ▲8.00 | 52.85 ▼2.16 |
| Media Library /wp-admin/upload.php | 1,414 ▲26 | 4.25 ▲0.12 | 110.76 ▼3.26 | 45.14 ▼3.02 |
| Add Words /wp-admin/admin.php?page=wfps_add | 832 | 2.05 | 24.51 | 24.74 |
| Word Freshener /wp-admin/admin.php?page=wfps-main | 2,857 | 1.69 | 27.78 | 38.77 |
| Settings /wp-admin/admin.php?page=wfps_settings | 818 | 2.02 | 26.20 | 26.27 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 25% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- Uninstall procedure had uncaught errors
- > Notice in wp-content/plugins/word-freshener/word-freshener.php+45
Trying to access array offset on value of type bool
- The uninstall procedure failed, leaving 1 table in the database
- wp_wfp
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
These errors were triggered by the plugin
- 12 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wfps_settings
- > Notice in wp-content/plugins/word-freshener/dashboard.php+204
Trying to access array offset on value of type bool
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/word-freshener/word-freshener.php:12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser 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:
- Tags: Too many tags (11 tag instead of maximum 10); only the first 5 tags are used in your directory listing
word-freshener/word-freshener.php Passed 13 tests
The entry point to "Word Freshener" version 1.3 is a PHP file that has certain tags in its header comment area
129 characters long description:
A simple plugin to filter commonly used unwanted and bad words from anywhere in your site. Replace words with full customization.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin294 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 48 | 54 | 294 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.26 |
| 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 | 8 | |
| ▷ Named functions | 8 | 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
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 |
| image/wf-logo.png | 2.23KB | 1.18KB | ▼ 46.97% |