Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.02MB] [CPU: ▼2.27ms] Passed 4 tests
Server-side resources used by Prettypre
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 37.55 ▼1.79 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 47.74 ▼0.99 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 48.76 ▲0.63 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 100.64 ▼6.94 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 37.25 ▲1.38 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Prettypre
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,818 ▲72 | 13.18 ▼1.22 | 1.58 ▼0.10 | 42.72 ▼2.34 |
| Dashboard /wp-admin | 2,222 ▲34 | 4.87 ▼0.98 | 112.38 ▲11.47 | 43.09 ▲2.45 |
| Posts /wp-admin/edit.php | 2,108 ▲22 | 1.96 ▼0.09 | 36.35 ▼1.18 | 30.20 ▼5.61 |
| Add New Post /wp-admin/post-new.php | 1,555 ▲21 | 18.48 ▼4.68 | 606.26 ▲16.31 | 46.04 ▼6.73 |
| Media Library /wp-admin/upload.php | 1,404 ▲22 | 4.21 ▼0.01 | 93.25 ▼3.73 | 43.70 ▲1.50 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 2× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/prettypre/loadjs.php
- > /wp-content/plugins/prettypre/prettyprecss.php
- 10× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/prettypre/options.php:3
- > PHP Notice
Undefined index: ts in wp-content/plugins/prettypre/prettyprecss.php on line 104
- > PHP Notice
Undefined index: ts in wp-content/plugins/prettypre/prettyprecss.php on line 36
- > PHP Notice
Undefined index: ts in wp-content/plugins/prettypre/prettyprecss.php on line 74
- > PHP Notice
Undefined index: ts in wp-content/plugins/prettypre/prettyprecss.php on line 56
- > PHP Notice
Undefined index: ts in wp-content/plugins/prettypre/prettyprecss.php on line 121
- > PHP Notice
Undefined index: ts in wp-content/plugins/prettypre/prettyprecss.php on line 89
- > PHP Notice
Undefined index: ts in wp-content/plugins/prettypre/prettyprecss.php on line 12
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/prettypre/prettypre.php:27
- > PHP Notice
Undefined index: ts in wp-content/plugins/prettypre/prettyprecss.php on line 21
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need your attention:
- Plugin Name: You should set the name of your plugin on the first line (
=== prettypre ===) - Tested up to: Version format is invalid
prettypre/prettypre.php 92% from 13 tests
The principal PHP file in "Prettypre" v. 1.30 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 189 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Everything looks great! No dangerous files found in this plugin185 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 65 | 26 | 185 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.00 |
| 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 | 5 | |
| ▷ Named functions | 5 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.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
No PNG files were detected