Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼7.19ms] Passed 4 tests
This is a short check of server-side resources used by Metabox with API
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 45.14 ▼6.70 |
Dashboard /wp-admin | 3.31 ▲0.00 | 61.96 ▼5.72 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 62.26 ▲2.30 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 95.04 ▼16.74 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 42.22 ▲0.39 |
Server storage [IO: ▲0.89MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 14 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Metabox with API
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,814 ▲53 | 14.34 ▼0.01 | 2.20 ▲0.49 | 42.87 ▼1.61 |
Dashboard /wp-admin | 2,192 ▲12 | 5.58 ▼0.07 | 91.29 ▼9.21 | 41.92 ▼1.24 |
Posts /wp-admin/edit.php | 2,103 ▲3 | 2.01 ▼0.01 | 40.82 ▲2.11 | 36.04 ▲1.52 |
Add New Post /wp-admin/post-new.php | 1,528 ▲2 | 23.02 ▼0.57 | 696.10 ▲10.13 | 51.98 ▼1.19 |
Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.19 ▼0.00 | 103.01 ▼3.15 | 45.50 ▼0.52 |
Uninstaller [IO: ▲0.89MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following itemsZombie WordPress options were found after uninstall: 6 options
- Uninstaller has failed for this plugin, leaving 14 files (0.89MB) in the plugin directory
- (new file) data/product.json
- (new file) screenshot-3.png
- (new file) screenshot-2.png
- (new file) css/metaboxapi.css
- (new file) screenshot-1.png
- (new file) metabox-with-api.php
- (new file) js/metaboxapi.js
- (new file) data/category.json
- (new file) LICENSE.txt
- (new file) readme.txt
- ...
- 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 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following items
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/metabox-with-api/metabox-with-api.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
6 plugin tags: custom metabox, data fetch, category api, data capture, product api...
metabox-with-api/metabox-with-api.php 92% from 13 tests
The primary PHP file in "Metabox with API" version 1.0 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 259 characters long)
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 detected536 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 86 | 78 | 384 |
JSON | 2 | 0 | 0 | 84 |
JavaScript | 1 | 4 | 0 | 44 |
CSS | 1 | 4 | 5 | 24 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.28 |
Average class complexity | 47.00 |
▷ Minimum class complexity | 47.00 |
▷ Maximum class complexity | 47.00 |
Average method complexity | 3.71 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 13.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 | 17 | |
▷ Static methods | 7 | 41.18% |
▷ Public methods | 17 | 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 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
7 PNG files occupy 0.85MB with 0.62MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-5.png | 156.83KB | 38.02KB | ▼ 75.75% |
screenshot-1.png | 93.19KB | 26.69KB | ▼ 71.36% |
screenshot-3.png | 154.39KB | 36.61KB | ▼ 76.29% |
screenshot-2.png | 128.22KB | 38.32KB | ▼ 70.11% |
screenshot-6.png | 163.35KB | 43.58KB | ▼ 73.32% |