Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.08MB] [CPU: ▼1.52ms] Passed 4 tests
An overview of server-side resources used by Gmt Post IDs
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 48.83 ▲9.43 |
Dashboard /wp-admin | 3.40 ▲0.09 | 51.52 ▲0.25 |
Posts /wp-admin/edit.php | 3.45 ▲0.09 | 49.81 ▼4.12 |
Add New Post /wp-admin/post-new.php | 5.98 ▲0.09 | 85.92 ▼9.39 |
Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 39.18 ▲7.18 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 10 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Gmt Post IDs
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,808 ▲47 | 14.76 ▲0.36 | 1.80 ▲0.23 | 42.20 ▼1.12 |
Dashboard /wp-admin | 2,214 ▲40 | 5.62 ▲0.04 | 91.89 ▲2.76 | 41.48 ▼3.34 |
Posts /wp-admin/edit.php | 2,146 ▲43 | 1.95 ▼0.02 | 37.52 ▼1.79 | 33.55 ▼5.46 |
Add New Post /wp-admin/post-new.php | 1,552 ▲26 | 23.10 ▲0.01 | 681.65 ▲70.84 | 59.95 ▲13.88 |
Media Library /wp-admin/upload.php | 1,419 ▲16 | 4.19 ▲0.07 | 106.14 ▼0.06 | 45.77 ▼0.41 |
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
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however 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
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/gmt-post-ids/partials/display-dashboard.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/gmt-post-ids/partials/gmt-post-ids-display.php:13
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Tags: You are using too many tags: 18 tag instead of maximum 10
- Screenshots: Please describe screenshot #1 in gmt-post-ids/assets to your readme.txt
gmt-post-ids/gmt-ids.php 85% from 13 tests
"Gmt Post IDs" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 311 characters long)
- Main file name: The principal plugin file should be the same as the plugin slug ("gmt-post-ids.php" instead of "gmt-ids.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected807 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 1 | 96 | 63 | 441 |
PHP | 4 | 74 | 145 | 326 |
JavaScript | 2 | 7 | 0 | 40 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.51 |
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 | 16 | |
▷ Named functions | 16 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.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
PNG images were not found in this plugin