Benchmarks
Plugin footprint 22% 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
Please fix the following installer errors
- The plugin cannot be installed
- > Warning in wp-content/plugins/wpgenealogy/includes/class-wpgenealogy-activator.php+127
copy(wpgenealogy/includes/Helpers/mu-plugins/wpgenealogy-helpers.php): failed to open stream: No such file or directory
Server metrics [RAM: ▲1.45MB] [CPU: ▲0.63ms] Passed 4 tests
This is a short check of server-side resources used by WP Genealogy - Your Family History Website
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 5.33 ▲1.86 | 52.30 ▲9.05 |
Dashboard /wp-admin | 4.77 ▲1.43 | 52.38 ▼11.18 |
Posts /wp-admin/edit.php | 4.82 ▲1.47 | 53.36 ▲4.56 |
Add New Post /wp-admin/post-new.php | 7.33 ▲1.44 | 93.51 ▲0.08 |
Media Library /wp-admin/upload.php | 4.69 ▲1.46 | 44.98 ▲9.60 |
Freemius Debug [v.2.6.0] /wp-admin/admin.php?page=freemius | 5.06 | 41.12 |
Server storage [IO: ▲33.86MB] [DB: ▲0.04MB] 33% from 3 tests
How much does this plugin use your filesystem and database?
Just a few items left to fix
- You have illegally modified 1 file (0.00KB) outside of "wp-content/plugins/wpgenealogy/" and "wp-content/uploads/"
- (new file) wp-content/plugins/mu-plugins/.empty
- Total filesystem usage should be limited to 25MB (currently using 33.86MB)
Filesystem: 3,333 new files
Database: 23 new tables, 10 new options
New tables |
---|
wp_tp_timelines |
wp_tp_temp_events |
wp_tp_todos |
wp_tp_event_types |
wp_tp_families |
wp_tp_childrens |
wp_tp_notes |
wp_tp_events |
wp_tp_todo_comments |
wp_tp_associations |
... |
New WordPress options |
---|
fs_active_plugins |
theysaidso_admin_options |
wpgenealogy_settings |
fs_debug_mode |
widget_recent-posts |
fs_accounts |
widget_theysaidso_widget |
widget_recent-comments |
db_upgraded |
can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for WP Genealogy - Your Family History Website
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,164 ▲403 | 19.24 ▲4.51 | 149.17 ▲147.35 | 39.25 ▼3.08 |
Dashboard /wp-admin | 2,234 ▲53 | 5.58 ▼0.14 | 82.65 ▼27.27 | 38.60 ▼4.31 |
Posts /wp-admin/edit.php | 2,137 ▲40 | 2.00 ▲0.06 | 36.20 ▼2.07 | 37.57 ▲4.51 |
Add New Post /wp-admin/post-new.php | 1,548 ▲22 | 23.12 ▲0.07 | 654.54 ▼20.14 | 51.29 ▼0.21 |
Media Library /wp-admin/upload.php | 1,439 ▲42 | 4.24 ▼0.05 | 101.13 ▲1.84 | 44.92 ▼0.25 |
Freemius Debug [v.2.6.0] /wp-admin/admin.php?page=freemius | 1,104 | 1.69 | 30.33 | 27.17 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.04MB] 25% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Uninstall procedure had uncaught errors
- > Notice in wp-content/plugins/wpgenealogy/freemius/includes/class-freemius.php+8546
Undefined property: stdClass::$plugins
- This plugin does not fully uninstall, leaving 23 tables in the database
- wp_tp_todo_comments
- wp_tp_charts
- wp_tp_notes
- wp_tp_places
- wp_tp_branches
- wp_tp_events
- wp_tp_repositories
- wp_tp_sources
- wp_tp_temp_events
- wp_tp_addresses
- ...
- This plugin did not uninstall successfully, leaving 10 options in the database
- fs_active_plugins
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- fs_debug_mode
- widget_theysaidso_widget
- theysaidso_admin_options
- wpgenealogy_settings
- fs_accounts
- db_upgraded
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 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 10× PHP files output text when accessed directly:
- > /wp-content/plugins/wpgenealogy/vendor/sabberworm/php-css-parser/tests/quickdump.php
- > /wp-content/plugins/wpgenealogy/public/partials/wpgenealogy-public-display.php
- > /wp-content/plugins/wpgenealogy/vendor/illuminate/pagination/resources/views/simple-bootstrap-4.blade.php
- > /wp-content/plugins/wpgenealogy/vendor/doctrine/dbal/bin/doctrine-dbal.php
- > /wp-content/plugins/wpgenealogy/admin/partials/wpgenealogy-admin-display.php
- > /wp-content/plugins/wpgenealogy/vendor/illuminate/pagination/resources/views/semantic-ui.blade.php
- > /wp-content/plugins/wpgenealogy/vendor/symfony/translation/Resources/bin/translation-status.php
- > /wp-content/plugins/wpgenealogy/vendor/illuminate/pagination/resources/views/default.blade.php
- > /wp-content/plugins/wpgenealogy/vendor/illuminate/pagination/resources/views/simple-default.blade.php
- > /wp-content/plugins/wpgenealogy/vendor/illuminate/pagination/resources/views/bootstrap-4.blade.php
- 914× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Doctrine\\DBAL\\Platforms\\Keywords\\PostgreSQL94Keywords' not found in wp-content/plugins/wpgenealogy/vendor/doctrine/dbal/lib/Doctrine/DBAL/Platforms/Keywords/PostgreSQL100Keywords.php:10
- > PHP Fatal error
Uncaught Error: Class 'PhpGedcom\\Parser\\Component' not found in wp-content/plugins/wpgenealogy/includes/Import/php-gedcom/library/PhpGedcom/Parser/Head/Date.php:22
- > PHP Fatal error
Uncaught Error: Class 'PhpGedcom\\Parser\\Fam\\Even' not found in wp-content/plugins/wpgenealogy/includes/Import/php-gedcom/library/PhpGedcom/Parser/Fam/Anul.php:22
- > PHP Fatal error
Uncaught Error: Class 'FontLib\\Table\\Table' not found in wp-content/plugins/wpgenealogy/vendor/phenx/php-font-lib/src/FontLib/Table/Type/post.php:18
- > PHP Fatal error
Uncaught Error: Class 'Illuminate\\Console\\Command' not found in wp-content/plugins/wpgenealogy/vendor/illuminate/database/Console/Migrations/InstallCommand.php:9
- > PHP Fatal error
Uncaught Error: Class 'Illuminate\\Support\\Facades\\Facade' not found in wp-content/plugins/wpgenealogy/vendor/illuminate/support/Facades/Session.php:33
- > PHP Fatal error
Uncaught Error: Class 'Illuminate\\Database\\Query\\Processors\\Processor' not found in wp-content/plugins/wpgenealogy/vendor/illuminate/database/Query/Processors/MySqlProcessor.php:5
- > PHP Fatal error
Uncaught Error: Class 'Symfony\\Component\\Translation\\Loader\\ArrayLoader' not found in wp-content/plugins/wpgenealogy/vendor/symfony/translation/Loader/FileLoader.php:21
- > PHP Fatal error
Uncaught Error: Class 'PhpGedcom\\Parser\\Component' not found in wp-content/plugins/wpgenealogy/includes/Import/php-gedcom/library/PhpGedcom/Parser/Subn.php:22
- > PHP Fatal error
Uncaught Error: Class 'PhpGedcom\\Parser\\Indi\\Attr' not found in wp-content/plugins/wpgenealogy/includes/Import/php-gedcom/library/PhpGedcom/Parser/Indi/Titl.php:22
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Screenshots: Please add images for these screenshots: #16 ([TBC Front end: Timeline]), #17 ([TBC Front end: Add a Descendent Chart Anywhere on your Blog with a Shortcode])
wpgenealogy/wpgenealogy.php Passed 13 tests
The principal PHP file in "WP Genealogy - Your Family History Website" v. 0.1.5 is loaded by WordPress automatically on each request
62 characters long description:
All you need to build your family history website in WordPress
Code Analysis 0% from 3 tests
File types 0% from 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Please make sure to remedy the following
- Do not include executable or dangerous files in your plugin
- .bat - Batch File in Windows
- ☣ wp-content/plugins/wpgenealogy/vendor/nesbot/carbon/bin/carbon.bat
- .bat - Batch File in Windows
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2,128 | 41,247 | 108,025 | 179,854 |
Vuejs Component | 226 | 250 | 2,830 | 25,774 |
JavaScript | 87 | 1,747 | 546 | 13,255 |
XSD | 3 | 92 | 48 | 2,803 |
JSON | 26 | 0 | 0 | 2,575 |
Sass | 1 | 269 | 9 | 2,481 |
Markdown | 29 | 504 | 0 | 1,594 |
CSS | 63 | 213 | 127 | 1,237 |
XML | 18 | 37 | 61 | 691 |
SVG | 6 | 0 | 0 | 159 |
Blade | 5 | 11 | 19 | 144 |
YAML | 4 | 16 | 2 | 83 |
reStructuredText | 1 | 74 | 78 | 74 |
HTML | 2 | 0 | 0 | 24 |
Bourne Shell | 1 | 6 | 1 | 19 |
DOS Batch | 1 | 0 | 0 | 4 |
PHP code 0% from 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
It is recommended to fix the following
- Cyclomatic complexity of classes should be reduced to less than 1000 (currently 3,096)
- Method cyclomatic complexity should be reduced to less than 100 (currently 652)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.44 |
Average class complexity | 16.38 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 3,096.00 |
Average method complexity | 2.96 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 652.00 |
Code structure | ||
---|---|---|
Namespaces | 220 | |
Interfaces | 168 | |
Traits | 80 | |
Classes | 1,157 | |
▷ Abstract classes | 57 | 4.93% |
▷ Concrete classes | 1,100 | 95.07% |
▷ Final classes | 92 | 8.36% |
Methods | 11,818 | |
▷ Static methods | 1,282 | 10.85% |
▷ Public methods | 9,420 | 79.71% |
▷ Protected methods | 1,618 | 13.69% |
▷ Private methods | 780 | 6.60% |
Functions | 844 | |
▷ Named functions | 196 | 23.22% |
▷ Anonymous functions | 648 | 76.78% |
Constants | 761 | |
▷ Global constants | 112 | 14.72% |
▷ Class constants | 649 | 85.28% |
▷ Public constants | 637 | 98.15% |
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
329 PNG files occupy 1.23MB with 0.67MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
public/src/assets/images/delete-white.png | 1.22KB | 0.33KB | ▼ 73.04% |
public/js/timeline_ajax/images/message-right.png | 1.85KB | 0.38KB | ▼ 79.18% |
public/src/assets/images/admin/people.png | 2.21KB | 1.79KB | ▼ 19.25% |
public/css/public/src/assets/images/admin/album_blue.png | 1.62KB | 0.86KB | ▼ 46.78% |
public/src/assets/images/admin/chart.png | 10.08KB | 4.52KB | ▼ 55.13% |