Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
These installer errors require your attention
- This plugin did not install gracefully
- > Parse error in wp-content/plugins/geodigs/functions/format.php+37
syntax error, unexpected end of file
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.98ms] Passed 4 tests
A check of server-side resources used by GeoDigs
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 40.61 ▼2.43 |
Dashboard /wp-admin | 3.31 ▲0.00 | 49.92 ▲4.76 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.60 ▼0.01 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 85.06 ▼9.52 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.83 ▲0.03 |
Server storage [IO: ▲0.75MB] [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: 136 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
GeoDigs: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.21 ▼1.17 | 1.73 ▼0.10 | 43.44 ▲4.73 |
Dashboard /wp-admin | 2,206 ▲21 | 5.91 ▲0.05 | 111.29 ▲14.05 | 43.32 ▲1.22 |
Posts /wp-admin/edit.php | 2,086 ▼0 | 2.03 ▲0.03 | 33.29 ▼2.50 | 34.24 ▲2.86 |
Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.07 ▼0.24 | 598.88 ▼108.30 | 55.02 ▼2.15 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.21 ▲0.02 | 93.13 ▼12.16 | 43.04 ▼3.80 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 0% 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
The following issues need your attention
- 15× PHP files perform the action of outputting non-empty strings when accessed directly (only 10 are shown):
- > /wp-content/plugins/geodigs/templates/listings/featured.php
- > /wp-content/plugins/geodigs/includes/listings-results.php
- > /wp-content/plugins/geodigs/geodigs.php
- > /wp-content/plugins/geodigs/templates/listings/map-preview.php
- > /wp-content/plugins/geodigs/templates/listings/footer.php
- > /wp-content/plugins/geodigs/includes/forgot-password.php
- > /wp-content/plugins/geodigs/templates/emails/more-info-request.php
- > /wp-content/plugins/geodigs/templates/listings/header.php
- > /wp-content/plugins/geodigs/includes/more-info-requested.php
- > /wp-content/plugins/geodigs/modals/map-single.php
- 225× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Notice
Undefined variable: phone in wp-content/plugins/geodigs/templates/emails/more-info-request.php on line 7
- > PHP Notice
Undefined variable: name in wp-content/plugins/geodigs/templates/emails/new-file-added-to-document-store.php on line 1
- > PHP Notice
Undefined variable: link_address in wp-content/plugins/geodigs/includes/featured-row.php on line 21
- > PHP Warning
Invalid argument supplied for foreach() in wp-content/plugins/geodigs/templates/listings/footer.php on line 10
- > PHP Notice
Undefined variable: gd_api in wp-content/plugins/geodigs/includes/featured-row.php on line 16
- > PHP Fatal error
Uncaught Error: Call to undefined function gd_get_option() in wp-content/plugins/geodigs/admin/includes/custom-search-form.php:2
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/geodigs/widgets/quick-search-modal.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/geodigs/templates/listings/details.php:17
- > PHP Notice
Undefined variable: pagination in wp-content/plugins/geodigs/templates/listings/header.php on line 29
- > PHP Notice
Trying to get property 'readable' of non-object in wp-content/plugins/geodigs/templates/account/settings.php on line 51
- > PHP Notice
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 97% 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
Attributes that require attention:
- Plugin Name: Please specify the plugin name on the first line (
=== geodigs ===
)
geodigs/geodigs.php Passed 13 tests
The main file in "GeoDigs" v. 3.4.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
125 characters long description:
GeoDigs allows you to connect with clients and help them find the perfect home through REcolorado and IRES IDX MLS solutions.
Code Analysis Passed 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
Good job! No executable or dangerous file extensions detected12,685 lines of code in 120 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 87 | 971 | 892 | 7,021 |
CSS | 13 | 225 | 196 | 3,824 |
JavaScript | 14 | 761 | 268 | 1,389 |
JSON | 1 | 0 | 0 | 391 |
SVG | 5 | 0 | 5 | 60 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
Average class complexity | 10.94 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 51.00 |
Average method complexity | 2.41 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 37.00 |
Code structure | ||
---|---|---|
Namespaces | 3 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 31 | |
▷ Abstract classes | 2 | 6.45% |
▷ Concrete classes | 29 | 93.55% |
▷ Final classes | 0 | 0.00% |
Methods | 225 | |
▷ Static methods | 73 | 32.44% |
▷ Public methods | 209 | 92.89% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 16 | 7.11% |
Functions | 35 | |
▷ Named functions | 35 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 81 | |
▷ Global constants | 76 | 93.83% |
▷ Class constants | 5 | 6.17% |
▷ Public constants | 5 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
12 PNG files occupy 0.03MB with 0.02MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/ui/icon-bed.png | 1.19KB | 0.25KB | ▼ 78.77% |
admin/assets/images/layout-rows.png | 1.10KB | 0.11KB | ▼ 89.63% |
assets/images/ui/icon-trash.png | 4.22KB | 3.95KB | ▼ 6.37% |
assets/images/ui/settings-icon.png | 1.88KB | 0.78KB | ▼ 58.60% |
assets/images/ui/icon-bath.png | 1.11KB | 0.20KB | ▼ 82.28% |