Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼7.09ms] 75% from 4 tests
This is a short check of server-side resources used by WebPurify Profanity Filter
The following require your attention
- CPU: Total CPU usage must kept under 500.00ms (currently 610.06ms on /wp-admin/options-general.php?page=webpurify-options)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 41.54 ▲2.62 |
Dashboard /wp-admin | 3.37 ▲0.03 | 47.55 ▼16.19 |
Posts /wp-admin/edit.php | 3.48 ▲0.13 | 51.22 ▲0.41 |
Add New Post /wp-admin/post-new.php | 5.97 ▲0.09 | 88.88 ▼12.08 |
Media Library /wp-admin/upload.php | 3.29 ▲0.07 | 39.81 ▼0.51 |
WebPurify /wp-admin/options-general.php?page=webpurify-options | 3.27 | 610.06 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for WebPurify Profanity Filter
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲58 | 13.56 ▼1.02 | 1.94 ▲0.03 | 42.57 ▼2.67 |
Dashboard /wp-admin | 2,213 ▲25 | 5.85 ▼0.04 | 102.31 ▼15.07 | 39.10 ▼3.81 |
Posts /wp-admin/edit.php | 2,090 ▲1 | 1.99 ▼0.02 | 37.29 ▼0.23 | 35.43 ▲2.05 |
Add New Post /wp-admin/post-new.php | 1,534 ▲20 | 23.21 ▲5.60 | 619.29 ▼63.43 | 55.65 ▼0.68 |
Media Library /wp-admin/upload.php | 1,389 ▲4 | 4.26 ▼0.04 | 103.67 ▼0.59 | 43.91 ▲0.62 |
WebPurify /wp-admin/options-general.php?page=webpurify-options | 998 | 2.07 | 24.28 | 30.45 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These server-side errors were triggered
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=webpurify-options
- > Notice in wp-content/plugins/webpurifytextreplace/webpurify-api.php+272
Undefined property: stdClass::$word
SRP Passed 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
Congratulations! This plugin passed the SRP test
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 93% from 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
9 plugin tags: filter, comments, profanity, bbpress, swearing...
webpurifytextreplace/webpurifytextreplace-options.php 85% from 13 tests
The principal PHP file in "WebPurify Profanity Filter" v. 4.0.2 is loaded by WordPress automatically on each request
The following require your attention:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("webpurifytextreplace.php" instead of "webpurifytextreplace-options.php")
- Text Domain: The text domain name should consist of only dashes and lowercase characters
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 detected607 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 178 | 267 | 473 |
JavaScript | 4 | 42 | 35 | 69 |
Markdown | 1 | 25 | 0 | 65 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
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 | 26 | |
▷ Named functions | 26 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
There are no PNG files in this plugin