Does Opti Marketing work with WordPress 6.8.3 and PHP 8.1.12? A smoke test was performed on .
| 5 | PHP notices |
| No JavaScript exceptions | |
| 1 | Page failed to load
|
| No resource errors |
Memory usage: 230.6 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.264 seconds
The average page load time increased by this amount after activating the plugin.
| WordPress version | 6.8.3 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | <10 |
| WordPress.org page | https://wordpress.org/plugins/opti-marketing/ |
| Badges |
|
| URL | /wp-admin/admin.php?page=optimarketing |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=opti-marketing%2Fopti-marketing.php&plugin_status=all&paged=1&s&_wpnonce=0680fddf5f |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 1.067 s |
| Memory usage | 3.72 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/admin.php?page=optimarketing |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.463 s |
| Memory usage | 3.72 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/admin.php?page=logs |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.426 s |
| Memory usage | 3.72 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 404 |
| Load time | 0.045 s |
| Memory usage | N/A |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/post-new.php |
|---|---|
| Aspect | new-meta-boxes |
| HTTP status | 200 |
| Load time | 0.733 s |
| Memory usage | 6.3 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.340 s | 0.755 s | +0.415 s | 3.51 MiB | 3.74 MiB | + 243.48 KiB |
| /wp-admin/edit.php | 0.216 s | 0.596 s | +0.380 s | 3.57 MiB | 3.8 MiB | + 234.85 KiB |
| /wp-admin/post-new.php | 0.782 s | 0.764 s | -0.018 s | 6.06 MiB | 6.3 MiB | + 247.44 KiB |
| /wp-admin/upload.php | 0.767 s | 0.794 s | +0.027 s | 3.52 MiB | 3.73 MiB | + 215.15 KiB |
| /wp-admin/options-writing.php | 0.223 s | 0.663 s | +0.440 s | 3.5 MiB | 3.72 MiB | + 220.39 KiB |
| /wp-admin/media-new.php | 0.273 s | 0.537 s | +0.264 s | 3.49 MiB | 3.72 MiB | + 228.59 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.243 s | 0.497 s | +0.254 s | 3.5 MiB | 3.74 MiB | + 239.57 KiB |
| /wp-admin/post-new.php?post_type=page | 0.613 s | 0.674 s | +0.061 s | 6.05 MiB | 6.29 MiB | + 242.65 KiB |
| /wp-admin/options-discussion.php | 0.278 s | 0.757 s | +0.479 s | 3.5 MiB | 3.72 MiB | + 217.52 KiB |
| /wp-admin/edit-comments.php | 0.214 s | 0.548 s | +0.334 s | 3.52 MiB | 3.73 MiB | + 216.39 KiB |
| Average | 0.395 s | 0.658 s | +0.264 s | 4.02 MiB | 4.25 MiB | + 230.6 KiB |
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 | |
|---|---|---|---|---|---|
| PHP | 87.8% | 2,709 | 288 | 24 | |
| JavaScript | 9.1% | 281 | 3 | 13 | |
| XSLT | 2.5% | 77 | 0 | 1 | |
| SVG | 0.5% | 15 | 1 | 1 | |
| CSS | 0.1% | 4 | 0 | 1 | |
| Total | 3,086 | 292 | 40 | ||
| Lines of code | 2,689 |
|---|---|
| Total complexity | 437 |
| Median class complexity | 6.0 |
| Median method complexity | 1.0 |
| Most complex class | ConstroleSql |
| Most complex function | save_token() |
| Classes | 11 |
|---|---|
| Methods | 47 |
| Functions | 104 |
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.
{
"post": {
"optimization_tips_meta_box": {
"title": "Dicas de Otimiza\u00e7\u00e3o",
"context": "normal"
}
}
}[31-Oct-2025 04:02:13 UTC] PHP Notice: Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6121
[31-Oct-2025 04:02:13 UTC] PHP Notice: Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6121
[31-Oct-2025 04:02:13 UTC] PHP Notice: Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6121
[31-Oct-2025 04:02:13 UTC] PHP Notice: Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6121
[31-Oct-2025 04:02:13 UTC] PHP Notice: Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6121