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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼143.18ms] Passed 4 tests
Analyzing server-side resources used by Vintage.js
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.86 ▲0.03 | 46.73 ▲8.82 |
Dashboard /wp-admin | 3.08 ▲0.03 | 60.36 ▼1.23 |
Posts /wp-admin/edit.php | 3.14 ▲0.03 | 42.79 ▼8.39 |
Add New Post /wp-admin/post-new.php | 5.44 ▲0.01 | 95.68 ▼557.47 |
Media Library /wp-admin/upload.php | 3.03 ▲0.03 | 34.29 ▼5.62 |
Vintage JS /wp-admin/themes.php?page=vintagejs | 3.00 | 39.52 |
Server storage [IO: ▲0.40MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 12 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
An overview of browser requirements for Vintage.js
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,824 ▲252 | 16.32 ▲0.76 | 20.92 ▲9.54 | 46.05 ▼3.27 |
Dashboard /wp-admin | 2,974 ▲47 | 5.88 ▼0.06 | 138.66 ▼35.37 | 111.82 ▼9.95 |
Posts /wp-admin/edit.php | 2,746 ▲7 | 2.73 ▲0.01 | 69.42 ▼7.44 | 95.28 ▲6.78 |
Add New Post /wp-admin/post-new.php | 1,599 ▲18 | 18.75 ▲0.06 | 426.71 ▼13.80 | 110.99 ▼12.52 |
Media Library /wp-admin/upload.php | 1,817 ▲10 | 5.05 ▲0.02 | 165.28 ▼11.56 | 127.19 ▼2.21 |
Vintage JS /wp-admin/themes.php?page=vintagejs | 1,032 | 2.06 | 61.28 | 72.81 |
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
Uninstaller ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
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
Almost there! Just fix the following items
- 4× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Warning
require(WP_PLUGIN_DIR/vintagejs/admin/admin.php): failed to open stream: No such file or directory in wp-content/plugins/vintagejs/loader.php on line 11
- > PHP Fatal error
require(): Failed opening required 'WP_PLUGIN_DIR/vintagejs/admin/admin.php' (include_path='.:/usr/share/php') in wp-content/plugins/vintagejs/loader.php on line 11
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/vintagejs/admin/admin.php:2
- > PHP Warning
Use of undefined constant WP_PLUGIN_DIR - assumed 'WP_PLUGIN_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/vintagejs/loader.php on line 11
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% 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
These attributes need to be fixed:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== vintagejs ===
) - Screenshots: Add images for these screenshots: #1 (upload option), #2 (vintage image filter)
vintagejs/loader.php 92% from 13 tests
"Vintage.js" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("vintagejs.php" instead of "loader.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
There were no executable files found in this plugin245 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 42 | 16 | 130 |
JavaScript | 3 | 5 | 26 | 87 |
CSS | 1 | 0 | 0 | 28 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.15 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 14 | |
▷ Named functions | 14 | 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
3 PNG files occupy 0.36MB with 0.22MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 314.74KB | 115.18KB | ▼ 63.40% |
css/clock.png | 4.16KB | 1.64KB | ▼ 60.64% |
screenshot-1.png | 47.84KB | 18.42KB | ▼ 61.49% |