Food Business Gross Profit Calculator 1.1
Does "Food Business Gross Profit Calculator" work with WordPress 6.0.1 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: 33.68 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 | 6.0.1 |
|---|---|
| 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=948d10393c |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.246 s |
| Memory usage | 3.73 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.182 s |
| Memory usage | 3.77 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.968 s |
| Memory usage | 3.87 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.206 s |
| Memory usage | 3.73 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.159 s |
| Memory usage | 3.72 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.164 s |
| Memory usage | 3.72 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.488 s |
| Memory usage | 3.67 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.233 s |
| Memory usage | 3.59 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.397 s | 0.278 s | -0.119 s | 3.72 MiB | 3.76 MiB | + 39.38 KiB |
| /wp-admin/edit.php | 0.196 s | 0.182 s | -0.014 s | 3.75 MiB | 3.79 MiB | + 39.38 KiB |
| /wp-admin/post-new.php | 0.740 s | 0.859 s | +0.119 s | 5.55 MiB | 5.59 MiB | + 47.73 KiB |
| /wp-admin/upload.php | 0.391 s | 0.401 s | +0.010 s | 3.68 MiB | 3.72 MiB | + 38.84 KiB |
| /wp-admin/options-writing.php | 0.155 s | 0.225 s | +0.070 s | 3.62 MiB | 3.63 MiB | + 18.75 KiB |
| /wp-admin/media-new.php | 0.451 s | 0.179 s | -0.272 s | 3.66 MiB | 3.7 MiB | + 39.02 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.177 s | 0.184 s | +0.007 s | 3.69 MiB | 3.73 MiB | + 39.92 KiB |
| /wp-admin/post-new.php?post_type=page | 0.815 s | 0.629 s | -0.186 s | 5.54 MiB | 5.58 MiB | + 43.32 KiB |
| /wp-admin/options-discussion.php | 0.214 s | 0.203 s | -0.011 s | 3.6 MiB | 3.63 MiB | + 39.33 KiB |
| /wp-admin/edit-comments.php | 0.205 s | 0.195 s | -0.010 s | 3.69 MiB | 3.73 MiB | + 38.23 KiB |
| / | 0.262 s | 0.253 s | -0.009 s | 3.6 MiB | 3.59 MiB | - 13.41 KiB |
| Average | 0.364 s | 0.326 s | -0.038 s | 4.01 MiB | 4.04 MiB | + 33.68 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
[29-Jul-2022 23:52:37 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:38 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:38 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:39 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:41 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:41 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:42 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:43 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:45 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:46 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:46 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:48 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:48 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:49 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:49 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:49 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:51 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:51 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:52 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:52 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831
[29-Jul-2022 23:52:52 UTC] PHP Notice: Function add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be numeric 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 5831