Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.23MB] [CPU: ▼5.10ms] Passed 4 tests
This is a short check of server-side resources used by JWT Auth - WordPress JSON Web Token Authentication
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.68 ▲0.21 | 34.70 ▼3.18 |
| Dashboard /wp-admin | 3.53 ▲0.22 | 45.89 ▼0.90 |
| Posts /wp-admin/edit.php | 3.64 ▲0.29 | 49.10 ▼0.37 |
| Add New Post /wp-admin/post-new.php | 6.13 ▲0.25 | 81.52 ▼15.96 |
| Media Library /wp-admin/upload.php | 3.45 ▲0.22 | 37.58 ▲3.38 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 35 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
JWT Auth - WordPress JSON Web Token Authentication: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲53 | 14.37 ▼0.36 | 1.68 ▼0.08 | 40.63 ▲0.32 |
| Dashboard /wp-admin | 2,223 ▲46 | 5.62 ▼0.00 | 83.95 ▼0.61 | 38.74 ▼0.47 |
| Posts /wp-admin/edit.php | 2,129 ▲26 | 2.07 ▲0.11 | 36.14 ▼4.44 | 34.71 ▼4.16 |
| Add New Post /wp-admin/post-new.php | 1,555 ▲27 | 18.18 ▼4.93 | 619.62 ▼78.90 | 67.74 ▲10.03 |
| Media Library /wp-admin/upload.php | 1,428 ▲25 | 4.28 ▲0.04 | 96.39 ▼12.84 | 42.63 ▼6.12 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/jwt-auth/jwt-auth.php
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Interface 'Firebase\\JWT\\JWTExceptionWithPayloadInterface' not found in wp-content/plugins/jwt-auth/vendor/firebase/php-jwt/src/ExpiredException.php:5
- > PHP Fatal error
Uncaught Error: Interface 'Firebase\\JWT\\JWTExceptionWithPayloadInterface' not found in wp-content/plugins/jwt-auth/vendor/firebase/php-jwt/src/BeforeValidException.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 97% 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
These attributes need your attention:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Success response when trying to generate token), #2 (Error response when trying to generate token), #3 (Other error responses)
jwt-auth/jwt-auth.php Passed 13 tests
This is the main PHP file of "JWT Auth - WordPress JSON Web Token Authentication" version 2.1.6, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
29 characters long description:
WordPress JWT Authentication.
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 plugin2,548 lines of code in 30 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 25 | 511 | 1,205 | 2,286 |
| Markdown | 2 | 64 | 0 | 120 |
| JSON | 1 | 0 | 0 | 116 |
| JavaScript | 1 | 7 | 3 | 24 |
| YAML | 1 | 0 | 0 | 2 |
PHP code Passed 2 tests
A brief analysis 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.45 |
| Average class complexity | 19.94 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 76.00 |
| Average method complexity | 3.74 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 22.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 4 | |
| Interfaces | 1 | |
| Traits | 0 | |
| Classes | 16 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 16 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 122 | |
| ▷ Static methods | 50 | 40.98% |
| ▷ Public methods | 97 | 79.51% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 25 | 20.49% |
| Functions | 3 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 3 | 100.00% |
| Constants | 12 | |
| ▷ Global constants | 3 | 25.00% |
| ▷ Class constants | 9 | 75.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin