Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▼0.94MB] [CPU: ▼33.69ms] Passed 4 tests
This is a short check of server-side resources used by Avishi Floating Horizontal Navigation
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 36.71 ▼3.22 |
Dashboard /wp-admin | 3.00 ▼0.30 | 21.87 ▼26.03 |
Posts /wp-admin/edit.php | 3.00 ▼0.35 | 22.22 ▼26.35 |
Add New Post /wp-admin/post-new.php | 3.00 ▼2.89 | 24.03 ▼69.61 |
Media Library /wp-admin/upload.php | 3.00 ▼0.23 | 21.54 ▼12.76 |
Avishi Floating Navigation /wp-admin/options-general.php?page=avishi-floating-horizontal-navigation/avishi_floating_horizontal_navigation.php | 3.00 | 22.32 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 3 new files
Database: no new tables, 7 new options
New WordPress options |
---|
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
db_upgraded |
avishi_navigation_id |
Browser metrics Passed 4 tests
A check of browser resources used by Avishi Floating Horizontal Navigation
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,885 ▲139 | 13.61 ▼0.79 | 8.75 ▲6.93 | 38.89 ▼10.50 |
Dashboard /wp-admin | 2,213 ▲22 | 5.89 ▲0.97 | 95.89 ▼24.55 | 40.59 ▼6.18 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.00 ▲0.02 | 39.75 ▼1.77 | 35.85 ▲2.14 |
Add New Post /wp-admin/post-new.php | 1,545 ▲9 | 18.03 ▼5.17 | 626.37 ▼58.97 | 64.49 ▲3.95 |
Media Library /wp-admin/upload.php | 1,389 ▲4 | 4.18 ▼0.01 | 95.16 ▼1.27 | 42.45 ▼1.08 |
Avishi Floating Navigation /wp-admin/options-general.php?page=avishi-floating-horizontal-navigation/avishi_floating_horizontal_navigation.php | 805 | 2.05 | 24.67 | 32.32 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- Uninstall procedure validation failed for this plugin
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- avishi_navigation_id
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Please fix the following server-side errors
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=avishi-floating-horizontal-navigation/avishi_floating_horizontal_navigation.php
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
SRP 50% from 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
Please take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_option() in wp-content/plugins/avishi-floating-horizontal-navigation/avishi_floating_horizontal_navigation.php:30
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
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
3 plugin tags: horizontal floating navigation, sticky on page scroll horizontal navigation, floating navigation
avishi-floating-horizontal-navigation/avishi_floating_horizontal_navigation.php 92% from 13 tests
Analyzing the main PHP file in "Avishi Floating Horizontal Navigation" version 1.0
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("avishi-floating-horizontal-navigation.php" instead of "avishi_floating_horizontal_navigation.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
Good job! No executable or dangerous file extensions detected77 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 60 | 35 | 77 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.07 |
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 | 4 | |
▷ Named functions | 4 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin