Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼4.71ms] Passed 4 tests
Server-side resources used by Expanding Archives
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 36.46 ▼7.46 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 46.91 ▼5.85 |
| Posts /wp-admin/edit.php | 3.43 ▲0.08 | 51.28 ▲1.84 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 87.96 ▼7.35 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 37.33 ▲4.13 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 26 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| widget_ng_expanding_archives |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for Expanding Archives
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,832 ▲97 | 13.25 ▼1.13 | 5.05 ▲3.21 | 46.12 ▲2.13 |
| Dashboard /wp-admin | 2,203 ▲15 | 5.86 ▼0.03 | 103.37 ▼14.23 | 37.05 ▼11.20 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 1.98 ▼0.03 | 41.43 ▲6.48 | 35.14 ▼0.06 |
| Add New Post /wp-admin/post-new.php | 1,538 ▼5 | 23.34 ▲4.91 | 674.71 ▲75.93 | 63.74 ▲7.96 |
| Media Library /wp-admin/upload.php | 1,391 ▲9 | 4.24 ▼0.11 | 107.29 ▲5.14 | 46.11 ▲4.23 |
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
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_ng_expanding_archives
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
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
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/expanding-archives/src/Widget.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function Ashleyfae\\ExpandingArchives\\trailingslashit() in wp-content/plugins/expanding-archives/src/Plugin.php:28
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need to be fixed:
- Tags: There are too many tags (12 tag instead of maximum 10)
expanding-archives/expanding-archives.php 85% from 13 tests
"Expanding Archives" version 2.0.2's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Domain Path: Prefix the domain path with a forward slash character ("/lang")
- Domain Path: The domain path follows the same naming rules as the domain name, using only dashes and lowercase characters ("lang")
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
Success! There were no dangerous files found in this plugin1,092 lines of code in 21 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 18 | 247 | 657 | 1,085 |
| JSON | 1 | 0 | 0 | 5 |
| CSS | 1 | 0 | 0 | 1 |
| JavaScript | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.40 |
| Average class complexity | 13.80 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 47.00 |
| Average method complexity | 2.81 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 6 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 10 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 10 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 73 | |
| ▷ Static methods | 19 | 26.03% |
| ▷ Public methods | 64 | 87.67% |
| ▷ Protected methods | 5 | 6.85% |
| ▷ Private methods | 4 | 5.48% |
| Functions | 12 | |
| ▷ Named functions | 4 | 33.33% |
| ▷ Anonymous functions | 8 | 66.67% |
| Constants | 2 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 2 | 100.00% |
| ▷ Public constants | 2 | 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