Benchmarks
Plugin footprint 65% 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 successfully, without throwing any errors or notices
Server metrics [RAM: ▼1.96MB] [CPU: ▼61.28ms] Passed 4 tests
A check of server-side resources used by Ajaxify-Comments
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.04 ▼1.42 | 4.59 ▼41.45 |
| Dashboard /wp-admin | 2.06 ▼1.28 | 5.09 ▼59.71 |
| Posts /wp-admin/edit.php | 2.06 ▼1.29 | 5.31 ▼44.98 |
| Add New Post /wp-admin/post-new.php | 2.06 ▼3.83 | 5.24 ▼98.99 |
| Media Library /wp-admin/upload.php | 2.06 ▼1.17 | 4.95 ▼32.57 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Ajaxify-Comments
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,874 ▲88 | 13.47 ▼0.91 | 9.15 ▲6.83 | 41.70 ▼5.91 |
| Dashboard /wp-admin | 2,197 ▲20 | 5.70 ▲0.00 | 96.09 ▼12.57 | 42.73 ▲0.94 |
| Posts /wp-admin/edit.php | 2,102 ▲2 | 2.05 ▲0.02 | 40.74 ▲4.16 | 34.59 ▲1.41 |
| Add New Post /wp-admin/post-new.php | 1,551 ▲20 | 18.37 ▼4.94 | 597.21 ▼74.69 | 53.36 ▼0.48 |
| Media Library /wp-admin/upload.php | 1,402 ▲5 | 4.42 ▲0.22 | 107.27 ▼1.14 | 49.45 ▲2.08 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- The plugin did not uninstall gracefully
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_enqueue_script() in wp-content/plugins/ajaxify-comments/ajaxify-comments.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
2 plugin tags: ajaxify comment form, ajaxify comments pagination
ajaxify-comments/ajaxify-comments.php 92% from 13 tests
The entry point to "Ajaxify-Comments" version 1.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Description: Please don't use more than 140 characters for the plugin description (currently 167 characters long)
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
No dangerous file extensions were detected72 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 1 | 11 | 2 | 67 |
| PHP | 1 | 2 | 6 | 5 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.00 |
| 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 | 0 | |
| ▷ Named functions | 0 | 0.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
No PNG files were detected