Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼6.41ms] Passed 4 tests
An overview of server-side resources used by SMNTCS Private Site
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.05 | 34.75 ▼0.02 |
Dashboard /wp-admin | 3.35 ▲0.00 | 44.04 ▼17.57 |
Posts /wp-admin/edit.php | 3.40 ▲0.04 | 48.12 ▲0.81 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 89.02 ▼8.64 |
Media Library /wp-admin/upload.php | 3.28 ▲0.04 | 33.99 ▲0.61 |
Server storage [IO: ▲0.36MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 13 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
widget_theysaidso_widget |
db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for SMNTCS Private Site
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.30 ▼1.03 | 4.74 ▲3.16 | 38.89 ▼0.37 |
Dashboard /wp-admin | 2,203 ▲15 | 5.77 ▼0.09 | 99.50 ▼5.37 | 40.32 ▼5.27 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.04 ▲0.00 | 39.43 ▲1.49 | 34.78 ▼1.45 |
Add New Post /wp-admin/post-new.php | 1,535 ▲16 | 23.06 ▼0.53 | 670.84 ▲4.79 | 49.80 ▼5.40 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.28 ▲0.11 | 96.66 ▼3.51 | 43.98 ▲1.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_head() in wp-content/plugins/smntcs-private-site/template/private-site.php:9
- > 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 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that require attention:
- Screenshots: These screenshots lack descriptions #1, #2 in smntcs-private-site/assets to your readme.txt
smntcs-private-site/smntcs-smntcs-private-site.php 85% from 13 tests
The entry point to "SMNTCS Private Site" version 1.8 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("smntcs-private-site.php" instead of "smntcs-smntcs-private-site.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected4,825 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 1 | 0 | 0 | 4,549 |
PHP | 2 | 25 | 44 | 178 |
XML | 1 | 14 | 14 | 50 |
Markdown | 1 | 23 | 0 | 35 |
YAML | 1 | 0 | 0 | 9 |
JavaScript | 1 | 0 | 2 | 4 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.14 |
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 | 4 | |
▷ Named functions | 4 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected