Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼1.84MB] [CPU: ▼64.43ms] Passed 4 tests
An overview of server-side resources used by WP QRecipeWriter
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.15 ▼1.31 | 5.00 ▼40.88 |
Dashboard /wp-admin | 2.17 ▼1.17 | 5.64 ▼61.18 |
Posts /wp-admin/edit.php | 2.17 ▼1.18 | 5.71 ▼59.37 |
Add New Post /wp-admin/post-new.php | 2.17 ▼3.71 | 6.49 ▼96.29 |
Media Library /wp-admin/upload.php | 2.17 ▼1.05 | 7.10 ▼29.65 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for WP QRecipeWriter
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,806 ▲35 | 13.22 ▼1.15 | 1.56 ▼0.33 | 47.25 ▲2.10 |
Dashboard /wp-admin | 2,205 ▲14 | 5.81 ▼0.07 | 99.77 ▼2.82 | 42.01 ▲0.45 |
Posts /wp-admin/edit.php | 2,094 ▲2 | 2.06 ▲0.07 | 38.06 ▼3.33 | 35.16 ▼1.53 |
Add New Post /wp-admin/post-new.php | 1,530 ▲16 | 23.17 ▲5.40 | 689.68 ▼20.16 | 61.21 ▲5.10 |
Media Library /wp-admin/upload.php | 1,387 ▼1 | 4.19 ▼0.00 | 100.56 ▼16.57 | 44.02 ▼7.01 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- This plugin cannot be uninstalled
- > User notice in wp-includes/functions.php+5905
Function wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the qrecipewriter_style handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
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
Everything seems fine, however this is by no means an exhaustive test
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 fix the following items
- 4× PHP files trigger server errors when accessed directly:
- > PHP Warning
Use of undefined constant WP_CONTENT_DIR - assumed 'WP_CONTENT_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-qrecipewriter/api.php on line 3
- > PHP Warning
Use of undefined constant WP_CONTENT_DIR - assumed 'WP_CONTENT_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-qrecipewriter/api.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-qrecipewriter/api.php:340
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-qrecipewriter/api.php:340
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
3 plugin tags: api, recipes, cooking
wp-qrecipewriter/index.php 92% from 13 tests
The principal PHP file in "WP QRecipeWriter" v. 0.1 is loaded by WordPress automatically on each request
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-qrecipewriter.php" instead of "index.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
There were no executable files found in this plugin338 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 54 | 22 | 298 |
CSS | 1 | 5 | 0 | 23 |
Markdown | 1 | 8 | 0 | 17 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.32 |
Average class complexity | 6.00 |
▷ Minimum class complexity | 6.00 |
▷ Maximum class complexity | 6.00 |
Average method complexity | 1.83 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.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 | 6 | |
▷ Static methods | 6 | 100.00% |
▷ Public methods | 6 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 6 | |
▷ Named functions | 4 | 66.67% |
▷ Anonymous functions | 2 | 33.33% |
Constants | 1 | |
▷ Global constants | 1 | 100.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
No PNG images were found in this plugin