Benchmarks
Plugin footprint 83% from 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.00MB] [CPU: ▼3.60ms] Passed 4 tests
Analyzing server-side resources used by Post Paging
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 47.42 ▲10.12 |
| Dashboard /wp-admin | 3.32 ▼0.03 | 43.56 ▼15.45 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 42.93 ▲1.65 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 81.96 ▼1.52 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 34.32 ▲0.91 |
| Post Paging /wp-admin/options-general.php?page=paging | 3.21 | 34.05 |
Server storage [IO: ▲0.46MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Post Paging
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,810 ▲60 | 14.39 ▲0.10 | 1.79 ▲0.18 | 43.08 ▲0.41 |
| Dashboard /wp-admin | 2,219 ▲45 | 5.77 ▲0.19 | 84.28 ▼7.42 | 37.64 ▼4.59 |
| Posts /wp-admin/edit.php | 2,123 ▲23 | 2.26 ▲0.23 | 35.12 ▼1.61 | 33.30 ▼2.73 |
| Add New Post /wp-admin/post-new.php | 1,568 ▲39 | 23.43 ▲0.09 | 606.38 ▼66.83 | 34.00 ▼21.59 |
| Media Library /wp-admin/upload.php | 1,421 ▲21 | 4.37 ▲0.15 | 96.36 ▲0.13 | 44.86 ▼2.54 |
| Post Paging /wp-admin/options-general.php?page=paging | 1,287 | 2.37 | 51.98 | 27.00 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
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
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function load_plugin_textdomain() in wp-content/plugins/post-paging/paging.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that require attention:
- Screenshots: These screenshots lack descriptions #0, #0 in post-paging/assets to your readme.txt
post-paging/paging.php 85% from 13 tests
Analyzing the main PHP file in "Post Paging" version 1.0
Please make the necessary changes and fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("post-paging.php" instead of "paging.php")
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
There were no executable files found in this plugin302 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 17 | 10 | 234 |
| PO File | 1 | 26 | 26 | 68 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.23 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 6 | |
| ▷ Named functions | 6 | 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
2 PNG files occupy 0.44MB with 0.25MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot2.png | 431.33KB | 142.88KB | ▼ 66.87% |
| screenshot1.png | 23.71KB | 12.70KB | ▼ 46.46% |