Does Inline Related Posts work with WordPress 6.4.3 and PHP 8.1.12? A smoke test was performed on .
No PHP errors, warnings or notices | |
3 | JavaScript exceptions |
All test pages loaded successfully | |
No resource errors |
Memory usage: 58.71 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.039 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 6.4.3 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 100,000+ |
WordPress.org page | https://wordpress.org/plugins/intelly-related-posts/ |
Badges |
|
URL | /wp-admin/options-general.php?page=intelly-related-posts |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=intelly-related-posts%2Findex.php&plugin_status=all&paged=1&s&_wpnonce=95b5a19fe7 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 2.950 s |
Memory usage | 3.4 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=intelly-related-posts |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.267 s |
Memory usage | 3.38 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=intelly-related-posts&tab=docs |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.154 s |
Memory usage | N/A |
JS errors |
|
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.969 s |
Memory usage | 3.4 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 0.625 s |
Memory usage | 5.45 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.396 s | 0.561 s | +0.165 s | 3.38 MiB | 3.46 MiB | + 82.34 KiB |
/wp-admin/edit.php | 0.223 s | 0.262 s | +0.039 s | 3.41 MiB | 3.49 MiB | + 86.54 KiB |
/wp-admin/post-new.php | 1.078 s | 1.134 s | +0.056 s | 5.46 MiB | 5.45 MiB | - 14.07 KiB |
/wp-admin/upload.php | 0.769 s | 0.433 s | -0.336 s | 3.33 MiB | 3.39 MiB | + 65.61 KiB |
/wp-admin/options-writing.php | 0.240 s | 0.238 s | -0.002 s | 3.32 MiB | 3.38 MiB | + 58.71 KiB |
/wp-admin/media-new.php | 0.318 s | 0.519 s | +0.201 s | 3.3 MiB | 3.37 MiB | + 78.31 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.237 s | 0.204 s | -0.033 s | 3.31 MiB | 3.4 MiB | + 85.96 KiB |
/wp-admin/post-new.php?post_type=page | 0.630 s | 1.027 s | +0.397 s | 5.45 MiB | 5.44 MiB | - 13.73 KiB |
/wp-admin/options-discussion.php | 0.330 s | 0.317 s | -0.013 s | 3.3 MiB | 3.37 MiB | + 68.34 KiB |
/wp-admin/edit-comments.php | 0.249 s | 0.280 s | +0.031 s | 3.34 MiB | 3.4 MiB | + 65.29 KiB |
/ | 0.286 s | 0.213 s | -0.073 s | 3.31 MiB | 3.39 MiB | + 82.45 KiB |
Average | 0.432 s | 0.472 s | +0.039 s | 3.72 MiB | 3.78 MiB | + 58.71 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 | 55.5% | 4,765 | 255 | 36 | |
SVG | 31.1% | 2,671 | 0 | 1 | |
JavaScript | 8.0% | 688 | 74 | 64 | |
HTML | 2.3% | 194 | 0 | 1 | |
CSS | 1.9% | 166 | 3 | 2 | |
PO File | 1.0% | 90 | 3 | 5 | |
JSON | 0.1% | 11 | 0 | 1 | |
Total | 8,585 | 335 | 110 |
Lines of code | 4,771 |
---|---|
Total complexity | 1,129 |
Median class complexity | 16.5 |
Median method complexity | 1.0 |
Most complex class | IRP_Utils |
Most complex function | IRP_HtmlTemplate::html() |
Classes | 26 |
---|---|
Methods | 309 |
Functions | 38 |
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.
wp_options
7{
"post": {
"irp_sectionid": {
"title": "Related Posts by IntellyWP",
"context": "side"
}
}
}
The log file is empty.