Parse.ly 3.20.6
Does Parse.ly work with WordPress 6.8.2 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: 234.83 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.040 seconds
The average page load time increased by this amount after activating the plugin.
Environment
| WordPress version | 6.8.2 |
|---|---|
| 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=db296ad08b |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.348 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.451 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.401 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.413 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.368 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.242 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.549 s |
| Memory usage | 6.07 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.296 s | 0.476 s | +0.180 s | 3.51 MiB | 3.7 MiB | + 196.06 KiB |
| /wp-admin/edit.php | 0.188 s | 0.279 s | +0.091 s | 3.57 MiB | 3.79 MiB | + 223.11 KiB |
| /wp-admin/post-new.php | 0.754 s | 0.926 s | +0.172 s | 6.06 MiB | 6.53 MiB | + 484.81 KiB |
| /wp-admin/upload.php | 0.571 s | 0.367 s | -0.204 s | 3.52 MiB | 3.7 MiB | + 181.06 KiB |
| /wp-admin/options-writing.php | 0.193 s | 0.236 s | +0.043 s | 3.5 MiB | 3.68 MiB | + 186.3 KiB |
| /wp-admin/media-new.php | 0.272 s | 0.416 s | +0.144 s | 3.49 MiB | 3.68 MiB | + 194.5 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.220 s | 0.219 s | -0.001 s | 3.5 MiB | 3.7 MiB | + 199.67 KiB |
| /wp-admin/post-new.php?post_type=page | 0.644 s | 0.690 s | +0.046 s | 6.05 MiB | 6.52 MiB | + 480.65 KiB |
| /wp-admin/options-discussion.php | 0.274 s | 0.302 s | +0.028 s | 3.5 MiB | 3.68 MiB | + 182.18 KiB |
| /wp-admin/edit-comments.php | 0.197 s | 0.235 s | +0.038 s | 3.52 MiB | 3.7 MiB | + 182.3 KiB |
| / | 0.303 s | 0.206 s | -0.097 s | 3.43 MiB | 3.5 MiB | + 72.51 KiB |
| Average | 0.356 s | 0.396 s | +0.040 s | 3.97 MiB | 4.2 MiB | + 234.83 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.2% | 15,586 | 6,526 | 156 | |
| PHP | 34.5% | 10,111 | 8,951 | 115 | |
| 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,284 | 15,513 | 335 | ||
PHP Code Analysis | More results »
| Lines of code | 9,762 |
|---|---|
| Total complexity | 1,700 |
| 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 | 93 |
|---|---|
| Methods | 609 |
| 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
[22-Jul-2025 06:21:32 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