Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼3.46ms] Passed 4 tests
A check of server-side resources used by Post Category Prev-Next Link Fix
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.04 | 41.30 ▼0.34 |
| Dashboard /wp-admin | 3.34 ▲0.03 | 47.18 ▼8.56 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 52.08 ▲2.27 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 85.83 ▼7.19 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 38.04 ▲4.11 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Post Category Prev-Next Link Fix
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲3 | 14.27 ▼0.08 | 1.58 ▼0.07 | 40.77 ▼0.93 |
| Dashboard /wp-admin | 2,198 ▲18 | 5.59 ▼0.06 | 87.43 ▼8.08 | 40.64 ▼2.21 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.02 ▲0.01 | 39.60 ▼2.21 | 37.54 ▲0.15 |
| Add New Post /wp-admin/post-new.php | 1,537 ▲11 | 18.25 ▼5.42 | 646.66 ▼47.17 | 72.59 ▲14.40 |
| Media Library /wp-admin/upload.php | 1,403 ▼0 | 4.19 ▼0.02 | 97.46 ▼10.34 | 43.31 ▼2.40 |
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
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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
Please take a closer look at the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/post-category-prev-next-link-fix/post-category-prev-next.php:39
- > 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 errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% 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
Please fix the following attributes:
- Requires at least: Invalid version format
- Requires php: Invalid version format
post-category-prev-next-link-fix/post-category-prev-next.php 85% from 13 tests
"Post Category Prev-Next Link Fix" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("post-category-prev-next-link-fix.php" instead of "post-category-prev-next.php")
- Description: Please keep the plugin description shorter than 140 characters (currently 197 characters long)
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
No dangerous file extensions were detected76 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 28 | 29 | 76 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| Average class complexity | 13.00 |
| ▷ Minimum class complexity | 13.00 |
| ▷ Maximum class complexity | 13.00 |
| Average method complexity | 2.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.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 | 8 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 8 | 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
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