Parse.ly 3.20.4
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: 227.09 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=220fd5379d |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.339 s |
| Memory usage | 3.98 MiB |
| JS errors | None |
| Resource errors | None |
Parse.ly
| URL | /wp-admin/admin.php?page=parsely-settings |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.530 s |
| Memory usage | 3.7 MiB |
| JS errors | None |
| Resource errors | None |
Parse.ly → Content Intelligence
| URL | /wp-admin/admin.php?page=parsely-settings |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 0.446 s |
| Memory usage | 3.7 MiB |
| JS errors | None |
| Resource errors | None |
Parse.ly → Recrawl
| URL | /wp-admin/admin.php?page=parsely-settings |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 0.423 s |
| Memory usage | 3.7 MiB |
| JS errors | None |
| Resource errors | None |
Parse.ly → Advanced
| URL | /wp-admin/admin.php?page=parsely-settings |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 0.406 s |
| Memory usage | 3.7 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.239 s |
| Memory usage | 3.5 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.583 s |
| Memory usage | 6.06 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.333 s | 0.477 s | +0.144 s | 3.51 MiB | 3.7 MiB | + 195.34 KiB |
| /wp-admin/edit.php | 0.223 s | 0.279 s | +0.056 s | 3.57 MiB | 3.79 MiB | + 222.38 KiB |
| /wp-admin/post-new.php | 0.866 s | 0.975 s | +0.109 s | 6.06 MiB | 6.53 MiB | + 479.09 KiB |
| /wp-admin/upload.php | 0.780 s | 0.388 s | -0.392 s | 3.52 MiB | 3.7 MiB | + 180.34 KiB |
| /wp-admin/options-writing.php | 0.236 s | 0.234 s | -0.002 s | 3.5 MiB | 3.68 MiB | + 185.58 KiB |
| /wp-admin/media-new.php | 0.316 s | 0.420 s | +0.104 s | 3.49 MiB | 3.68 MiB | + 193.77 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.195 s | 0.210 s | +0.015 s | 3.5 MiB | 3.7 MiB | + 198.95 KiB |
| /wp-admin/post-new.php?post_type=page | 0.754 s | 0.747 s | -0.007 s | 6.05 MiB | 6.51 MiB | + 474.94 KiB |
| /wp-admin/options-discussion.php | 0.428 s | 0.324 s | -0.104 s | 3.5 MiB | 3.68 MiB | + 181.45 KiB |
| /wp-admin/edit-comments.php | 0.257 s | 0.254 s | -0.003 s | 3.52 MiB | 3.7 MiB | + 181.58 KiB |
| / | 0.326 s | 0.217 s | -0.109 s | 3.5 MiB | 3.5 MiB | + 4.58 KiB |
| Average | 0.429 s | 0.411 s | -0.017 s | 3.98 MiB | 4.2 MiB | + 227.09 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 | 53.3% | 15,565 | 6,521 | 156 | |
| PHP | 34.4% | 10,064 | 8,885 | 113 | |
| Sass | 10.2% | 2,981 | 28 | 28 | |
| Markdown | 1.3% | 367 | 0 | 6 | |
| JSON | 0.4% | 114 | 0 | 4 | |
| YAML | 0.2% | 48 | 1 | 1 | |
| JavaScript | 0.2% | 44 | 7 | 12 | |
| CSS | 0.1% | 33 | 0 | 13 | |
| Total | 29,216 | 15,442 | 333 | ||
PHP Code Analysis | More results »
| Lines of code | 9,715 |
|---|---|
| Total complexity | 1,693 |
| Median class complexity | 8.0 |
| Median method complexity | 1.0 |
| Most complex class | Parsely\UI\Settings_Page |
| Most complex function | Parsely\Models\Inbound_Smart_Link::get_paragraph() |
| Classes | 91 |
|---|---|
| Methods | 604 |
| Functions | 15 |
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 3
- parsely
- parsely_data_schema_version
- 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
[08-Jul-2025 13:50:36 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