Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▼0.33MB] [CPU: ▼18.44ms] Passed 4 tests
This is a short check of server-side resources used by Payper widget
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.43 ▼0.03 | 33.56 ▼11.96 |
Dashboard /wp-admin | 3.29 ▼0.01 | 37.32 ▼15.56 |
Posts /wp-admin/edit.php | 3.33 ▼0.03 | 40.08 ▼7.00 |
Add New Post /wp-admin/post-new.php | 4.64 ▼1.25 | 49.22 ▼39.22 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 34.25 ▲1.10 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_recent-posts |
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Payper widget: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,815 ▲80 | 13.23 ▼1.14 | 4.80 ▲2.93 | 40.68 ▼9.15 |
Dashboard /wp-admin | 2,218 ▲30 | 5.82 ▲0.93 | 97.37 ▼6.12 | 83.48 ▲38.80 |
Posts /wp-admin/edit.php | 2,104 ▲15 | 1.98 ▼0.04 | 35.50 ▼0.84 | 32.62 ▼2.29 |
Add New Post /wp-admin/post-new.php | 6,455 ▲4,918 | 20.11 ▼3.03 | 997.82 ▲314.47 | 57.96 ▲1.22 |
Media Library /wp-admin/upload.php | 1,400 ▲9 | 4.18 ▼0.05 | 98.59 ▼1.76 | 81.85 ▲34.70 |
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
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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 take a closer look at the following
- 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/payper/includes/settings.php:113
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/payper/includes/adminbox.php:67
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
4 plugin tags: paywall, blocks, monetization, gutenberg
payper/wp-payper.php 92% from 13 tests
The entry point to "Payper widget" version 0.1.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("payper.php" instead of "wp-payper.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
There were no executable files found in this plugin300 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 65 | 86 | 300 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.23 |
Average class complexity | 4.00 |
▷ Minimum class complexity | 4.00 |
▷ Maximum class complexity | 4.00 |
Average method complexity | 2.00 |
▷ Minimum method complexity | 2.00 |
▷ Maximum method complexity | 2.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 1 | 100.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 3 | |
▷ Static methods | 3 | 100.00% |
▷ Public methods | 3 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 11 | |
▷ Named functions | 11 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
payper_16x16.png | 0.39KB | 0.29KB | ▼ 25.69% |