Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Please fix the following installer errors
- The plugin cannot be installed
- > Notice in wp-content/plugins/popular-posts-count/assets/main.php+46
Trying to access array offset on value of type bool
Server metrics [RAM: ▼1.80MB] [CPU: ▼52.96ms] Passed 4 tests
This is a short check of server-side resources used by Popular Posts Count
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.19 ▼1.27 | 5.93 ▼39.90 |
Dashboard /wp-admin | 2.21 ▼1.09 | 8.35 ▼43.05 |
Posts /wp-admin/edit.php | 2.21 ▼1.15 | 7.18 ▼39.72 |
Add New Post /wp-admin/post-new.php | 2.21 ▼3.68 | 7.35 ▼89.16 |
Media Library /wp-admin/upload.php | 2.21 ▼1.02 | 7.65 ▼26.97 |
Server storage [IO: ▲0.65MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 20 new files
Database: no new tables, 8 new options
New WordPress options |
---|
widget_recent-posts |
widget_popular-posts-count |
can_compress_scripts |
db_upgraded |
recovery_mode_email_last_sent |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Popular Posts Count
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,707 ▼28 | 13.16 ▼1.59 | 1.18 ▼0.85 | 24.84 ▼23.86 |
Dashboard /wp-admin | 2,223 ▲32 | 4.92 ▲0.03 | 98.99 ▼15.80 | 79.64 ▲33.58 |
Posts /wp-admin/edit.php | 2,106 ▲17 | 2.01 ▼0.00 | 38.94 ▲2.26 | 33.87 ▼1.58 |
Add New Post /wp-admin/post-new.php | 45 ▼1,469 | 0.44 ▼17.13 | 0.10 ▼586.45 | 11.09 ▼42.17 |
Media Library /wp-admin/upload.php | 1,408 ▲26 | 4.08 ▼0.15 | 105.05 ▲4.46 | 50.08 ▲7.11 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- The plugin did not uninstall gracefully
- > Notice in wp-content/plugins/popular-posts-count/assets/main.php+46
Trying to access array offset on value of type bool
- Zombie WordPress options detected upon uninstall: 8 options
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- recovery_mode_email_last_sent
- db_upgraded
- widget_popular-posts-count
- widget_recent-comments
- widget_recent-posts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Good news, no errors were detected
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
7 plugin tags: post views, popular posts, views, posts, popular...
popular-posts-count/index.php 85% from 13 tests
This is the main PHP file of "Popular Posts Count" version 1.3, 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: It is recommended to name the main PHP file as the plugin slug ("popular-posts-count.php" instead of "index.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 199 characters long)
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 detected644 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 35 | 35 | 541 |
CSS | 2 | 11 | 10 | 103 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 9.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 16.00 |
Average method complexity | 1.22 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 5.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 | 24 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 24 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
9 PNG files occupy 0.47MB with 0.24MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.png | 188.32KB | 78.99KB | ▼ 58.06% |
assets/img/icon1.png.png | 2.16KB | 1.41KB | ▼ 34.75% |
assets/icon-128x128.png.png | 13.07KB | 6.83KB | ▼ 47.73% |
assets/img/icon.png | 1.88KB | 0.84KB | ▼ 55.44% |
assets/screenshot-1.png.png | 188.32KB | 78.99KB | ▼ 58.06% |