Benchmarks
Plugin footprint 82% 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: ▼14.46MB] [CPU: ▼2,944,061.47ms] Passed 4 tests
Server-side resources used by wp_instasass
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.19 ▼58.09 | 7.11 ▼11,776,221.90 |
| Dashboard /wp-admin | 3.45 ▲0.06 | 53.56 ▼7.52 |
| Posts /wp-admin/edit.php | 3.57 ▲0.16 | 53.34 ▼1.57 |
| Add New Post /wp-admin/post-new.php | 6.03 ▲0.10 | 87.60 ▼14.88 |
| Media Library /wp-admin/upload.php | 3.38 ▲0.10 | 43.55 ▲9.15 |
| InstaSASS settings /wp-admin/options-general.php?page=fixcms | 3.32 | 36.57 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] 67% from 3 tests
Input-output and database impact of this plugin
Please fix the following
- The plugin illegally modified 2 files (0.00KB) outside of "wp-content/plugins/wp-instasass/" and "wp-content/uploads/"
- (new file) wp-content/themes/twentytwentyone/scss/0main.scss
- (new file) wp-content/themes/twentytwentyone/scss/css/.empty
Filesystem: 63 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for wp_instasass
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,793 ▲32 | 14.27 ▼0.39 | 1.78 ▼0.13 | 42.57 ▼15.38 |
| Dashboard /wp-admin | 2,196 ▲19 | 5.59 ▲0.01 | 87.83 ▼7.61 | 40.76 ▲1.78 |
| Posts /wp-admin/edit.php | 2,101 ▲4 | 2.00 ▲0.06 | 36.46 ▼2.87 | 33.25 ▼1.69 |
| Add New Post /wp-admin/post-new.php | 1,529 ▲3 | 23.42 ▼0.06 | 685.96 ▲21.99 | 51.26 ▼10.57 |
| Media Library /wp-admin/upload.php | 1,404 ▲4 | 4.21 ▼0.05 | 109.96 ▲12.26 | 46.88 ▲4.04 |
| InstaSASS settings /wp-admin/options-general.php?page=fixcms | 900 | 1.69 | 27.88 | 26.85 |
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
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Smoke test failed, please fix the following
- 5 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=fixcms
- > Notice in wp-content/plugins/wp-instasass/wp_instasass.php+386
Trying to access array offset on value of type bool
- 12 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=fixcms
- > Warning in wp-content/plugins/easy-age-verifier/lib/extras/wpApi.php+48
file_get_contents(): php_network_getaddresses: getaddrinfo failed: Name or service not known
- 12 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=fixcms
- > Warning in wp-content/plugins/easy-age-verifier/lib/extras/wpApi.php+48
file_get_contents(http://www.fillyourtaproom.com/wp-json/wp/v2/posts?per_page=10): failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known
SRP 0% 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
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/wp-instasass/wp_instasass.php
- 33× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/Validator/../../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/Validator/RpcFormatValidatorTest.php on line 5
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/ProcedureHandlerTest.php on line 5
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/Validator/../../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/Validator/UserValidatorTest.php on line 5
- > PHP Warning
require_once(wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/Response/../../vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/Response/ResponseBuilderTest.php on line 11
- > PHP Warning
require_once(wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/../vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/ServerProtocolTest.php on line 5
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/MiddlewareHandlerTest.php on line 7
- > PHP Fatal error
require_once(): Failed opening required 'vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-instasass/vendor/fixcms/instasass/example.php on line 7
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/Request/../../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/Request/RequestBuilderTest.php on line 5
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/ServerProtocolTest.php on line 5
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-instasass/vendor/fguillot/json-rpc/tests/HttpClientTest.php on line 5
- > 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 errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Please fix the following attributes:
- Donate link: Invalid URI ("")
- Tags: No valid plugin tags found
wp-instasass/wp_instasass.php 85% from 13 tests
This is the main PHP file of "wp_instasass" version 1.0.5, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please take the time to fix the following:
- Git Repository: A Git repository was detected inside this plugin
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-instasass.php" instead of "wp_instasass.php")
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
Everything looks great! No dangerous files found in this plugin3,267 lines of code in 56 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 49 | 741 | 1,466 | 2,865 |
| Markdown | 1 | 110 | 0 | 244 |
| JSON | 4 | 0 | 0 | 134 |
| YAML | 1 | 4 | 0 | 17 |
| XML | 1 | 0 | 0 | 7 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.23 |
| Average class complexity | 4.33 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 40.00 |
| Average method complexity | 1.81 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 7 | |
| Interfaces | 1 | |
| Traits | 0 | |
| Classes | 50 | |
| ▷ Abstract classes | 1 | 2.00% |
| ▷ Concrete classes | 49 | 98.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 229 | |
| ▷ Static methods | 13 | 5.68% |
| ▷ Public methods | 215 | 93.89% |
| ▷ Protected methods | 8 | 3.49% |
| ▷ Private methods | 6 | 2.62% |
| Functions | 44 | |
| ▷ Named functions | 10 | 22.73% |
| ▷ Anonymous functions | 34 | 77.27% |
| 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
PNG files should be compressed to save space and minimize bandwidth usage
No PNG files were detected