Food Business Gross Profit Calculator 1.1
Does "Food Business Gross Profit Calculator" work with WordPress 5.8.2 and PHP 7.4.8? A smoke test was performed on .
Summary
Errors
| 21 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 32.16 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
insignificant.
The plugin didn't make the site noticeably slower.
Environment
| WordPress version | 5.8.2 |
|---|---|
| PHP version | 7.4.8 |
| MySQL version | 8.0.21 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | <10 |
| WordPress.org page | https://wordpress.org/plugins/food-business-gross-profit-calculator/ |
| Badges |
|
Pages 8
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=food-business-gross-profit-calculator%2Fsc-recipe-calc.php&plugin_status=all&paged=1&s&_wpnonce=1f2fa1bffb |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.346 s |
| Memory usage | 3.08 MiB |
| JS errors | None |
| Resource errors | None |
Recipes
| URL | /wp-admin/edit.php?post_type=screcipe |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.158 s |
| Memory usage | 3.11 MiB |
| JS errors | None |
| Resource errors | None |
Recipes → Add New
| URL | /wp-admin/post-new.php?post_type=screcipe |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.940 s |
| Memory usage | 3.28 MiB |
| JS errors | None |
| Resource errors | None |
Recipes → Categories
| URL | /wp-admin/edit-tags.php?taxonomy=category&post_type=screcipe |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.189 s |
| Memory usage | 3.08 MiB |
| JS errors | None |
| Resource errors | None |
Recipes → Tags
| URL | /wp-admin/edit-tags.php?taxonomy=post_tag&post_type=screcipe |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.147 s |
| Memory usage | 3.07 MiB |
| JS errors | None |
| Resource errors | None |
Recipes → Recipe Categories
| URL | /wp-admin/edit-tags.php?taxonomy=screcipe_categories&post_type=screcipe |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.147 s |
| Memory usage | 3.07 MiB |
| JS errors | None |
| Resource errors | None |
Recipes → How To Use
| URL | /wp-admin/edit.php?post_type=screcipe&page=screcipe_info |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.608 s |
| Memory usage | 3.07 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.270 s |
| Memory usage | 2.94 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.297 s | 0.446 s | +0.149 s | 3.08 MiB | 3.12 MiB | + 38.32 KiB |
| /wp-admin/edit.php | 0.178 s | 0.166 s | -0.012 s | 3.11 MiB | 3.15 MiB | + 38.32 KiB |
| /wp-admin/post-new.php | 1.163 s | 1.070 s | -0.093 s | 5.27 MiB | 5.31 MiB | + 42.68 KiB |
| /wp-admin/upload.php | 0.594 s | 0.504 s | -0.090 s | 3.03 MiB | 3.07 MiB | + 37.79 KiB |
| /wp-admin/options-writing.php | 0.137 s | 0.138 s | +0.001 s | 3.02 MiB | 3.05 MiB | + 21.77 KiB |
| /wp-admin/media-new.php | 0.373 s | 0.175 s | -0.198 s | 3.01 MiB | 3.04 MiB | + 37.96 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.177 s | 0.169 s | -0.008 s | 3.04 MiB | 3.08 MiB | + 38.87 KiB |
| /wp-admin/post-new.php?post_type=page | 1.082 s | 0.930 s | -0.152 s | 5.26 MiB | 5.3 MiB | + 38.27 KiB |
| /wp-admin/options-discussion.php | 0.217 s | 0.212 s | -0.005 s | 3 MiB | 3.04 MiB | + 38.27 KiB |
| /wp-admin/edit-comments.php | 0.200 s | 0.185 s | -0.015 s | 3.04 MiB | 3.08 MiB | + 37.17 KiB |
| / | 0.254 s | 0.192 s | -0.062 s | 2.96 MiB | 2.94 MiB | - 15.63 KiB |
| Average | 0.425 s | 0.381 s | -0.044 s | 3.44 MiB | 3.47 MiB | + 32.16 KiB |
Code Statistics
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| CSS | 52.2% | 815 | 63 | 3 | |
| PHP | 28.7% | 449 | 90 | 7 | |
| JavaScript | 19.1% | 298 | 8 | 1 | |
| Total | 1,562 | 161 | 11 | ||
PHP Code Analysis | More results »
| Lines of code | 247 |
|---|---|
| Total complexity | 55 |
| Median class complexity | 5.0 |
| Median method complexity | 1.0 |
| Most complex class | SCRecipeHelper |
| Most complex function | SCRecipeHelper::screcipe_action() |
| Classes | 5 |
|---|---|
| Methods | 21 |
| Functions | 0 |
Additions
Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.
Custom Post Types 1
| ID | Name |
|---|---|
| screcipe | Recipes |
PHP Error Log 21 lines
[25-Nov-2021 12:22:46 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:46 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:47 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:47 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:48 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:48 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:49 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:49 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:51 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:51 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:51 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:53 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:54 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:54 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:54 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:54 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:56 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:56 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:57 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:57 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663
[25-Nov-2021 12:22:57 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.3.0.) in /wp-includes/functions.php on line 5663