Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼3.08ms] Passed 4 tests
Server-side resources used by WP PageNavi Style
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 41.18 ▲0.45 |
| Dashboard /wp-admin | 3.33 ▼0.01 | 50.26 ▼14.82 |
| Posts /wp-admin/edit.php | 3.38 ▲0.03 | 52.53 ▲7.31 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 91.72 ▲1.68 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 38.66 ▲0.36 |
Server storage [IO: ▲0.30MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 110 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| WP_PAGENAVI_STYLE_OPTION |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by WP PageNavi Style
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,812 ▲51 | 14.25 ▼0.11 | 2.11 ▲0.16 | 45.10 ▲2.73 |
| Dashboard /wp-admin | 2,198 ▲27 | 5.56 ▼0.11 | 93.61 ▼0.18 | 78.74 ▲38.35 |
| Posts /wp-admin/edit.php | 2,115 ▲15 | 2.01 ▲0.02 | 35.10 ▼4.62 | 35.62 ▼1.24 |
| Add New Post /wp-admin/post-new.php | 1,558 ▲32 | 23.02 ▼0.25 | 697.38 ▲40.46 | 56.84 ▲7.55 |
| Media Library /wp-admin/upload.php | 1,415 ▲15 | 4.18 ▲0.01 | 100.76 ▼0.77 | 71.38 ▲25.98 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 3× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/wp-pagenavi-style/includes/our_feeds.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function load_plugin_textdomain() in wp-content/plugins/wp-pagenavi-style/wp-pagenavi-style.php:36
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/wp-pagenavi-style/includes/options.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
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: pagenavi styling, pagination, pagenavi css, pagenavi style, navigation...
wp-pagenavi-style/wp-pagenavi-style.php 92% from 13 tests
The entry point to "WP PageNavi Style" version 1.4 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- Domain Path: The domain path points to an invalid folder, "/lang" does not exist
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected2,312 lines of code in 44 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 36 | 25 | 0 | 1,405 |
| JavaScript | 3 | 4 | 23 | 522 |
| PHP | 5 | 36 | 37 | 385 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.14 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 7 | |
| ▷ Named functions | 7 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
60 PNG files occupy 0.13MB with 0.03MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| style/images/css3_light_blue_glossy.png | 3.38KB | 2.78KB | ▼ 17.56% |
| style/images/green.png | 2.23KB | 1.20KB | ▼ 46.25% |
| style/images/css3_yellow_glossy.png | 3.33KB | 2.77KB | ▼ 16.67% |
| style/images/red_black.png | 4.49KB | 2.91KB | ▼ 35.32% |
| images/error.png | 1.07KB | 0.97KB | ▼ 9.91% |