Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.40ms] Passed 4 tests
Server-side resources used by Agregs Postget
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 37.01 ▼2.59 |
Dashboard /wp-admin | 3.32 ▲0.02 | 44.88 ▼4.26 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 44.13 ▼3.60 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 79.25 ▼15.15 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.63 ▲0.95 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Agregs Postget
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.35 ▼1.02 | 4.07 ▲2.41 | 47.10 ▲5.76 |
Dashboard /wp-admin | 2,209 ▲21 | 5.78 ▼0.18 | 94.46 ▼21.55 | 38.59 ▼7.29 |
Posts /wp-admin/edit.php | 2,092 ▲3 | 2.00 ▼0.02 | 35.33 ▲1.44 | 32.48 ▼2.33 |
Add New Post /wp-admin/post-new.php | 1,544 ▲30 | 18.07 ▲0.66 | 600.36 ▼33.36 | 52.60 ▼2.17 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.22 ▲0.04 | 100.08 ▲1.74 | 41.68 ▼2.26 |
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 were found after uninstall: 6 options
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not 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
Almost there! Just fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/agregs-postget/agregspostget.php:25
- > 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 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Screenshots: Screenshot #1 (`/assets/screenshot-1.jpg`) image required
agregs-postget/agregspostget.php 85% from 13 tests
"Agregs Postget" version 1.0.6's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 201 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("agregs-postget.php" instead of "agregspostget.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Success! There were no dangerous files found in this plugin183 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 56 | 77 | 142 |
PO File | 1 | 10 | 10 | 37 |
INI | 1 | 1 | 0 | 4 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.23 |
Average class complexity | 13.00 |
▷ Minimum class complexity | 13.00 |
▷ Maximum class complexity | 13.00 |
Average method complexity | 2.71 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 6.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 | 7 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 7 | 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
PNG images were not found in this plugin