Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.25ms] Passed 4 tests
An overview of server-side resources used by Pretty Contact
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 37.81 ▲0.82 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 46.28 ▼0.49 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 48.20 ▲6.05 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 86.27 ▼10.68 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.69 ▼2.64 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 17 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Pretty Contact
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲69 | 13.28 ▼1.39 | 1.59 ▼0.10 | 42.74 ▲3.81 |
| Dashboard /wp-admin | 2,213 ▲22 | 4.83 ▼0.05 | 98.38 ▼19.67 | 39.35 ▼6.09 |
| Posts /wp-admin/edit.php | 2,096 ▲4 | 2.02 ▲0.02 | 38.51 ▲1.00 | 34.55 ▲3.89 |
| Add New Post /wp-admin/post-new.php | 1,549 ▲20 | 23.19 ▲4.62 | 627.46 ▼34.27 | 55.95 ▼3.97 |
| Media Library /wp-admin/upload.php | 1,386 ▼2 | 4.14 ▼0.05 | 98.39 ▼5.09 | 43.00 ▼3.06 |
| Pretty Contact /wp-admin/pretty_contact.php | 26 | 0.44 | 0.13 | 14.41 |
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
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/pretty-contact/pretty_contact.php:75
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There are user-side issues you should fix
- > GET request to /wp-admin/pretty_contact.php
- > Network (severe)
wp-admin/pretty_contact.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 93% 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
2 plugin tags: post, link
pretty-contact/pretty_contact.php 85% from 13 tests
The main PHP file in "Pretty Contact" ver. 0.1a... adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("pretty-contact.php" instead of "pretty_contact.php")
- Version: The version number should only use digits and periods (ex. "1.0.3" instead of "0.1a...")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Good job! No executable or dangerous file extensions detected63 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 8 | 22 | 47 |
| JSON | 1 | 0 | 0 | 16 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| 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 | 3 | |
| ▷ Named functions | 3 | 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
PNG files should be compressed to save space and minimize bandwidth usage
14 compressed PNG files occupy 0.01MB
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| icons/vk.png | 0.64KB | 0.71KB | 0.00% |
| icons/myspace.png | 0.37KB | 0.41KB | 0.00% |
| icons/youtube.png | 0.54KB | 0.60KB | 0.00% |
| icons/lastfm.png | 0.73KB | 0.82KB | 0.00% |
| icons/dribbble.png | 0.89KB | 0.96KB | 0.00% |