Parse.ly 3.18.1
Does Parse.ly work with WordPress 6.8.1 and PHP 8.1.12? A smoke test was performed on .
Summary
Errors
| 1 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 191.66 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.8.1 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 1,000+ |
| WordPress.org page | https://wordpress.org/plugins/wp-parsely/ |
| Badges |
|
Pages 7
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=wp-parsely%2Fwp-parsely.php&plugin_status=all&paged=1&s&_wpnonce=50f805939c |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.334 s |
| Memory usage | 3.89 MiB |
| JS errors | None |
| Resource errors | None |
Settings → Parse.ly
| URL | /wp-admin/options-general.php?page=parsely |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.461 s |
| Memory usage | 3.7 MiB |
| JS errors | None |
| Resource errors | None |
Settings → Parse.ly → Content Helper
| URL | /wp-admin/options-general.php?page=parsely |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 0.367 s |
| Memory usage | 3.67 MiB |
| JS errors | None |
| Resource errors | None |
Settings → Parse.ly → Recrawl
| URL | /wp-admin/options-general.php?page=parsely |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 0.316 s |
| Memory usage | 3.67 MiB |
| JS errors | None |
| Resource errors | None |
Settings → Parse.ly → Advanced
| URL | /wp-admin/options-general.php?page=parsely |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 0.318 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.254 s |
| Memory usage | 3.49 MiB |
| JS errors | None |
| Resource errors | None |
Widgets ‹ Test site — WordPress
| URL | /wp-admin/widgets.php |
|---|---|
| Aspect | new-sidebar-widgets |
| HTTP status | 200 |
| Load time | 1.483 s |
| Memory usage | 5.99 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.362 s | 0.478 s | +0.116 s | 3.51 MiB | 3.67 MiB | + 166.82 KiB |
| /wp-admin/edit.php | 0.200 s | 0.280 s | +0.080 s | 3.57 MiB | 3.76 MiB | + 193.88 KiB |
| /wp-admin/post-new.php | 0.823 s | 0.987 s | +0.164 s | 6.06 MiB | 6.42 MiB | + 371.34 KiB |
| /wp-admin/upload.php | 0.766 s | 0.388 s | -0.378 s | 3.52 MiB | 3.67 MiB | + 151.82 KiB |
| /wp-admin/options-writing.php | 0.223 s | 0.231 s | +0.008 s | 3.5 MiB | 3.65 MiB | + 157.06 KiB |
| /wp-admin/media-new.php | 0.276 s | 0.382 s | +0.106 s | 3.49 MiB | 3.65 MiB | + 165.26 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.191 s | 0.232 s | +0.041 s | 3.5 MiB | 3.67 MiB | + 170.43 KiB |
| /wp-admin/post-new.php?post_type=page | 0.606 s | 0.742 s | +0.136 s | 6.05 MiB | 6.41 MiB | + 366.23 KiB |
| /wp-admin/options-discussion.php | 0.440 s | 0.325 s | -0.115 s | 3.5 MiB | 3.65 MiB | + 152.94 KiB |
| /wp-admin/edit-comments.php | 0.294 s | 0.241 s | -0.053 s | 3.52 MiB | 3.67 MiB | + 153.06 KiB |
| / | 0.307 s | 0.207 s | -0.100 s | 3.43 MiB | 3.49 MiB | + 59.41 KiB |
| Average | 0.408 s | 0.408 s | +0.000 s | 3.97 MiB | 4.16 MiB | + 191.66 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 | |
|---|---|---|---|---|---|
| TypeScript | 47.9% | 9,442 | 3,759 | 105 | |
| PHP | 39.2% | 7,736 | 7,248 | 100 | |
| Sass | 10.0% | 1,967 | 27 | 19 | |
| Markdown | 1.8% | 364 | 0 | 6 | |
| JSON | 0.6% | 109 | 0 | 4 | |
| YAML | 0.2% | 48 | 1 | 1 | |
| JavaScript | 0.2% | 35 | 7 | 11 | |
| CSS | 0.1% | 21 | 0 | 11 | |
| Total | 19,722 | 11,042 | 257 | ||
PHP Code Analysis | More results »
| Lines of code | 7,476 |
|---|---|
| Total complexity | 1,302 |
| Median class complexity | 8.0 |
| Median method complexity | 1.0 |
| Most complex class | Parsely\UI\Settings_Page |
| Most complex function | Parsely\UI\Settings_Page::validate_recrawl_section() |
| Classes | 80 |
|---|---|
| Methods | 503 |
| Functions | 13 |
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.
Options wp_options 2
- parsely
- widget_parsely_recommended_widget
Custom Post Types 1
| ID | Name |
|---|---|
| parsely_smart_link | Smart Links |
Sidebar Widgets 1
| ID | Name |
|---|---|
| parsely_recommended_widget | Parse.ly Recommended Widget |
PHP Error Log 1 lines
[02-May-2025 23:48:22 UTC] PHP Notice: Function wp_enqueue_script() was called <strong>incorrectly</strong>. "wp-editor" script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets). 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 5.8.0.) in /wp-includes/functions.php on line 6121