Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▼0.58MB] [CPU: ▼26.28ms] Passed 4 tests
This is a short check of server-side resources used by Blimply
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.64 ▲0.18 | 36.59 ▼6.38 |
Dashboard /wp-admin | 3.27 ▼0.08 | 30.15 ▼33.18 |
Posts /wp-admin/edit.php | 3.61 ▲0.26 | 49.96 ▲1.67 |
Add New Post /wp-admin/post-new.php | 3.27 ▼2.62 | 26.06 ▼67.21 |
Media Library /wp-admin/upload.php | 3.43 ▲0.20 | 37.61 ▲2.40 |
Urban Airship Tags /wp-admin/edit-tags.php?taxonomy=blimply_tags | 3.30 | 27.68 |
Blimply Settings /wp-admin/options-general.php?page=blimply_settings | 3.39 | 29.90 |
Server storage [IO: ▲0.22MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 17 new files
Database: no new tables, 8 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
widget_recent-comments |
blimply_sounds |
urban_airship |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Blimply
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,895 ▲149 | 13.35 ▼1.20 | 4.43 ▲2.73 | 38.37 ▼3.78 |
Dashboard /wp-admin | 2,286 ▲101 | 5.89 ▲0.04 | 100.56 ▼8.86 | 80.63 ▲33.32 |
Posts /wp-admin/edit.php | 2,109 ▲38 | 2.23 ▲0.20 | 40.20 ▲3.78 | 33.72 ▼3.08 |
Add New Post /wp-admin/post-new.php | 6,238 ▲4,724 | 25.98 ▲8.37 | 829.49 ▲166.88 | 67.32 ▲8.63 |
Media Library /wp-admin/upload.php | 1,404 ▲22 | 4.41 ▲0.18 | 97.19 ▼16.14 | 43.43 ▼0.77 |
Urban Airship Tags /wp-admin/edit-tags.php?taxonomy=blimply_tags | 28 | 0.44 | 0.06 | 3.69 |
Blimply Settings /wp-admin/options-general.php?page=blimply_settings | 908 | 2.06 | 36.35 | 24.88 |
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
The following items require your attention
- Zombie WordPress options detected upon uninstall: 8 options
- blimply_sounds
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- urban_airship
- theysaidso_admin_options
Smoke tests 50% 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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following
- 4× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/blimply/blimply.php:31
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blimply/lib/settings-api-class/class.settings-api.php:35
- > PHP Fatal error
Uncaught Error: Class 'WeDevs_Settings_API' not found in wp-content/plugins/blimply/lib/blimply-settings.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blimply/lib/settings-api-class/procedural-example.php:249
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please take a look at the following user-side issues
- > GET request to /wp-admin/edit-tags.php?taxonomy=blimply_tags
- > Network (severe)
wp-admin/edit-tags.php?taxonomy=blimply_tags - Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Please fix the following attributes:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Per-post Push notification), #2 (Dashboard widget), #3 (Blimply Settings)
- Tested up to: Version not formatted correctly
blimply/blimply.php 92% from 13 tests
The principal PHP file in "Blimply" v. 0.4 is loaded by WordPress automatically on each request
The following require your attention:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 240 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin1,380 lines of code in 10 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 6 | 189 | 313 | 1,300 |
Markdown | 2 | 19 | 0 | 34 |
JavaScript | 1 | 4 | 0 | 33 |
CSS | 1 | 3 | 0 | 13 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.31 |
Average class complexity | 14.38 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 41.00 |
Average method complexity | 2.60 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 12.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 67 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 66 | 98.51% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 1.49% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 11 | |
▷ Global constants | 11 | 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
4 PNG files occupy 0.14MB with 0.09MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 19.77KB | 7.55KB | ▼ 61.80% |
screenshot-3.png | 37.41KB | 17.11KB | ▼ 54.27% |
screenshot-1.png | 16.73KB | 6.54KB | ▼ 60.93% |
lib/settings-api-class/screenshot-1.png | 73.98KB | 26.00KB | ▼ 64.85% |