Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼2.20ms] Passed 4 tests
Server-side resources used by Fomo for WooCommerce
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 38.17 ▼1.71 |
Dashboard /wp-admin | 3.35 ▲0.05 | 50.48 ▲4.57 |
Posts /wp-admin/edit.php | 3.40 ▲0.05 | 51.20 ▲2.75 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 86.12 ▼8.42 |
Media Library /wp-admin/upload.php | 3.27 ▲0.05 | 32.92 ▼1.41 |
Server storage [IO: ▲3.96MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 25 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Fomo for WooCommerce
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,811 ▲76 | 14.74 ▲0.36 | 1.62 ▼0.34 | 42.16 ▼0.01 |
Dashboard /wp-admin | 2,220 ▲35 | 4.84 ▼0.06 | 99.79 ▼13.90 | 41.34 ▲3.59 |
Posts /wp-admin/edit.php | 2,102 ▲13 | 2.06 ▲0.03 | 40.68 ▲5.55 | 34.39 ▼1.05 |
Add New Post /wp-admin/post-new.php | 1,525 ▲6 | 17.91 ▼5.44 | 651.02 ▼37.89 | 51.71 ▼1.33 |
Media Library /wp-admin/upload.php | 1,399 ▲11 | 4.21 ▼0.03 | 96.59 ▼3.71 | 41.77 ▼1.62 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were 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
Please fix the following attributes:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Message & Basic settings for Fomo notifications shown on storefront.), #2 (Design & Settings page for Fomo advanced settings of notification shown on storefront.), #3 (Fomo Live shows how many notification are currently shown to your customers.), #4 (Example how Fomo notification looks on storefront.)
fomo/woocommerce-plugin-fomo-v2.php 92% from 13 tests
The main PHP file in "Fomo for WooCommerce" ver. 2.0.11 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 ("fomo.php" instead of "woocommerce-plugin-fomo-v2.php")
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
There were no executable files found in this plugin10,305 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 10 | 1,736 | 5,634 | 10,252 |
CSS | 1 | 2 | 0 | 53 |
PHP code 50% from 2 tests
A short review of cyclomatic complexity and code structure
It is recommended to fix the following
- Please reduce cyclomatic complexity of methods to less than 100 (currently 104)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 239.88 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 562.00 |
Average method complexity | 7.71 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 104.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 285 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 285 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 19 | |
▷ Named functions | 19 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 124 | |
▷ Global constants | 124 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
8 PNG files occupy 2.86MB with 1.82MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-7.png | 393.48KB | 139.68KB | ▼ 64.50% |
screenshot-6.png | 282.48KB | 108.20KB | ▼ 61.70% |
screenshot-3.png | 472.08KB | 164.51KB | ▼ 65.15% |
screenshot-2.png | 169.96KB | 68.38KB | ▼ 59.77% |
screenshot-5.png | 255.00KB | 84.14KB | ▼ 67.00% |