Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼5.55ms] Passed 4 tests
Server-side resources used by WP PayMobile Content Locker
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.53 ▲0.07 | 37.68 ▼0.32 |
| Dashboard /wp-admin | 3.38 ▲0.07 | 45.63 ▲0.74 |
| Posts /wp-admin/edit.php | 3.43 ▲0.07 | 43.25 ▼1.48 |
| Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 77.68 ▼21.14 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 40.59 ▲10.00 |
| Statistics /wp-admin/admin.php?page=WP_PayMobile_Stats | 3.27 | 31.64 |
| WP PayMobile /wp-admin/admin.php?page=WP_PayMobile | 3.26 | 30.46 |
| Install Guide /wp-admin/admin.php?page=WP_PayMobile_Install | 3.26 | 30.54 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 5 new files
Database: 1 new table, 10 new options
| New tables |
|---|
| wp_paymobile |
| New WordPress options |
|---|
| widget_recent-comments |
| wp_paytoread_btnstyle |
| db_upgraded |
| wp_paytoread_msg |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| wp_paytoread_currency |
| widget_recent-posts |
| can_compress_scripts |
| wp_paytoread_service |
Browser metrics Passed 4 tests
Checking browser requirements for WP PayMobile Content Locker
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,819 ▲73 | 14.25 ▼0.27 | 1.81 ▲0.25 | 44.02 ▲2.49 |
| Dashboard /wp-admin | 2,225 ▲51 | 5.53 ▼0.07 | 87.35 ▲0.05 | 76.14 ▲30.09 |
| Posts /wp-admin/edit.php | 2,127 ▲27 | 1.99 ▼0.02 | 38.28 ▲0.73 | 34.22 ▼5.57 |
| Add New Post /wp-admin/post-new.php | 1,704 ▲155 | 22.39 ▲4.03 | 667.46 ▲39.53 | 57.10 ▼6.30 |
| Media Library /wp-admin/upload.php | 1,430 ▲33 | 4.15 ▼0.06 | 98.83 ▼0.42 | 76.38 ▲34.26 |
| Statistics /wp-admin/admin.php?page=WP_PayMobile_Stats | 904 | 2.03 | 26.89 | 27.06 |
| WP PayMobile /wp-admin/admin.php?page=WP_PayMobile | 925 | 2.04 | 24.58 | 30.68 |
| Install Guide /wp-admin/admin.php?page=WP_PayMobile_Install | 1,004 | 1.99 | 28.91 | 32.57 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie tables detected upon uninstall: 1 table
- wp_paymobile
- This plugin did not uninstall successfully, leaving 10 options in the database
- wp_paytoread_service
- widget_recent-comments
- widget_theysaidso_widget
- wp_paytoread_btnstyle
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- wp_paytoread_msg
- wp_paytoread_currency
- db_upgraded
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)
Even though everything seems fine, this is not an exhaustive test
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
Please fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/wp-paymobile-content-locker/WP-PayMobile.php:23
- > 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)
There are user-side issues you should fix
- > GET request to /wp-admin/admin.php?page=WP_PayMobile_Stats
- > Network (severe)
wp-content/plugins/wp-paymobile-content-locker/assets/lock-icon.png - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/admin.php?page=WP_PayMobile_Install
- > Network (severe)
wp-admin/assets/blueprint-css/screen.css - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/admin.php?page=WP_PayMobile_Install
- > Network (severe)
wp-admin/assets/blueprint-css/plugins/fancy-type/screen.css - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/admin.php?page=WP_PayMobile_Install
- > Network (severe)
wp-admin/assets/blueprint-css/print.css - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Stable tag: Not defined
wp-paymobile-content-locker/WP-PayMobile.php 92% from 13 tests
The principal PHP file in "WP PayMobile Content Locker" v. 1.3 is loaded by WordPress automatically on each request
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-paymobile-content-locker.php" instead of "WP-PayMobile.php")
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
Good job! No executable or dangerous file extensions detected394 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 80 | 37 | 314 |
| HTML | 1 | 26 | 2 | 80 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 32.00 |
| ▷ Minimum class complexity | 32.00 |
| ▷ Maximum class complexity | 32.00 |
| Average method complexity | 3.82 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.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 | 11 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 11 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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 Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| lock-icon.png | 2.80KB | 1.40KB | ▼ 50.05% |
| lock.png | 2.03KB | 0.62KB | ▼ 69.32% |