Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.34MB] [CPU: ▼295.19ms] Passed 4 tests
This is a short check of server-side resources used by Advanced Recent Posts
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.94 ▲0.43 | 59.29 ▲4.62 |
Dashboard /wp-admin | 3.77 ▲0.37 | 35.83 ▲1.90 |
Posts /wp-admin/edit.php | 4.00 ▲0.36 | 39.63 ▲3.79 |
Add New Post /wp-admin/post-new.php | 7.28 ▲0.28 | 101.74 ▼1,181.20 |
Media Library /wp-admin/upload.php | 3.65 ▲0.35 | 24.82 ▼5.26 |
Server storage [IO: ▲0.20MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 14 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
A check of browser resources used by Advanced Recent Posts
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,940 ▲195 | 16.50 ▲0.75 | 10.53 ▲3.05 | 2.72 ▲0.53 |
Dashboard /wp-admin | 2,918 ▲57 | 6.15 ▼0.02 | 118.74 ▼20.90 | 151.26 ▼9.50 |
Posts /wp-admin/edit.php | 2,714 ▲20 | 3.24 ▼0.00 | 63.79 ▲2.11 | 138.10 ▲4.07 |
Add New Post /wp-admin/post-new.php | 1,736 ▼22 | 17.49 ▼3.91 | 424.30 ▼5.73 | 191.43 ▲32.77 |
Media Library /wp-admin/upload.php | 1,724 ▲26 | 5.48 ▲0.03 | 132.80 ▼4.49 | 181.27 ▼7.77 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The plugin uninstalled successfully, without leaving any zombie files or tables
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, 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
- 4× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/advanced-recent-posts/lptw-recent-posts.php:21
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/advanced-recent-posts/includes/class.widget.small.thumbnails.php:7
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/advanced-recent-posts/includes/class.widget.fluid.images.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/advanced-recent-posts/backend/lptw-recent-posts-backend.php:4
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need your attention:
- Plugin Name: You should set the name of your plugin on the first line (
=== advanced-recent-posts ===
) - Tags: Please delete some tags, you are using 17 tag instead of maximum 10
advanced-recent-posts/lptw-recent-posts.php 85% from 13 tests
The primary PHP file in "Advanced Recent Posts" version 0.6.14 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("advanced-recent-posts.php" instead of "lptw-recent-posts.php")
- Text Domain: The text domain name must use dashes instead of underscores, and it must be lowercase
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected3,064 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 317 | 155 | 2,014 |
CSS | 3 | 165 | 65 | 684 |
JavaScript | 3 | 71 | 34 | 366 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 102.00 |
▷ Minimum class complexity | 99.00 |
▷ Maximum class complexity | 105.00 |
Average method complexity | 21.20 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 58.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 | 10 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 10 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 24 | |
▷ Named functions | 24 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 compressed PNG files occupy 0.00MB
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
backend/chosen/chosen-sprite.png | 0.53KB | 0.88KB | 0.00% |
backend/chosen/chosen-sprite@2x.png | 0.72KB | 0.83KB | 0.00% |