Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼302.18ms] Passed 4 tests
An overview of server-side resources used by Inpsyde AntiSpam
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.59 ▲0.07 | 55.27 ▲4.02 |
Dashboard /wp-admin | 3.50 ▲0.08 | 34.82 ▲1.09 |
Posts /wp-admin/edit.php | 3.72 ▲0.08 | 38.15 ▼0.46 |
Add New Post /wp-admin/post-new.php | 6.96 ▼0.02 | 93.47 ▼1,209.90 |
Media Library /wp-admin/upload.php | 3.37 ▲0.07 | 26.00 ▲0.57 |
Antispam /wp-admin/options-general.php?page=inpsyde-antispam-page | 3.32 | 22.62 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 13 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Inpsyde AntiSpam
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,803 ▲49 | 15.85 ▼0.06 | 7.39 ▲0.81 | 2.64 ▼0.03 |
Dashboard /wp-admin | 2,897 ▲43 | 6.21 ▲0.02 | 117.36 ▼28.69 | 162.09 ▼10.36 |
Posts /wp-admin/edit.php | 2,696 ▲2 | 3.24 ▼0.00 | 66.45 ▲3.29 | 138.25 ▼4.52 |
Add New Post /wp-admin/post-new.php | 1,714 ▼38 | 20.79 ▼0.09 | 459.79 ▲14.40 | 158.70 ▼1.69 |
Media Library /wp-admin/upload.php | 1,703 ▲8 | 5.53 ▲0.00 | 146.74 ▲2.90 | 188.94 ▼1.02 |
Antispam /wp-admin/options-general.php?page=inpsyde-antispam-page | 1,146 | 2.40 | 55.41 | 126.57 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The plugin uninstalled successfully, without leaving any zombie files or tables
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These errors were triggered by the plugin
- > GET request to /wp-admin/options-general.php?page=inpsyde-antispam-page
- > User deprecated in wp-includes/functions.php+5326
screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=inpsyde-antispam-page
- > User deprecated in wp-includes/functions.php+5326
get_screen_icon is deprecated since version 3.8.0 with no alternative available.
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 take a closer look at the following
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function Inpsyde\\Antispam\\is_admin() in wp-content/plugins/js-antispam/antispam.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function Inpsyde\\Antispam\\is_admin() in wp-content/plugins/js-antispam/antispam.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that need to be fixed:
- Donate link: Invalid URI ("")
js-antispam/inpsyde-antispam.php 85% from 13 tests
The entry point to "Inpsyde AntiSpam" version 2.1.3 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("js-antispam.php" instead of "inpsyde-antispam.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Everything looks great! No dangerous files found in this plugin435 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 75 | 160 | 316 |
PO File | 1 | 23 | 50 | 66 |
Markdown | 1 | 17 | 0 | 38 |
JavaScript | 4 | 7 | 13 | 15 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
Average class complexity | 6.00 |
▷ Minimum class complexity | 6.00 |
▷ Maximum class complexity | 6.00 |
Average method complexity | 1.20 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 2.00 |
Code structure | ||
---|---|---|
Namespaces | 2 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 6 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 6 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 20 | |
▷ Named functions | 12 | 60.00% |
▷ Anonymous functions | 8 | 40.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
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