Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼6.59ms] Passed 4 tests
Server-side resources used by SacredBits Remove Website Link Input Field From Comment Form of Post
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 35.99 ▼2.16 |
Dashboard /wp-admin | 3.31 ▼0.03 | 43.84 ▼16.46 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 44.51 ▼4.60 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 88.55 ▼3.15 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 33.02 ▲0.14 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 3 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for SacredBits Remove Website Link Input Field From Comment Form of Post
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲79 | 13.39 ▼0.95 | 4.78 ▲3.18 | 40.19 ▼1.47 |
Dashboard /wp-admin | 2,206 ▲21 | 5.85 ▼0.02 | 109.07 ▲9.37 | 41.84 ▲0.14 |
Posts /wp-admin/edit.php | 2,089 ▲18 | 2.06 ▲0.03 | 39.15 ▲4.72 | 34.67 ▼0.38 |
Add New Post /wp-admin/post-new.php | 1,542 ▲7 | 18.29 ▼4.83 | 607.10 ▼74.40 | 55.75 ▲2.74 |
Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.20 ▼0.01 | 99.59 ▼3.44 | 41.50 ▼4.64 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% 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
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 96% 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
3 plugin tags: url, wp, comment form
sacredbits-remove-website-link-input-field-from-comment-form-of-post/sacredbits-remove-website-link-input-field-from-comment-form-of-post.php 92% from 13 tests
The entry point to "SacredBits Remove Website Link Input Field From Comment Form of Post" version 1.0.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Description: Keep the plugin description shorter than 140 characters (currently 332 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Good job! No executable or dangerous file extensions detected29 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 4 | 13 | 29 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.67 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 2.00 |
Average method complexity | 1.50 |
▷ 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 | 2 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 2 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
1 PNG file occupies 0.05MB with 0.04MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshots/screenshot-1.png | 50.64KB | 14.11KB | ▼ 72.14% |