Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.11MB] [CPU: ▼141.93ms] Passed 4 tests
An overview of server-side resources used by BridgerPay
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.92 ▲0.20 | 34.40 ▲12.75 |
Dashboard /wp-admin | 3.15 ▲0.10 | 39.43 ▼8.88 |
Posts /wp-admin/edit.php | 3.27 ▲0.16 | 42.66 ▼0.92 |
Add New Post /wp-admin/post-new.php | 5.51 ▲0.08 | 90.04 ▼567.35 |
Media Library /wp-admin/upload.php | 3.10 ▲0.10 | 35.22 ▲9.42 |
Server storage [IO: ▲0.24MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 25 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for BridgerPay
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,836 ▲240 | 16.23 ▲0.36 | 10.82 ▲2.60 | 49.46 ▲2.87 |
Dashboard /wp-admin | 2,991 ▲57 | 5.85 ▼0.22 | 135.64 ▼12.08 | 108.30 ▼10.61 |
Posts /wp-admin/edit.php | 2,763 ▲24 | 2.70 ▲0.02 | 63.46 ▼3.56 | 93.31 ▲4.86 |
Add New Post /wp-admin/post-new.php | 1,700 ▲119 | 18.78 ▼1.68 | 367.07 ▼29.32 | 116.77 ▲0.74 |
Media Library /wp-admin/upload.php | 1,831 ▲24 | 5.01 ▲0.02 | 146.64 ▼12.72 | 186.56 ▲66.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The plugin uninstalled successfully, without leaving any zombie files or tables
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 0% 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 items
- 2× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/bridgerpay/public/partials/bridgerpay-public-display.php
- > /wp-content/plugins/bridgerpay/admin/partials/bridgerpay-admin-display.php
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/bridgerpay/admin/class-bridgerpay-admin.php:287
- > 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 on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need to be fixed:
- Plugin Name: You should set the name of your plugin on the first line (
=== bridgerpay ===
) - Donate link: Please fix this invalid url: ""
bridgerpay/bridgerpay.php Passed 13 tests
The main file in "BridgerPay" v. 1.0.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
96 characters long description:
This is a short description of what the plugin does. It's displayed in the WordPress admin area.
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
Success! There were no dangerous files found in this plugin440 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 12 | 176 | 569 | 434 |
JavaScript | 2 | 4 | 54 | 6 |
CSS | 2 | 0 | 8 | 0 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
Average class complexity | 3.38 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 13.00 |
Average method complexity | 1.51 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.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 | 38 | |
▷ Static methods | 2 | 5.26% |
▷ Public methods | 33 | 86.84% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 13.16% |
Functions | 5 | |
▷ Named functions | 5 | 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
PNG files should be compressed to save space and minimize bandwidth usage
3 PNG files occupy 0.19MB with 0.10MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.PNG | 25.23KB | 12.32KB | ▼ 51.19% |
assets/screenshot-3.PNG | 128.13KB | 54.29KB | ▼ 57.63% |
assets/screenshot-2.PNG | 39.91KB | 17.32KB | ▼ 56.59% |