Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.14MB] [CPU: ▼3.81ms] Passed 4 tests
Server-side resources used by Pushed
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.59 ▲0.13 | 46.67 ▼5.40 |
Dashboard /wp-admin | 3.46 ▲0.11 | 51.61 ▼10.69 |
Posts /wp-admin/edit.php | 3.57 ▲0.21 | 53.11 ▲2.98 |
Add New Post /wp-admin/post-new.php | 6.03 ▲0.15 | 98.04 ▼0.37 |
Media Library /wp-admin/upload.php | 3.38 ▲0.15 | 37.87 ▲1.22 |
Pushed /wp-admin/options-general.php?page=pushed | 3.35 | 37.04 |
Server storage [IO: ▲0.95MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-comments |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Pushed
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,823 ▲62 | 13.22 ▼1.04 | 1.92 ▲0.02 | 43.12 ▲3.90 |
Dashboard /wp-admin | 2,229 ▲23 | 4.82 ▼0.06 | 118.12 ▲16.69 | 44.06 ▲7.22 |
Posts /wp-admin/edit.php | 2,108 ▲5 | 2.03 ▲0.05 | 40.73 ▼7.68 | 35.19 ▼7.31 |
Add New Post /wp-admin/post-new.php | 6,249 ▲4,709 | 18.92 ▼4.13 | 1,046.86 ▲435.29 | 65.30 ▲4.88 |
Media Library /wp-admin/upload.php | 1,411 ▲14 | 4.26 ▲0.06 | 100.07 ▼18.48 | 47.28 ▼5.32 |
Pushed /wp-admin/options-general.php?page=pushed | 953 | 2.18 | 32.43 | 39.13 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pushed-push-notifications/settings.php:296
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pushed-push-notifications/settings.php:296
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need to be fixed:
- Screenshots: These screenshots do not have images: #1 (Pushed Administration Panel), #2 (Pushed Publishing Widget), #3 (Pushed.co Developer Panel (App Credentials highlighted))
pushed-push-notifications/pushed.php 92% from 13 tests
The main file in "Pushed" v. 2.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("pushed-push-notifications.php" instead of "pushed.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected864 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 131 | 64 | 654 |
JavaScript | 1 | 26 | 1 | 146 |
CSS | 1 | 11 | 0 | 58 |
HTML | 1 | 0 | 0 | 6 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.33 |
Average class complexity | 4.67 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 13.00 |
Average method complexity | 2.10 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 20 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 19 | 95.00% |
▷ Protected methods | 1 | 5.00% |
▷ Private methods | 0 | 0.00% |
Functions | 19 | |
▷ Named functions | 19 | 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 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
8 PNG files occupy 0.91MB with 0.52MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 169.05KB | 73.03KB | ▼ 56.80% |
assets/pushed_logo_wordpress_settings_page.png | 19.58KB | 10.63KB | ▼ 45.74% |
assets/icon-128x128.png | 16.66KB | 7.85KB | ▼ 52.89% |
assets/pushed_favicon_wordpress_edit_page.png | 43.81KB | 14.34KB | ▼ 67.27% |
assets/banner-772x250.png | 255.05KB | 101.88KB | ▼ 60.06% |