Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼1.63ms] Passed 4 tests
This is a short check of server-side resources used by WP jQuery Pager
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 37.87 ▼0.35 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 46.12 ▼0.37 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.35 ▼2.91 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 97.71 ▼1.70 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.16 ▼1.55 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 11 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP jQuery Pager
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.74 ▲0.37 | 1.94 ▲0.18 | 44.27 ▲2.59 |
| Dashboard /wp-admin | 2,206 ▲63 | 5.83 ▲0.18 | 97.10 ▼1.90 | 38.17 ▼5.83 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.00 ▼0.00 | 38.51 ▲0.78 | 34.48 ▲0.33 |
| Add New Post /wp-admin/post-new.php | 1,542 ▲14 | 18.42 ▲0.27 | 646.70 ▼7.63 | 56.22 ▼8.71 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.22 ▲0.05 | 107.47 ▲4.64 | 47.09 ▲0.45 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/wp-jquery-pdf-paged/assets/views/output-view.php
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Notice
Undefined variable: imgs in wp-content/plugins/wp-jquery-pdf-paged/assets/views/output-view.php on line 7
- > PHP Warning
Invalid argument supplied for foreach() in wp-content/plugins/wp-jquery-pdf-paged/assets/views/output-view.php on line 7
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_die() in wp-content/plugins/wp-jquery-pdf-paged/wp-jquery-paged.php:32
- > PHP Notice
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
8 plugin tags: image, book, gallery, pager, magazine...
wp-jquery-pdf-paged/wp-jquery-paged.php 92% from 13 tests
"WP jQuery Pager" version 1.4.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("wp-jquery-pdf-paged.php" instead of "wp-jquery-paged.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin454 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 1 | 67 | 15 | 322 |
| PHP | 2 | 18 | 23 | 70 |
| JavaScript | 2 | 11 | 50 | 62 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 3.00 |
| Average method complexity | 1.40 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 5 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 2 | 40.00% |
| ▷ Protected methods | 3 | 60.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/button.png | 8.68KB | 3.29KB | ▼ 62.07% |