Benchmarks

Plugin footprint 65% from 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | The install procedure must perform silently

Installer ran successfully

Server metrics [RAM: ▲0.01MB] [CPU: ▼3.74ms] Passed 4 tests

A check of server-side resources used by Mango FAQs

Server-side resource usage in normal parameters

Page	Memory (MB)	CPU Time (ms)
Home /	3.47 ▲0.01	38.84 ▼5.47
Dashboard /wp-admin	3.31 ▲0.01	50.44 ▼1.89
Posts /wp-admin/edit.php	3.36 ▲0.01	49.68 ▲0.08
Add New Post /wp-admin/post-new.php	5.89 ▲0.01	92.69 ▼7.66
Media Library /wp-admin/upload.php	3.24 ▲0.01	37.27 ▲2.20
Mango FAQs /wp-admin/options-general.php?page=mango-settings	3.18	32.69

Server storage [IO: ▲0.02MB] [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: 4 new files

Database: 1 new table, 6 new options

New tables
wp_mango

New WordPress options
can_compress_scripts
widget_recent-comments
db_upgraded
widget_recent-posts
theysaidso_admin_options
widget_theysaidso_widget

Browser metrics Passed 4 tests

Checking browser requirements for Mango FAQs

There were no issues detected in relation to browser resource usage

Page	Nodes	Memory (MB)	Script (ms)	Layout (ms)
Home /	2,884 ▲123	13.44 ▼1.11	8.07 ▲4.85	41.37 ▲2.13
Dashboard /wp-admin	2,206 ▲29	5.65 ▲0.01	86.73 ▼15.91	40.32 ▼2.27
Posts /wp-admin/edit.php	2,108 ▲8	2.00 ▼0.02	37.79 ▲0.18	35.34 ▲0.26
Add New Post /wp-admin/post-new.php	1,538 ▲12	23.31 ▲0.20	646.77 ▲41.25	57.08 ▲4.72
Media Library /wp-admin/upload.php	1,411 ▲14	4.20 ▲0.01	96.28 ▼5.53	43.62 ▼1.17
Mango FAQs /wp-admin/options-general.php?page=mango-settings	936	2.04	22.48	32.85

Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests

🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces

The following items require your attention

The plugin did not uninstall successfully, leaving 1 table in the database
- wp_mango
This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts

Smoke tests 25% from 4 tests

Server-side errors 0% from 1 test

🔹 Test weight: 20 | A smoke test targeting server-side errors

These server-side errors were triggered

- > GET request to /wp-admin/options-general.php?page=mango-settings
- > Notice in wp-content/plugins/mango-faqs/mango.php+59
Undefined index: addquestion
- > GET request to /wp-admin/options-general.php?page=mango-settings
- > Notice in wp-content/plugins/mango-faqs/mango.php+59
Undefined index: addanswer
- > GET request to /wp-admin/options-general.php?page=mango-settings
- > Notice in wp-content/plugins/mango-faqs/mango.php+59
Undefined index: deleteid
- > GET request to /wp-admin/options-general.php?page=mango-settings
- > Notice in wp-content/plugins/mango-faqs/mango.php+65
Undefined variable: addquestion
- > GET request to /wp-admin/options-general.php?page=mango-settings
- > Notice in wp-content/plugins/mango-faqs/mango.php+66
Undefined variable: deleteid

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

1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
  Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/mango-faqs/mango.php:32

User-side errors 0% from 1 test

🔹 Test weight: 20 | A shallow check that no browser errors were triggered

Please fix the following user-side errors

- > GET request to /wp-admin/options-general.php?page=mango-settings
- > Network (severe)
wp-content/plugins/mango/style.css?ver=6.3.1 - Failed to load resource: the server responded with a status of 404 (Not Found)

Optimizations

Plugin configuration 96% from 29 tests

readme.txt Passed 16 tests

The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org

9 plugin tags: mango, faqs, autoresponder, contact form, plugin...

mango-faqs/mango.php 92% from 13 tests

The entry point to "Mango FAQs" version 1.0 is a PHP file that has certain tags in its header comment area

It is important to fix the following:

Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("mango-faqs.php" instead of "mango.php")

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

Everything looks great! No dangerous files found in this plugin344 lines of code in 3 files:

Language	Files	Blank lines	Comment lines	Lines of code
PHP	1	60	41	311
CSS	1	6	0	26
JavaScript	1	0	0	7

PHP code Passed 2 tests

This is a short overview of cyclomatic complexity and code structure for this plugin

There are no cyclomatic complexity problems detected for this plugin

Cyclomatic complexity
Average complexity per logical line of code	0.22
Average class complexity	0.00
▷ Minimum class complexity	0.00
▷ Maximum class complexity	0.00
Average method complexity	0.00
▷ Minimum method complexity	0.00
▷ Maximum method complexity	0.00

Code structure
Namespaces	0
Interfaces	0
Traits	0
Classes	0
▷ Abstract classes	0	0.00%
▷ Concrete classes	0	0.00%
▷ Final classes	0	0.00%
Methods	0
▷ Static methods	0	0.00%
▷ Public methods	0	0.00%
▷ Protected methods	0	0.00%
▷ Private methods	0	0.00%
Functions	17
▷ Named functions	17	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

Using a strong compression for your PNG files is a great way to speed-up your plugin

PNG images were not found in this plugin

Code Review | Mango FAQs

About plugin

Code review

User reviews

Install metrics