Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼6.19ms] Passed 4 tests
A check of server-side resources used by Fancy Coming Soon & Maintenance Mode
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 41.77 ▼1.13 |
Dashboard /wp-admin | 3.38 ▲0.07 | 48.90 ▼3.18 |
Posts /wp-admin/edit.php | 3.43 ▲0.07 | 48.80 ▲0.79 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 88.99 ▼12.61 |
Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 35.69 ▼7.82 |
Server storage [IO: ▲1.23MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 18 new files
Database: no new tables, 7 new options
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
fancy_coming_soon_uses_option |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Fancy Coming Soon & Maintenance Mode
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,809 ▲48 | 14.38 ▼0.01 | 1.67 ▼0.34 | 43.69 ▲0.31 |
Dashboard /wp-admin | 2,199 ▲28 | 5.56 ▼0.07 | 89.83 ▲1.86 | 40.57 ▼7.54 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 2.04 ▲0.04 | 36.96 ▼0.77 | 34.79 ▲0.63 |
Add New Post /wp-admin/post-new.php | 1,534 ▲8 | 23.17 ▲5.62 | 663.22 ▼21.71 | 54.49 ▼1.89 |
Media Library /wp-admin/upload.php | 1,401 ▲1 | 4.17 ▲0.02 | 97.56 ▼19.39 | 44.27 ▼5.63 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_recent-posts
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- fancy_coming_soon_uses_option
- can_compress_scripts
- widget_theysaidso_widget
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 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 2× 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/fancy-coming-soon-maintenance-mode/templates/fancy-customizer.php:441
- > PHP Fatal error
Uncaught Error: Call to undefined function bloginfo() in wp-content/plugins/fancy-coming-soon-maintenance-mode/templates/fancy-template.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Screenshots: These screenshots need descriptions #2, #3 in fancy-coming-soon-maintenance-mode/assets to your readme.txt
- Contributors: Contributors not specified
fancy-coming-soon-maintenance-mode/fancy-coming-soon.php 77% from 13 tests
The primary PHP file in "Fancy Coming Soon & Maintenance Mode" version 1.4.4 is used by WordPress to initiate all plugin functionality
Please make the necessary changes and fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("fancy-coming-soon-maintenance-mode.php" instead of "fancy-coming-soon.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Description: The description should be shorter than 140 characters (currently 229 characters long)
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
Everything looks great! No dangerous files found in this plugin3,155 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
SVG | 1 | 0 | 3 | 2,227 |
PHP | 5 | 184 | 172 | 543 |
CSS | 1 | 202 | 66 | 381 |
JavaScript | 1 | 0 | 0 | 4 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.22 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 2.00 |
Average method complexity | 1.33 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 2.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 | 3 | |
▷ Static methods | 1 | 33.33% |
▷ Public methods | 2 | 66.67% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 33.33% |
Functions | 10 | |
▷ Named functions | 10 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
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 |
assets/images/favicon.png | 0.10KB | 0.08KB | ▼ 17.65% |
assets/images/logo.png | 0.43KB | 0.21KB | ▼ 50.11% |