Benchmarks
Plugin footprint 83% 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.12MB] [CPU: ▼7.82ms] Passed 4 tests
A check of server-side resources used by Native Lazyload + Polyfill
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.60 ▲0.14 | 39.96 ▼0.60 |
| Dashboard /wp-admin | 3.50 ▲0.15 | 50.63 ▼11.39 |
| Posts /wp-admin/edit.php | 3.51 ▲0.16 | 46.47 ▼5.84 |
| Add New Post /wp-admin/post-new.php | 5.98 ▲0.10 | 85.65 ▼13.44 |
| Media Library /wp-admin/upload.php | 3.32 ▲0.10 | 44.17 ▲5.80 |
Server storage [IO: ▲0.20MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 27 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Native Lazyload + Polyfill
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,798 ▲52 | 14.26 ▼0.09 | 2.45 ▲0.83 | 38.66 ▼1.57 |
| Dashboard /wp-admin | 2,192 ▲12 | 5.52 ▼0.15 | 84.51 ▼11.72 | 37.64 ▼1.94 |
| Posts /wp-admin/edit.php | 2,099 ▼1 | 1.96 ▲0.01 | 36.37 ▼4.69 | 33.35 ▼3.52 |
| Add New Post /wp-admin/post-new.php | 1,529 ▼9 | 23.23 ▲0.19 | 663.56 ▲5.45 | 51.29 ▼3.89 |
| Media Library /wp-admin/upload.php | 1,405 ▲5 | 4.17 ▼0.06 | 99.48 ▼5.33 | 48.09 ▼0.05 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Trait 'IvoPetkov\\HTML5DOMDocument\\Internal\\QuerySelectors' not found in wp-content/plugins/native-lazyload-polyfill/vendor/ivopetkov/html5-dom-document-php/src/HTML5DOMElement.php on line 19
- > PHP Fatal error
Trait 'IvoPetkov\\HTML5DOMDocument\\Internal\\QuerySelectors' not found in wp-content/plugins/native-lazyload-polyfill/vendor/ivopetkov/html5-dom-document-php/src/HTML5DOMDocument.php on line 15
- > PHP Fatal error
Uncaught Error: Call to undefined function Nextgenthemes\ativeLazyloadPolyfill\\add_action() in wp-content/plugins/native-lazyload-polyfill/native-lazyload-polyfill.php:29
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
6 plugin tags: iframe, polyfill, images, lazyload, loading...
native-lazyload-polyfill/native-lazyload-polyfill.php 85% from 13 tests
The entry point to "Native Lazyload + Polyfill" version 1.1.0 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Domain Path: The domain path folder does not exist ("/languages")
- Description: Keep the plugin description shorter than 140 characters (currently 145 characters long)
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
Everything looks great! No dangerous files found in this plugin1,929 lines of code in 21 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 15 | 251 | 522 | 1,681 |
| JavaScript | 2 | 36 | 66 | 145 |
| JSON | 3 | 0 | 0 | 93 |
| HTML | 1 | 1 | 0 | 10 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.54 |
| Average class complexity | 45.25 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 144.00 |
| Average method complexity | 3.95 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 37.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 4 | |
| Interfaces | 0 | |
| Traits | 1 | |
| Classes | 7 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 7 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 62 | |
| ▷ Static methods | 3 | 4.84% |
| ▷ Public methods | 53 | 85.48% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 9 | 14.52% |
| Functions | 39 | |
| ▷ Named functions | 12 | 30.77% |
| ▷ Anonymous functions | 27 | 69.23% |
| Constants | 11 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 11 | 100.00% |
| ▷ Public constants | 11 | 100.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
There were not PNG files found in your plugin