ApplicantPro 1.3.8
Does ApplicantPro work with WordPress 6.5.2 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: 28.53 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.5.2 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | 90+ |
| 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=2bfd27a719 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.320 s |
| Memory usage | 3.42 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.326 s |
| Memory usage | 3.42 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.378 s |
| Memory usage | 3.49 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.226 s |
| Memory usage | 3.38 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.370 s | 0.320 s | -0.050 s | 3.44 MiB | 3.47 MiB | + 34.48 KiB |
| /wp-admin/edit.php | 0.204 s | 0.178 s | -0.026 s | 3.46 MiB | 3.48 MiB | + 22.54 KiB |
| /wp-admin/post-new.php | 0.985 s | 0.744 s | -0.241 s | 5.59 MiB | 5.65 MiB | + 58.77 KiB |
| /wp-admin/upload.php | 0.600 s | 0.573 s | -0.027 s | 3.38 MiB | 3.4 MiB | + 17.45 KiB |
| /wp-admin/options-writing.php | 0.219 s | 0.301 s | +0.082 s | 3.37 MiB | 3.38 MiB | + 9.66 KiB |
| /wp-admin/media-new.php | 0.293 s | 0.315 s | +0.022 s | 3.35 MiB | 3.38 MiB | + 29.27 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.188 s | 0.257 s | +0.069 s | 3.37 MiB | 3.4 MiB | + 34.44 KiB |
| /wp-admin/post-new.php?post_type=page | 0.560 s | 0.600 s | +0.040 s | 5.59 MiB | 5.64 MiB | + 54.34 KiB |
| /wp-admin/options-discussion.php | 0.311 s | 0.495 s | +0.184 s | 3.36 MiB | 3.38 MiB | + 19.45 KiB |
| /wp-admin/edit-comments.php | 0.225 s | 0.252 s | +0.027 s | 3.39 MiB | 3.41 MiB | + 17.11 KiB |
| / | 0.307 s | 0.222 s | -0.085 s | 3.37 MiB | 3.38 MiB | + 16.38 KiB |
| Average | 0.387 s | 0.387 s | -0.000 s | 3.79 MiB | 3.82 MiB | + 28.53 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.