Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.16MB] [CPU: ▼9.22ms] Passed 4 tests
An overview of server-side resources used by Awesome Coming Soon
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.73 ▼0.73 | 12.17 ▼26.32 |
Dashboard /wp-admin | 3.34 ▲0.04 | 48.07 ▲1.41 |
Posts /wp-admin/edit.php | 3.43 ▲0.07 | 51.22 ▲1.57 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 78.67 ▼10.39 |
Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 35.55 ▼1.56 |
Server storage [IO: ▲0.77MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 24 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Awesome Coming Soon
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,982 ▲247 | 14.80 ▲0.05 | 1.91 ▲0.20 | 41.74 ▼5.50 |
Dashboard /wp-admin | 2,360 ▲172 | 6.45 ▲1.54 | 134.77 ▲23.50 | 40.07 ▼0.61 |
Posts /wp-admin/edit.php | 2,266 ▲177 | 3.42 ▲1.43 | 54.83 ▲9.55 | 34.35 ▼0.79 |
Add New Post /wp-admin/post-new.php | 1,531 ▲17 | 23.10 ▲5.69 | 643.13 ▼11.27 | 34.07 ▼26.77 |
Media Library /wp-admin/upload.php | 1,405 ▲17 | 4.16 ▼0.04 | 82.55 ▼12.37 | 41.37 ▼0.84 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% 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 no errors were found, this is by no means 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 take a closer look at the following
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/awesome-coming-soon/inc/acs-plugin-options.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/awesome-coming-soon/inc/acs-plugin-options.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
3 plugin tags: comingsoon, mantaince mode, landing page
awesome-coming-soon/awesome-coming-soon.php Passed 13 tests
The principal PHP file in "Awesome Coming Soon" v. 1.1 is loaded by WordPress automatically on each request
26 characters long description:
Flat Coming Soon WP Plugin
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
There were no executable files found in this plugin2,863 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 3 | 82 | 50 | 1,866 |
SVG | 1 | 0 | 0 | 504 |
PHP | 3 | 252 | 47 | 434 |
JavaScript | 2 | 20 | 21 | 59 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
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 | 13 | |
▷ Named functions | 13 | 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
6 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
inc/images/ico/favicon.png | 0.88KB | 0.36KB | ▼ 59.18% |
inc/images/bg-transparent.png | 0.20KB | 0.09KB | ▼ 51.98% |
inc/images/ico/apple-touch-icon-144.png | 2.69KB | 1.01KB | ▼ 62.28% |
inc/images/ico/apple-touch-icon-57.png | 1.25KB | 0.56KB | ▼ 55.09% |
inc/images/ico/apple-touch-icon-72.png | 1.51KB | 0.67KB | ▼ 55.46% |