Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
These installer errors require your attention
- The plugin cannot be installed
- > Parse error in wp-content/plugins/technoscore-login-redirection/secure-frontend-ajax-login.php+234
syntax error, unexpected end of file
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.98ms] Passed 4 tests
This is a short check of server-side resources used by Secure Frontend Ajax Login
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 35.66 ▼2.49 |
Dashboard /wp-admin | 3.31 ▲0.00 | 45.63 ▼2.52 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 51.55 ▲5.36 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 80.75 ▼5.31 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 32.04 ▼1.59 |
Server storage [IO: ▲0.09MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Secure Frontend Ajax Login
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲68 | 13.25 ▼1.05 | 4.34 ▲2.53 | 39.38 ▼3.73 |
Dashboard /wp-admin | 2,209 ▲21 | 5.81 ▼0.09 | 107.77 ▲6.03 | 37.63 ▼6.04 |
Posts /wp-admin/edit.php | 2,086 ▼6 | 2.05 ▲0.04 | 33.75 ▼3.15 | 37.65 ▲4.32 |
Add New Post /wp-admin/post-new.php | 1,514 ▼28 | 17.62 ▼0.70 | 669.34 ▲15.31 | 54.99 ▼8.56 |
Media Library /wp-admin/upload.php | 1,391 ▲9 | 4.26 ▲0.10 | 96.28 ▼4.66 | 42.13 ▲0.63 |
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
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
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
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Parse error
syntax error, unexpected end of file in wp-content/plugins/technoscore-login-redirection/secure-frontend-ajax-login.php on line 234
- > PHP Parse error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Screenshots: No descriptions were found for these screenshots #2, #3, #4, #5 in technoscore-login-redirection/assets to your readme.txt
technoscore-login-redirection/secure-frontend-ajax-login.php 85% from 13 tests
This is the main PHP file of "Secure Frontend Ajax Login" version 1.0.2, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("technoscore-login-redirection.php" instead of "secure-frontend-ajax-login.php")
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
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
Success! There were no dangerous files found in this plugin1,385 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 1 | 168 | 145 | 1,085 |
PHP | 2 | 39 | 32 | 174 |
CSS | 1 | 9 | 0 | 126 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.08 |
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 | 4 | |
▷ Named functions | 4 | 100.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/close3.png | 1.27KB | 0.52KB | ▼ 59.21% |