Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▼0.90MB] [CPU: ▼29.35ms] Passed 4 tests
An overview of server-side resources used by ReplyToCom Ajaxify
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 43.09 ▼0.33 |
| Dashboard /wp-admin | 3.05 ▼0.26 | 21.63 ▼22.44 |
| Posts /wp-admin/edit.php | 3.05 ▼0.31 | 24.91 ▼21.06 |
| Add New Post /wp-admin/post-new.php | 3.05 ▼2.84 | 24.79 ▼64.46 |
| Media Library /wp-admin/upload.php | 3.05 ▼0.19 | 22.63 ▼9.45 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for ReplyToCom Ajaxify
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,887 ▲152 | 13.62 ▼0.98 | 5.46 ▲3.75 | 41.41 ▲0.42 |
| Dashboard /wp-admin | 2,210 ▲19 | 5.85 ▼0.05 | 108.28 ▲1.51 | 43.72 ▼1.19 |
| Posts /wp-admin/edit.php | 2,096 ▲4 | 2.02 ▲0.00 | 39.31 ▼2.92 | 34.82 ▼5.26 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲3 | 18.44 ▼0.04 | 595.40 ▼47.31 | 55.34 ▲6.55 |
| Media Library /wp-admin/upload.php | 1,392 ▲7 | 4.38 ▲0.21 | 94.69 ▼9.35 | 41.47 ▼5.39 |
| ReplyToCom Ajaxify /wp-admin/replytocom.php | 26 | 0.44 | 0.10 | 13.92 |
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
These items require your attention
- This plugin cannot be uninstalled
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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 errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/replytocom-ajaxify/replytocom.php:28
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
These are user-side errors you should fix
- > GET request to /wp-admin/replytocom.php
- > Network (severe)
wp-admin/replytocom.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
2 plugin tags: seo, replytocom
replytocom-ajaxify/replytocom.php 92% from 13 tests
The main PHP file in "ReplyToCom Ajaxify" ver. 1.0.3 adds more information about the plugin and also serves as the entry point for this plugin
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("replytocom-ajaxify.php" instead of "replytocom.php")
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
Everything looks great! No dangerous files found in this plugin399 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 48 | 9 | 299 |
| JavaScript | 1 | 39 | 0 | 100 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.50 |
| Average class complexity | 59.00 |
| ▷ Minimum class complexity | 59.00 |
| ▷ Maximum class complexity | 59.00 |
| Average method complexity | 4.41 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 15.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 | 17 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 17 | 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 | 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
There are no PNG files in this plugin