Parse.ly 3.17.0
Does Parse.ly work with WordPress 6.8 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.46 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.038 seconds
The average page load time increased by this amount after activating the plugin.
Environment
| WordPress version | 6.8 |
|---|---|
| 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=d1a6ecbed7 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.323 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.468 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.287 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.343 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.328 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.284 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.669 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.340 s | 0.536 s | +0.196 s | 3.51 MiB | 3.67 MiB | + 166.85 KiB |
| /wp-admin/edit.php | 0.230 s | 0.292 s | +0.062 s | 3.57 MiB | 3.76 MiB | + 194.6 KiB |
| /wp-admin/post-new.php | 0.879 s | 1.060 s | +0.181 s | 6.06 MiB | 6.42 MiB | + 369.87 KiB |
| /wp-admin/upload.php | 0.646 s | 0.400 s | -0.246 s | 3.52 MiB | 3.67 MiB | + 151.82 KiB |
| /wp-admin/options-writing.php | 0.253 s | 0.251 s | -0.002 s | 3.5 MiB | 3.65 MiB | + 157.06 KiB |
| /wp-admin/media-new.php | 0.298 s | 0.442 s | +0.144 s | 3.49 MiB | 3.65 MiB | + 165.26 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.232 s | 0.255 s | +0.023 s | 3.5 MiB | 3.67 MiB | + 170.43 KiB |
| /wp-admin/post-new.php?post_type=page | 0.671 s | 0.762 s | +0.091 s | 6.05 MiB | 6.41 MiB | + 364.77 KiB |
| /wp-admin/options-discussion.php | 0.308 s | 0.353 s | +0.045 s | 3.5 MiB | 3.65 MiB | + 152.94 KiB |
| /wp-admin/edit-comments.php | 0.240 s | 0.273 s | +0.033 s | 3.52 MiB | 3.67 MiB | + 153.06 KiB |
| / | 0.358 s | 0.244 s | -0.114 s | 3.43 MiB | 3.49 MiB | + 59.41 KiB |
| Average | 0.405 s | 0.443 s | +0.038 s | 3.97 MiB | 4.16 MiB | + 191.46 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.8% | 9,230 | 3,659 | 101 | |
| PHP | 39.3% | 7,588 | 7,165 | 99 | |
| Sass | 9.9% | 1,915 | 27 | 18 | |
| Markdown | 1.9% | 364 | 0 | 6 | |
| JSON | 0.6% | 109 | 0 | 4 | |
| YAML | 0.2% | 48 | 1 | 1 | |
| JavaScript | 0.2% | 43 | 10 | 11 | |
| CSS | 0.1% | 21 | 0 | 11 | |
| Total | 19,318 | 10,862 | 251 | ||
PHP Code Analysis | More results »
| Lines of code | 7,328 |
|---|---|
| Total complexity | 1,277 |
| 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 | 79 |
|---|---|
| Methods | 499 |
| 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
[18-Apr-2025 00:46:40 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