Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.10MB] [CPU: ▼135.18ms] Passed 4 tests
A check of server-side resources used by WordPress GPS
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.88 ▲0.16 | 40.58 ▲18.72 |
| Dashboard /wp-admin | 3.14 ▲0.09 | 44.54 ▲0.88 |
| Posts /wp-admin/edit.php | 3.26 ▲0.15 | 46.75 ▲4.92 |
| Add New Post /wp-admin/post-new.php | 5.51 ▲0.08 | 94.89 ▼540.53 |
| Media Library /wp-admin/upload.php | 3.09 ▲0.08 | 33.37 ▼6.00 |
Server storage [IO: ▲0.09MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 17 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
An overview of browser requirements for WordPress GPS
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,723 ▲127 | 15.81 ▲0.16 | 8.83 ▲1.14 | 47.99 ▲3.04 |
| Dashboard /wp-admin | 2,993 ▲56 | 5.87 ▼0.06 | 161.64 ▼0.48 | 109.87 ▼0.81 |
| Posts /wp-admin/edit.php | 2,759 ▲20 | 2.68 ▼0.13 | 66.10 ▲6.14 | 92.23 ▲10.66 |
| Add New Post /wp-admin/post-new.php | 1,685 ▲183 | 18.89 ▲0.31 | 373.39 ▲23.25 | 118.69 ▲8.41 |
| Media Library /wp-admin/upload.php | 1,830 ▲20 | 5.02 ▼0.01 | 147.52 ▼25.31 | 112.53 ▼17.18 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
This plugin's uninstaller ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for 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
- 9× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Warning
Use of undefined constant GB_GPS_ADMIN_MENU_TITLE - assumed 'GB_GPS_ADMIN_MENU_TITLE' (this will throw an Error in a future version of PHP) in wp-content/plugins/wordpress-gps/include/admin_menu.tpl.php on line 7
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/wordpress-gps/include/admin_menu.tpl.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wordpress-gps/scenarios.php:15
- > PHP Warning
Use of undefined constant GB_GPS_MENU_POINTER_TITLE - assumed 'GB_GPS_MENU_POINTER_TITLE' (this will throw an Error in a future version of PHP) in wp-content/plugins/wordpress-gps/scenarios.php on line 15
- > PHP Warning
Use of undefined constant GB_GPS_ADD_POST_SCENARIO_DESCRIPTION - assumed 'GB_GPS_ADD_POST_SCENARIO_DESCRIPTION' (this will throw an Error in a future version of PHP) in wp-content/plugins/wordpress-gps/scenarios.php on line 7
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wordpress-gps/include/lang.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/wordpress-gps/include/config.php:5
- > PHP Warning
Use of undefined constant GB_GPS_ADD_POST_SCENARIO_LABEL - assumed 'GB_GPS_ADD_POST_SCENARIO_LABEL' (this will throw an Error in a future version of PHP) in wp-content/plugins/wordpress-gps/scenarios.php on line 6
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/wordpress-gps/include/config.php:5
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Please fix the following attributes:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== wordpress-gps ===) - Screenshots: These screenshots require images: #1 (Choose the scenario you want to launch from its name and a little description), #2 (Follow the pointers!)
wordpress-gps/gb_gps.php 85% from 13 tests
The main PHP file in "WordPress GPS" ver. 1.0.16 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("wordpress-gps.php" instead of "gb_gps.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 195 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
Success! There were no dangerous files found in this plugin889 lines of code in 12 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 9 | 102 | 141 | 649 |
| Markdown | 1 | 52 | 0 | 118 |
| PO File | 1 | 48 | 47 | 114 |
| JavaScript | 1 | 1 | 0 | 8 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.26 |
| Average class complexity | 10.00 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 17.00 |
| Average method complexity | 2.42 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 5.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 19 | |
| ▷ Static methods | 2 | 10.53% |
| ▷ Public methods | 16 | 84.21% |
| ▷ Protected methods | 3 | 15.79% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 54 | |
| ▷ Global constants | 51 | 94.44% |
| ▷ Class constants | 3 | 5.56% |
| ▷ Public constants | 3 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.03MB with 0.01MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 16.15KB | 10.34KB | ▼ 35.99% |
| screenshot-2.png | 13.39KB | 8.74KB | ▼ 34.70% |