Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼0.35ms] Passed 4 tests
An overview of server-side resources used by FullScreen AJAX Loader
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.55 ▲0.09 | 39.83 ▼1.56 |
Dashboard /wp-admin | 3.37 ▲0.06 | 45.60 ▼1.92 |
Posts /wp-admin/edit.php | 3.42 ▲0.06 | 48.69 ▲0.08 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 96.83 ▲2.28 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 35.75 ▲2.02 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 13 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for FullScreen AJAX Loader
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,830 ▲84 | 14.48 ▼0.26 | 1.64 ▼0.24 | 39.60 ▼4.80 |
Dashboard /wp-admin | 2,206 ▲35 | 5.86 ▲0.98 | 108.22 ▼13.23 | 40.47 ▼2.79 |
Posts /wp-admin/edit.php | 2,089 ▼3 | 2.03 ▲0.01 | 39.39 ▼1.12 | 35.06 ▼4.14 |
Add New Post /wp-admin/post-new.php | 1,533 ▼3 | 23.30 ▲0.15 | 661.88 ▲50.80 | 49.33 ▼4.27 |
Media Library /wp-admin/upload.php | 1,385 ▼6 | 4.23 ▼0.00 | 104.73 ▲4.00 | 47.65 ▲4.47 |
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
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
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
Please take a closer look at the following
- 6× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/fullscreen-ajax-loader/templates/circular.php
- > /wp-content/plugins/fullscreen-ajax-loader/templates/spiral.php
- > /wp-content/plugins/fullscreen-ajax-loader/templates/floating-bars.php
- > /wp-content/plugins/fullscreen-ajax-loader/templates/load-ball.php
- > /wp-content/plugins/fullscreen-ajax-loader/templates/custom.php
- > /wp-content/plugins/fullscreen-ajax-loader/templates/floating-circles.php
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function FPWD\\add_action() in wp-content/plugins/fullscreen-ajax-loader/Fullscreen_Ajax_Loader.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need to be fixed:
- Screenshots: Please describe screenshot #4 in fullscreen-ajax-loader/assets to your readme.txt
fullscreen-ajax-loader/Fullscreen_Ajax_Loader.php 92% from 13 tests
The main file in "FullScreen AJAX Loader" v. 1.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("fullscreen-ajax-loader.php" instead of "Fullscreen_Ajax_Loader.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Good job! No executable or dangerous file extensions detected359 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 6 | 62 | 22 | 310 |
PO File | 1 | 11 | 14 | 47 |
CSS | 1 | 0 | 0 | 1 |
JavaScript | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.15 |
Average class complexity | 11.00 |
▷ Minimum class complexity | 11.00 |
▷ Maximum class complexity | 11.00 |
Average method complexity | 1.69 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 14 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 13 | 92.86% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 7.14% |
Functions | 1 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 1 | 100.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.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
No PNG images were found in this plugin