Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The following installer errors require your attention
- The plugin cannot be installed
- > Deprecated in wp-content/plugins/blog-post-filter/adminPage.php+2
Methods with the same name as their class will not be constructors in a future version of PHP; BlogPostFilterAdminPage has a deprecated constructor
Server metrics [RAM: ▼1.91MB] [CPU: ▼53.93ms] Passed 4 tests
A check of server-side resources used by Blog Post Filter
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.09 ▼1.38 | 5.59 ▼33.09 |
| Dashboard /wp-admin | 2.11 ▼1.20 | 6.13 ▼46.60 |
| Posts /wp-admin/edit.php | 2.11 ▼1.25 | 6.75 ▼48.71 |
| Add New Post /wp-admin/post-new.php | 2.11 ▼3.78 | 6.32 ▼87.30 |
| Media Library /wp-admin/upload.php | 2.11 ▼1.13 | 9.03 ▼26.78 |
| post filtering /wp-admin/edit.php?page=blog-post-filter-setting | 2.11 | 5.83 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 5 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| category_children |
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Blog Post Filter
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,829 ▲40 | 13.23 ▲0.04 | 2.29 ▲0.16 | 44.59 ▼3.71 |
| Dashboard /wp-admin | 2,210 ▲4 | 5.83 ▼0.08 | 108.83 ▲6.73 | 39.58 ▼2.29 |
| Posts /wp-admin/edit.php | 2,096 ▲7 | 2.00 ▲0.03 | 39.19 ▼3.47 | 35.30 ▼4.97 |
| Add New Post /wp-admin/post-new.php | 1,523 ▼10 | 23.25 ▲0.08 | 702.65 ▼1.65 | 72.24 ▲13.65 |
| Media Library /wp-admin/upload.php | 1,389 ▲4 | 4.21 ▲0.09 | 102.85 ▲0.83 | 44.10 ▲1.62 |
| post filtering /wp-admin/edit.php?page=blog-post-filter-setting | 776 | 2.04 | 27.03 | 27.00 |
Uninstaller [IO: ✅] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- Uninstall procedure validation failed for this plugin
- > Deprecated in wp-content/plugins/blog-post-filter/adminPage.php+2
Methods with the same name as their class will not be constructors in a future version of PHP; BlogPostFilterAdminPage has a deprecated constructor
- The uninstall procedure has failed, leaving 7 options in the database
- category_children
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
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
Please fix the following server-side errors
- > GET request to /wp-admin/edit.php?page=blog-post-filter-setting
- > Deprecated in wp-content/plugins/blog-post-filter/adminPage.php+2
Methods with the same name as their class will not be constructors in a future version of PHP; BlogPostFilterAdminPage has a deprecated constructor
- > GET request to /wp-admin/edit.php?page=blog-post-filter-setting
- > Notice in wp-content/plugins/blog-post-filter/adminPage.php+24
Trying to access array offset on value of type bool
SRP 50% 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 trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blog-post-filter/blog-post-filter.php:16
- > 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)
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
5 plugin tags: filter, frontpage, categories, category, post
blog-post-filter/blog-post-filter.php Passed 13 tests
The main PHP script in "Blog Post Filter" version 1.1.0 is automatically included on every request by WordPress
61 characters long description:
Blog Post Filter filters frontpage posts by their categories.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected172 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 27 | 31 | 136 |
| PO File | 1 | 11 | 17 | 36 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 8.50 |
| ▷ Minimum class complexity | 8.00 |
| ▷ Maximum class complexity | 9.00 |
| Average method complexity | 2.36 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 7.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 11 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 11 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
There were not PNG files found in your plugin