Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼145.71ms] Passed 4 tests
An overview of server-side resources used by Gigaom New Relic
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.87 ▲0.04 | 32.82 ▲3.08 |
| Dashboard /wp-admin | 3.10 ▲0.04 | 45.14 ▲1.22 |
| Posts /wp-admin/edit.php | 3.15 ▲0.04 | 42.59 ▲0.31 |
| Add New Post /wp-admin/post-new.php | 5.46 ▲0.03 | 85.53 ▼573.27 |
| Media Library /wp-admin/upload.php | 3.04 ▲0.03 | 30.59 ▼11.10 |
| New Relic Settings /wp-admin/options-general.php?page=go-newrelic-settings | 3.01 | 29.09 |
Server storage [IO: ▲0.19MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 7 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
A check of browser resources used by Gigaom New Relic
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,684 ▲88 | 15.93 ▲0.49 | 8.22 ▲0.54 | 45.64 ▼2.48 |
| Dashboard /wp-admin | 2,972 ▲38 | 5.89 ▼0.13 | 139.81 ▼0.15 | 99.59 ▼2.16 |
| Posts /wp-admin/edit.php | 2,744 ▲5 | 2.68 ▼0.01 | 65.60 ▲0.56 | 89.37 ▼3.80 |
| Add New Post /wp-admin/post-new.php | 1,501 ▼171 | 18.81 ▲0.01 | 360.92 ▼7.43 | 111.16 ▼0.75 |
| Media Library /wp-admin/upload.php | 1,815 ▲8 | 5.01 ▼0.02 | 156.99 ▲8.96 | 114.25 ▼13.31 |
| New Relic Settings /wp-admin/options-general.php?page=go-newrelic-settings | 1,035 | 2.09 | 57.76 | 69.25 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Uninstall script ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not 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 trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/go-newrelic/components/class-go-newrelic-browser.php:10
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need your attention:
- Screenshots: Please add images for these screenshots: #1 (New Relic application list, showing two blogs. Each WordPress blog is reported as four applications in New Relic to separate reader, writer, cron, and admin-ajax activity for better detail and fine-grained control.), #2 (New Relic application overview, showing performance history for a single app.)
go-newrelic/go-newrelic.php 92% from 13 tests
"Gigaom New Relic" version 0.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 164 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Everything looks great! No dangerous files found in this plugin252 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 46 | 62 | 252 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 11.33 |
| ▷ Minimum class complexity | 9.00 |
| ▷ Maximum class complexity | 14.00 |
| Average method complexity | 3.21 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 14 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 13 | 92.86% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 7.14% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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
2 PNG files occupy 0.17MB with 0.08MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 63.11KB | 35.99KB | ▼ 42.97% |
| screenshot-2.png | 112.27KB | 56.19KB | ▼ 49.95% |