Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.23MB] [CPU: ▼5.34ms] Passed 4 tests
This is a short check of server-side resources used by iframe - Responsive, Lazy Load
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.16 ▲0.70 | 42.04 ▼2.86 |
| Dashboard /wp-admin | 3.56 ▲0.26 | 47.70 ▼2.85 |
| Posts /wp-admin/edit.php | 3.61 ▲0.26 | 43.67 ▼1.34 |
| Add New Post /wp-admin/post-new.php | 6.08 ▲0.19 | 81.69 ▼14.30 |
| Media Library /wp-admin/upload.php | 3.42 ▲0.19 | 35.35 ▼0.38 |
| iframe RLL /wp-admin/options-general.php?page=iframe-rll | 3.40 | 30.53 |
Server storage [IO: ▲0.83MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 71 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| widget_iframerll_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| iframeRLL_fields |
Browser metrics Passed 4 tests
This is an overview of browser requirements for iframe - Responsive, Lazy Load
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,810 ▲64 | 13.59 ▼1.24 | 2.70 ▲0.94 | 42.69 ▼0.39 |
| Dashboard /wp-admin | 2,215 ▲33 | 4.90 ▼1.00 | 99.24 ▼17.20 | 37.83 ▼10.98 |
| Posts /wp-admin/edit.php | 2,095 ▲6 | 2.19 ▲0.18 | 34.56 ▼2.06 | 35.11 ▲3.27 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲16 | 23.34 ▲5.71 | 628.83 ▼23.03 | 48.49 ▼9.43 |
| Media Library /wp-admin/upload.php | 1,394 ▲3 | 4.25 ▲0.04 | 98.85 ▼6.40 | 40.17 ▼5.38 |
| iframe RLL /wp-admin/options-general.php?page=iframe-rll | 1,044 | 2.23 | 23.20 | 36.12 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- Zombie WordPress options detected upon uninstall: 7 options
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- widget_iframerll_widget
- 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
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
Please take a closer look at the following
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/iframe-responsive-lazy-load/assests/vendor/masterminds/html5/bin/entities.php
- 28× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Masterminds\\HTML5\\Tests\\TestCase' not found in wp-content/plugins/iframe-responsive-lazy-load/assests/vendor/masterminds/html5/test/HTML5/Serializer/TraverserTest.php:8
- > PHP Fatal error
Uncaught Error: Interface 'Masterminds\\HTML5\\Parser\\InputStream' not found in wp-content/plugins/iframe-responsive-lazy-load/assests/vendor/masterminds/html5/src/HTML5/Parser/StringInputStream.php:46
- > PHP Fatal error
Uncaught Error: Class 'Masterminds\\HTML5\\Tests\\TestCase' not found in wp-content/plugins/iframe-responsive-lazy-load/assests/vendor/masterminds/html5/test/HTML5/ElementsTest.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_enqueue_style() in wp-content/plugins/iframe-responsive-lazy-load/includes/views/admin-editor-btn.php:2
- > PHP Warning
require(wp-content/plugins/iframe-responsive-lazy-load/assests/vendor/masterminds/html5/test/benchmark/../../vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/iframe-responsive-lazy-load/assests/vendor/masterminds/html5/test/benchmark/run.php on line 3
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/iframe-responsive-lazy-load/includes/class-widgets.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function iframe_RLL() in wp-content/plugins/iframe-responsive-lazy-load/includes/views/admin-iframe-rll-page.php:2
- > PHP Fatal error
Uncaught Error: Interface 'Masterminds\\HTML5\\InstructionProcessor' not found in wp-content/plugins/iframe-responsive-lazy-load/assests/vendor/masterminds/html5/test/HTML5/Parser/InstructionProcessorMock.php:5
- > PHP Fatal error
Uncaught Error: Class 'Masterminds\\HTML5\\Tests\\TestCase' not found in wp-content/plugins/iframe-responsive-lazy-load/assests/vendor/masterminds/html5/test/HTML5/Serializer/OutputRulesTest.php:9
- > PHP Fatal error
require(): Failed opening required 'vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/iframe-responsive-lazy-load/assests/vendor/masterminds/html5/example.php on line 3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Screenshots: Add a description for screenshot #3 in iframe-responsive-lazy-load/assets to your readme.txt
iframe-responsive-lazy-load/iframeRLL.php 85% from 13 tests
This is the main PHP file of "iframe - Responsive, Lazy Load" version 1.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("iframe-responsive-lazy-load.php" instead of "iframeRLL.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
There were no executable files found in this plugin16,576 lines of code in 66 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 54 | 1,462 | 2,547 | 10,742 |
| HTML | 4 | 1,089 | 56 | 5,286 |
| CSS | 2 | 3 | 1 | 305 |
| Markdown | 2 | 39 | 0 | 110 |
| JSON | 1 | 0 | 0 | 71 |
| JavaScript | 2 | 9 | 5 | 45 |
| XML | 1 | 0 | 0 | 17 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 13.49 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 140.00 |
| Average method complexity | 2.37 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 62.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 9 | |
| Interfaces | 4 | |
| Traits | 0 | |
| Classes | 39 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 39 | 100.00% |
| ▷ Final classes | 1 | 2.56% |
| Methods | 418 | |
| ▷ Static methods | 19 | 4.55% |
| ▷ Public methods | 355 | 84.93% |
| ▷ Protected methods | 58 | 13.88% |
| ▷ Private methods | 5 | 1.20% |
| Functions | 5 | |
| ▷ Named functions | 2 | 40.00% |
| ▷ Anonymous functions | 3 | 60.00% |
| Constants | 72 | |
| ▷ Global constants | 9 | 12.50% |
| ▷ Class constants | 63 | 87.50% |
| ▷ Public constants | 63 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
There are no PNG files in this plugin