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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.02MB] [CPU: ▼0.92ms] Passed 4 tests
An overview of server-side resources used by Pay to Comment with Lightning
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 35.21 ▼6.39 |
Dashboard /wp-admin | 3.32 ▲0.02 | 44.37 ▼0.02 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 47.71 ▲3.20 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 85.35 ▼0.45 |
Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 38.27 ▲6.84 |
Pay to Comment with Lightning /wp-admin/options-general.php?page=lightning_comments | 3.19 | 27.94 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-posts |
db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Pay to Comment with Lightning
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,835 ▲78 | 13.69 ▼0.71 | 2.63 ▲0.54 | 41.49 ▼6.94 |
Dashboard /wp-admin | 2,210 ▲55 | 5.91 ▲0.30 | 102.44 ▼2.67 | 37.48 ▼1.24 |
Posts /wp-admin/edit.php | 2,096 ▲7 | 2.03 ▲0.02 | 38.94 ▲3.49 | 34.63 ▼4.61 |
Add New Post /wp-admin/post-new.php | 1,536 ▲22 | 23.10 ▲5.45 | 658.00 ▲63.83 | 51.56 ▲2.47 |
Media Library /wp-admin/upload.php | 1,389 ▲1 | 4.20 ▲0.00 | 98.50 ▼0.41 | 44.76 ▲1.22 |
Pay to Comment with Lightning /wp-admin/options-general.php?page=lightning_comments | 836 | 2.03 | 24.43 | 26.16 |
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
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These server-side errors were triggered
- 6 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=lightning_comments
- > Notice in wp-content/plugins/wp-lightning-comments/lightningcomments.php+270
Trying to access array offset on value of type bool
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-lightning-comments/lightningcomments.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need to be fixed:
- Donate link: Please fix this invalid URI: ""
wp-lightning-comments/lightningcomments.php 92% from 13 tests
The main file in "Pay to Comment with Lightning" v. 0.2.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("wp-lightning-comments.php" instead of "lightningcomments.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin466 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 46 | 22 | 229 |
JavaScript | 2 | 33 | 47 | 193 |
CSS | 1 | 2 | 3 | 30 |
Markdown | 1 | 3 | 0 | 14 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.16 |
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 | 18 | |
▷ Named functions | 17 | 94.44% |
▷ Anonymous functions | 1 | 5.56% |
Constants | 2 | |
▷ Global constants | 2 | 100.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
There are no PNG files in this plugin