ApplicantPro 1.3.8
Does ApplicantPro work with WordPress 6.6.1 and PHP 8.1.12? A smoke test was performed on .
Summary
| No PHP errors, warnings or notices | |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors | |
| Looks good! No problems were detected. |
Memory usage: 42.01 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.
| WordPress version | 6.6.1 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | 60+ |
| WordPress.org page | https://wordpress.org/plugins/applicantpro/ |
| Badges |
|
Pages 4
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=applicantpro%2Fapplicantpro.php&plugin_status=all&paged=1&s&_wpnonce=9f4b9fdffe |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.209 s |
| Memory usage | 3.53 MiB |
| JS errors | None |
| Resource errors | None |
ApplicantPro
| URL | /wp-admin/admin.php?page=apppro_home |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.216 s |
| Memory usage | 3.49 MiB |
| JS errors | None |
| Resource errors | None |
ApplicantPro → Settings
| URL | /wp-admin/admin.php?page=apppro_settings |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.245 s |
| Memory usage | 3.52 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.170 s |
| Memory usage | 3.42 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.285 s | 0.264 s | -0.021 s | 3.47 MiB | 3.51 MiB | + 34.8 KiB |
| /wp-admin/edit.php | 0.179 s | 0.183 s | +0.004 s | 3.54 MiB | 3.56 MiB | + 22.95 KiB |
| /wp-admin/post-new.php | 0.668 s | 0.552 s | -0.116 s | 5.75 MiB | 5.81 MiB | + 55.07 KiB |
| /wp-admin/upload.php | 0.482 s | 0.341 s | -0.141 s | 3.49 MiB | 3.51 MiB | + 17.39 KiB |
| /wp-admin/options-writing.php | 0.177 s | 0.358 s | +0.181 s | 3.41 MiB | 3.49 MiB | + 80.2 KiB |
| /wp-admin/media-new.php | 0.202 s | 0.226 s | +0.024 s | 3.4 MiB | 3.49 MiB | + 93.59 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.158 s | 0.159 s | +0.001 s | 3.47 MiB | 3.51 MiB | + 40.25 KiB |
| /wp-admin/post-new.php?post_type=page | 0.524 s | 0.517 s | -0.007 s | 5.75 MiB | 5.8 MiB | + 54.66 KiB |
| /wp-admin/options-discussion.php | 0.214 s | 0.213 s | -0.001 s | 3.41 MiB | 3.49 MiB | + 81.88 KiB |
| /wp-admin/edit-comments.php | 0.189 s | 0.186 s | -0.003 s | 3.49 MiB | 3.51 MiB | + 17.38 KiB |
| / | 0.273 s | 0.172 s | -0.101 s | 3.45 MiB | 3.42 MiB | - 36.02 KiB |
| Average | 0.305 s | 0.288 s | -0.016 s | 3.88 MiB | 3.92 MiB | + 42.01 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 | |
|---|---|---|---|---|---|
| PHP | 51.8% | 5,428 | 175 | 10 | |
| SVG | 39.3% | 4,121 | 1 | 14 | |
| CSS | 8.1% | 853 | 25 | 5 | |
| JavaScript | 0.7% | 76 | 5 | 2 | |
| Total | 10,478 | 206 | 31 | ||
PHP Code Analysis | More results »
| Lines of code | 245 |
|---|---|
| Total complexity | 65 |
| Median class complexity | 23.0 |
| Median method complexity | 2.0 |
| Most complex class | apppro_Public |
| Most complex function | apppro_Public::search_jobs() |
| Classes | 2 |
|---|---|
| Methods | 15 |
| Functions | 9 |
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 1
- show_job_location
PHP Error Log
The log file is empty.