Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.12MB] [CPU: ▼300.75ms] Passed 4 tests
Analyzing server-side resources used by Access Code Feeder
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.72 ▲0.21 | 56.34 ▲5.79 |
| Dashboard /wp-admin | 3.56 ▲0.15 | 35.01 ▲1.86 |
| Posts /wp-admin/edit.php | 3.78 ▲0.14 | 39.83 ▲4.64 |
| Add New Post /wp-admin/post-new.php | 7.02 ▲0.06 | 96.26 ▼1,205.57 |
| Media Library /wp-admin/upload.php | 3.43 ▲0.13 | 25.54 ▼3.92 |
| Access Code Feeder /wp-admin/options-general.php?page=access-code-feeder | 3.41 | 25.53 |
Server storage [IO: ▲0.66MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 23 new files
Database: 1 new table, no new options
| New tables |
|---|
| wp_acf_Feeders |
Browser metrics Passed 4 tests
Access Code Feeder: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,791 ▲37 | 16.14 ▲0.53 | 6.28 ▲0.09 | 2.46 ▼0.44 |
| Dashboard /wp-admin | 2,897 ▲36 | 6.15 ▼0.02 | 114.59 ▼12.83 | 159.85 ▼1.54 |
| Posts /wp-admin/edit.php | 2,693 ▲5 | 3.24 ▲0.00 | 61.41 ▲1.62 | 137.03 ▼2.83 |
| Add New Post /wp-admin/post-new.php | 1,683 ▼7 | 18.18 ▼3.03 | 400.53 ▼3.75 | 152.22 ▲1.40 |
| Media Library /wp-admin/upload.php | 1,703 ▲5 | 5.50 ▲0.03 | 139.63 ▲5.08 | 186.35 ▼4.12 |
| Access Code Feeder /wp-admin/options-general.php?page=access-code-feeder | 1,446 | 3.06 | 62.06 | 169.22 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Uninstall script ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
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
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/access-code-feeder/access-code-feeder.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: These screenshots do not have images: #1 (**Feeders List** -), #2 (**Add new Feeder** - Entering Feeder Name.), #3 (**Load Access Codes** - No access codes yet.), #4 (**Access Codes Loaded** - Just for Testing.), #5 (**Usage** - Usage information.)
access-code-feeder/access-code-feeder.php Passed 13 tests
The main PHP script in "Access Code Feeder" version 1.0.3 is automatically included on every request by WordPress
63 characters long description:
Feeds unique access codes to chat bots, merchant services, etc.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected1,267 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 63 | 15 | 731 |
| SVG | 1 | 0 | 0 | 288 |
| PO File | 1 | 66 | 68 | 188 |
| CSS | 3 | 6 | 15 | 48 |
| JavaScript | 3 | 2 | 15 | 12 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.16 |
| Average class complexity | 51.00 |
| ▷ Minimum class complexity | 51.00 |
| ▷ Maximum class complexity | 51.00 |
| Average method complexity | 3.27 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 25.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 | 22 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 22 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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 Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
7 PNG files occupy 0.23MB with 0.09MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 26.96KB | 15.21KB | ▼ 43.60% |
| screenshot-5.png | 46.24KB | 26.34KB | ▼ 43.03% |
| screenshot-2.png | 35.57KB | 20.36KB | ▼ 42.77% |
| images/icon1_1.png | 41.11KB | 13.66KB | ▼ 66.77% |
| images/icon1.png | 8.49KB | 8.30KB | ▼ 2.21% |