Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.10MB] [CPU: ▼2.24ms] Passed 4 tests
Analyzing server-side resources used by Sharpay
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.06 | 44.98 ▲2.36 |
Dashboard /wp-admin | 3.41 ▲0.11 | 49.09 ▼2.61 |
Posts /wp-admin/edit.php | 3.52 ▲0.17 | 47.17 ▲0.80 |
Add New Post /wp-admin/post-new.php | 6.01 ▲0.12 | 84.56 ▼9.51 |
Media Library /wp-admin/upload.php | 3.33 ▲0.10 | 36.56 ▲4.28 |
Sharpay /wp-admin/options-general.php?page=sharpay-settings | 3.30 | 34.04 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 14 new files
Database: no new tables, 7 new options
New WordPress options |
---|
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
widget_sharpay_widget |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
Browser metrics Passed 4 tests
Sharpay: an overview of browser usage
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,808 ▲73 | 13.26 ▼1.10 | 4.79 ▲3.05 | 42.51 ▼3.42 |
Dashboard /wp-admin | 2,217 ▲28 | 4.90 ▼0.05 | 99.85 ▼20.53 | 39.32 ▼5.86 |
Posts /wp-admin/edit.php | 2,097 ▲11 | 2.04 ▲0.08 | 35.89 ▼1.57 | 31.93 ▼1.87 |
Add New Post /wp-admin/post-new.php | 1,521 ▼18 | 23.59 ▲0.09 | 661.72 ▲8.38 | 50.17 ▲0.42 |
Media Library /wp-admin/upload.php | 1,396 ▲5 | 4.24 ▲0.02 | 94.88 ▼1.29 | 39.71 ▼0.96 |
Sharpay /wp-admin/options-general.php?page=sharpay-settings | 2,248 | 4.50 | 84.01 | 26.73 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- The uninstall procedure has failed, leaving 7 options in the database
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_sharpay_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
- 4× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/sharpay/sharpay.php:33
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/sharpay/includes/sharpay-admin.php:19
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/sharpay/includes/sharpay-public.php:19
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/sharpay/includes/class-sharpay-widget.php:19
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Please take a look at the following user-side issues
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=sharpay-settings
- > Other (severe) in unknown
chrome-error://chromewebdata/ - Refused to display 'https://app.sharpay.io/' in a frame because it set 'X-Frame-Options' to 'deny'.
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% 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 (
=== sharpay ===
)
sharpay/sharpay.php 85% from 13 tests
Analyzing the main PHP file in "Sharpay" version 1.9.2
It is important to 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
- Description: Please keep the plugin description shorter than 140 characters (currently 202 characters long)
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 plugin828 lines of code in 10 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 158 | 74 | 540 |
PO File | 1 | 38 | 38 | 118 |
JavaScript | 1 | 19 | 13 | 98 |
CSS | 1 | 23 | 14 | 69 |
Markdown | 2 | 1 | 0 | 3 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.46 |
Average class complexity | 8.00 |
▷ Minimum class complexity | 8.00 |
▷ Maximum class complexity | 8.00 |
Average method complexity | 2.75 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.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 | 4 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 4 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 23 | |
▷ Named functions | 23 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 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
No PNG files were detected