Benchmarks
Plugin footprint Passed 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.02MB] [CPU: ▼139.30ms] Passed 4 tests
This is a short check of server-side resources used by Auto Post to Google+
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.86 ▲0.03 | 37.05 ▲6.58 |
| Dashboard /wp-admin | 3.09 ▲0.03 | 44.12 ▼0.27 |
| Posts /wp-admin/edit.php | 3.14 ▲0.02 | 44.44 ▼6.56 |
| Add New Post /wp-admin/post-new.php | 5.45 ▲0.01 | 104.18 ▼550.19 |
| Media Library /wp-admin/upload.php | 3.03 ▲0.03 | 31.74 ▼0.18 |
| Google+ Auto Post /wp-admin/options-general.php?page=ergplus | 2.98 | 34.99 |
Server storage [IO: ▲0.36MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 4 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Auto Post to Google+
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,684 ▲47 | 15.81 ▲0.23 | 7.46 ▼1.35 | 48.97 ▼0.87 |
| Dashboard /wp-admin | 2,975 ▲44 | 5.86 ▼0.07 | 139.78 ▼3.34 | 121.34 ▲1.61 |
| Posts /wp-admin/edit.php | 2,744 ▲5 | 2.70 ▼0.00 | 70.99 ▲0.93 | 90.89 ▲0.32 |
| Add New Post /wp-admin/post-new.php | 1,723 ▲119 | 15.92 ▼2.91 | 417.13 ▲0.91 | 127.89 ▲7.62 |
| Media Library /wp-admin/upload.php | 1,812 ▲5 | 5.04 ▲0.02 | 161.86 ▲10.36 | 157.19 ▲23.14 |
| Google+ Auto Post /wp-admin/options-general.php?page=ergplus | 1,202 | 2.05 | 57.40 | 81.59 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Uninstall script ran successfully
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
These server-side errors were triggered
- 3 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=ergplus
- > Notice in wp-content/plugins/google-auto-post/ergplus-autopost.php+49
Trying to access array offset on value of type bool
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× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/google-auto-post/ergplus-autopost.php:10
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 90% 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
These attributes need your attention:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== google-auto-post ===) - Screenshots: These screenshots have no corresponding images in /assets: #1 (Screenshot 1 : The Options Panel), #2 (Screenshot 2 : The Post Screen)
google-auto-post/ergplus-autopost.php 92% from 13 tests
This is the main PHP file of "Auto Post to Google+" version 1.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("google-auto-post.php" instead of "ergplus-autopost.php")
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
Everything looks great! No dangerous files found in this plugin137 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 3 | 27 | 137 |
PHP code Passed 2 tests
Analyzing 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 | 1.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 1.00 |
| Average method complexity | 1.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 1.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 | 2 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 2 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 10 | |
| ▷ Named functions | 10 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.35MB with 0.21MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 210.68KB | 82.60KB | ▼ 60.80% |
| screenshot-2.png | 142.92KB | 57.35KB | ▼ 59.87% |