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: ▼12.55ms] Passed 4 tests
Server-side resources used by Amplify
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.39 ▼0.07 | 23.29 ▼20.33 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 44.77 ▼1.06 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.73 ▼4.35 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 79.37 ▼24.47 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.76 ▲6.60 |
Server storage [IO: ▲1.26MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 33 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
| widget_recent-posts |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Amplify
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,935 ▲200 | 13.65 ▼0.59 | 5.25 ▲3.22 | 43.42 ▼3.31 |
| Dashboard /wp-admin | 2,224 ▲33 | 4.91 ▼0.99 | 107.52 ▲4.35 | 72.57 ▲29.13 |
| Posts /wp-admin/edit.php | 2,107 ▲15 | 2.02 ▲0.00 | 37.77 ▼2.80 | 32.89 ▼4.30 |
| Add New Post /wp-admin/post-new.php | 1,536 ▼6 | 23.24 ▲5.05 | 771.30 ▲172.96 | 53.21 ▼6.48 |
| Media Library /wp-admin/upload.php | 1,394 ▲3 | 4.14 ▼0.08 | 98.84 ▼2.35 | 74.85 ▲31.68 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
Smoke tests 75% 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 items
- 5× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/amplify/includes/html/sociallogin.php:29
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/amplify/index.php:53
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/amplify/includes/html/advancesettings.php:21
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/amplify/includes/html/amplify.php:23
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/amplify/includes/html/socialsharing.php:20
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Please fix the following attributes:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (**Amplify** -Feedback widgets, contact us forms etc are seen by your users as one-way conversations. Users after filling up a form are not even sure if they will receive a reply. But with Amplify Connect these feedbacks are turned into conversations and stored in a personalised user-inbox for every user.), #2 (**Pro-active User Engagement**-Less than 0.5% users on any site submits a feedback or fill up a contact form. So instead of waiting for users to contact you, why not greet them with a custom message when then pay you a visit.), #3 (**Easy and yet powerful customer support**-Easily assign these conversations and support requests to team members. Use email forwarding to centralised your support queries via Amplify Connect.), #4 (**additional marketing channel**-An additional marketing channel)
amplify/index.php 92% from 13 tests
The entry point to "Amplify" version 1.0.1 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("amplify.php" instead of "index.php")
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
Success! There were no dangerous files found in this plugin1,711 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 7 | 266 | 196 | 1,312 |
| CSS | 1 | 55 | 1 | 393 |
| JavaScript | 1 | 0 | 0 | 6 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| Average class complexity | 47.00 |
| ▷ Minimum class complexity | 38.00 |
| ▷ Maximum class complexity | 56.00 |
| Average method complexity | 2.61 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 57 | |
| ▷ Static methods | 12 | 21.05% |
| ▷ Public methods | 50 | 87.72% |
| ▷ Protected methods | 4 | 7.02% |
| ▷ Private methods | 3 | 5.26% |
| 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 50% from 2 tests
Image compression 50% from 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
23 PNG files occupy 1.18MB with 0.72MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-3.png | 81.93KB | 26.66KB | ▼ 67.46% |
| images/u93_normal.png | 303.20KB | 84.03KB | ▼ 72.29% |
| images/amp-connect.png | 7.02KB | 1.58KB | ▼ 77.53% |
| screenshot-2.png | 150.03KB | 50.75KB | ▼ 66.17% |
| images/u204_normal.png | 2.54KB | 1.95KB | ▼ 23.11% |