Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
It is recommended to fix the following installer errors
- This plugin did not install gracefully
- > Deprecated in wp-content/plugins/flickr-eyecandy/flickr_eyecandy.php+157
Methods with the same name as their class will not be constructors in a future version of PHP; FlickrEyeCandyWidget has a deprecated constructor
Server metrics [RAM: ▼1.71MB] [CPU: ▼48.48ms] Passed 4 tests
This is a short check of server-side resources used by FlickrEyeCandy
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.28 ▼1.18 | 9.56 ▼33.04 |
| Dashboard /wp-admin | 2.29 ▼1.01 | 11.01 ▼39.15 |
| Posts /wp-admin/edit.php | 2.30 ▼1.06 | 10.69 ▼33.48 |
| Add New Post /wp-admin/post-new.php | 2.29 ▼3.59 | 9.98 ▼88.26 |
| Media Library /wp-admin/upload.php | 2.29 ▼0.94 | 8.69 ▼26.81 |
Server storage [IO: ▲0.49MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 6 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
| widget_flickreyecandywidget |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for FlickrEyeCandy
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.27 ▼0.45 | 1.80 ▲0.09 | 40.75 ▼3.49 |
| Dashboard /wp-admin | 2,195 ▲21 | 5.54 ▼0.13 | 87.01 ▼10.39 | 39.29 ▼2.98 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.98 ▼0.03 | 39.88 ▼0.84 | 35.53 ▼8.25 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼2 | 23.81 ▲0.88 | 651.03 ▼2.40 | 55.95 ▲1.70 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.17 ▼0.02 | 98.71 ▼14.36 | 40.33 ▼2.11 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- The plugin did not uninstall gracefully
- > User deprecated in wp-includes/functions.php+5546
The called constructor method for WP_Widget class in FlickrEyeCandyWidget is deprecated since version 4.3.0! Use __construct() instead.
- Zombie WordPress options were found after uninstall: 7 options
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- widget_flickreyecandywidget
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
Even though no errors were found, this is by no means an exhaustive test
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 fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_site_url() in wp-content/plugins/flickr-eyecandy/flickr_eyecandy.php:28
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that need to be fixed:
- Screenshots: These screenshots do not have images: #1 (This shows the rendering of the Widget in the sidebar of a WP blog.), #2 (This shows how to Activate the plugin in the Plugins menu in the WP Admin backend), #3 (Configuring the settings for the flickr_eyecandy widget in the WP Admin backend.)
flickr-eyecandy/flickr_eyecandy.php 85% from 13 tests
The principal PHP file in "FlickrEyeCandy" v. 2016.01.29 is loaded by WordPress automatically on each request
It is important to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 147 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("flickr-eyecandy.php" instead of "flickr_eyecandy.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 plugin248 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 40 | 43 | 248 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 11.00 |
| ▷ Minimum class complexity | 8.00 |
| ▷ Maximum class complexity | 14.00 |
| Average method complexity | 3.22 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.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 | 9 | |
| ▷ Static methods | 3 | 33.33% |
| ▷ Public methods | 9 | 100.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
PNG files should be compressed to save space and minimize bandwidth usage
3 PNG files occupy 0.23MB with 0.10MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 45.37KB | 25.72KB | ▼ 43.31% |
| screenshot-3.png | 8.82KB | 7.28KB | ▼ 17.50% |
| screenshot-1.png | 181.74KB | 56.14KB | ▼ 69.11% |