Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼2.38ms] Passed 4 tests
Server-side resources used by Far Future Expiry Header
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 47.90 ▲0.11 |
| Dashboard /wp-admin | 3.35 ▲0.05 | 54.14 ▼0.71 |
| Posts /wp-admin/edit.php | 3.40 ▲0.05 | 52.31 ▲2.82 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 90.68 ▼11.75 |
| Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 39.55 ▲3.71 |
| FarFutureExpiry /wp-admin/options-general.php?page=ffe_plugin_options | 3.27 | 33.85 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Far Future Expiry Header
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲58 | 14.79 ▲0.42 | 1.84 ▲0.05 | 43.92 ▼7.97 |
| Dashboard /wp-admin | 2,213 ▲25 | 4.81 ▼1.10 | 113.40 ▲2.54 | 49.35 ▲6.56 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.00 ▼0.02 | 36.59 ▼7.21 | 35.61 ▲0.56 |
| Add New Post /wp-admin/post-new.php | 1,530 ▼3 | 18.62 ▼4.46 | 664.85 ▼31.85 | 49.81 ▼10.41 |
| Media Library /wp-admin/upload.php | 1,395 ▲7 | 4.21 ▲0.01 | 95.23 ▼14.56 | 44.47 ▼1.85 |
| FarFutureExpiry /wp-admin/options-general.php?page=ffe_plugin_options | 969 | 2.17 | 26.68 | 24.57 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
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 fix the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/far-future-expiry-header/far-future-expiration.php:36
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need your attention:
- Tags: Too many tags (12 tag instead of maximum 10); only the first 5 tags are used in your directory listing
far-future-expiry-header/far-future-expiration.php 92% from 13 tests
"Far Future Expiry Header" version 1.6's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("far-future-expiry-header.php" instead of "far-future-expiration.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected407 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 57 | 56 | 407 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.51 |
| Average class complexity | 40.00 |
| ▷ Minimum class complexity | 40.00 |
| ▷ Maximum class complexity | 40.00 |
| Average method complexity | 3.79 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 14.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| 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 | 14 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG images were found in this plugin