Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
These installer errors require your attention
- This plugin did not install gracefully
- > Warning in wp-content/plugins/eewee-flattr/controllers/EeweeFlattr.php+2
Use of undefined constant EeweeFlattr - assumed 'EeweeFlattr' (this will throw an Error in a future version of PHP)
Server metrics [RAM: ▼1.93MB] [CPU: ▼51.84ms] Passed 4 tests
Analyzing server-side resources used by eewee flattr
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.07 ▼1.40 | 4.61 ▼39.20 |
Dashboard /wp-admin | 2.09 ▼1.26 | 5.63 ▼52.60 |
Posts /wp-admin/edit.php | 2.09 ▼1.27 | 6.13 ▼39.42 |
Add New Post /wp-admin/post-new.php | 2.09 ▼3.80 | 5.94 ▼76.14 |
Media Library /wp-admin/upload.php | 2.09 ▼1.14 | 5.20 ▼29.70 |
Eewee Flattr /wp-admin/admin.php?page=idEeweeFlattr | 2.09 | 5.54 |
Manual /wp-admin/admin.php?page=idSousMenuFlattr | 2.09 | 7.37 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 15 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
can_compress_scripts |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for eewee flattr
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,838 ▲92 | 13.26 ▼1.42 | 1.82 ▲0.11 | 43.59 ▼1.45 |
Dashboard /wp-admin | 2,243 ▲55 | 5.86 ▲0.01 | 101.81 ▼17.53 | 78.59 ▲35.60 |
Posts /wp-admin/edit.php | 2,120 ▲31 | 2.03 ▲0.01 | 34.96 ▼2.63 | 29.56 ▼5.64 |
Add New Post /wp-admin/post-new.php | 1,696 ▲182 | 22.18 ▲4.66 | 793.66 ▲154.22 | 58.78 ▲6.61 |
Media Library /wp-admin/upload.php | 1,422 ▲37 | 4.16 ▼0.02 | 98.59 ▼1.04 | 46.20 ▲3.96 |
Eewee Flattr /wp-admin/admin.php?page=idEeweeFlattr | 795 | 2.02 | 23.88 | 22.56 |
Manual /wp-admin/admin.php?page=idSousMenuFlattr | 904 | 1.86 | 24.23 | 35.55 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- This plugin cannot be uninstalled
- > Warning in wp-content/plugins/eewee-flattr/controllers/EeweeFlattr.php+2
Use of undefined constant EeweeFlattr - assumed 'EeweeFlattr' (this will throw an Error in a future version of PHP)
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 0% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These server-side errors were triggered
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=idSousMenuFlattr
- > Warning in wp-content/plugins/eewee-flattr/controllers/EeweeFlattr.php+2
Use of undefined constant EeweeFlattr - assumed 'EeweeFlattr' (this will throw an Error in a future version of PHP)
- 8 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=idSousMenuFlattr
- > Notice in wp-content/plugins/eewee-flattr/controllers/EeweeFlattr.php+117
Undefined property: EeweeFlattr::$adminOptionsName
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=idSousMenuFlattr
- > Warning in wp-content/plugins/eewee-flattr/controllers/EeweeFlattr.php+30
Use of undefined constant menu - assumed 'menu' (this will throw an Error in a future version of PHP)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=idSousMenuFlattr
- > Warning in wp-content/plugins/eewee-flattr/controllers/EeweeFlattr.php+32
Use of undefined constant sousMenu1 - assumed 'sousMenu1' (this will throw an Error in a future version of PHP)
SRP 0% 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
Please fix the following
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/eewee-flattr/view/manual.php
- 4× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/eewee-flattr/index.php:18
- > PHP Fatal error
Uncaught Error: Class 'form_add_twitterCard' not found in wp-content/plugins/eewee-flattr/view/flattr.php:14
- > PHP Warning
Use of undefined constant WP_PLUGIN_DIR - assumed 'WP_PLUGIN_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/eewee-flattr/index.php on line 18
- > PHP Warning
Use of undefined constant EeweeFlattr - assumed 'EeweeFlattr' (this will throw an Error in a future version of PHP) in wp-content/plugins/eewee-flattr/controllers/EeweeFlattr.php on line 2
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There are user-side issues you should fix
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=idSousMenuFlattr
- > Network (severe)
wp-content/plugins/eewee_flattr/css/style.css?ver=6.3.1 - Failed to load resource: the server responded with a status of 404 (Not Found)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=idSousMenuFlattr
- > Network (severe)
wp-content/plugins/eewee_flattr/img/icon.png - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/admin.php?page=idSousMenuFlattr
- > Network (severe)
https://tools.flattr.net/widgets/thing.html?thing=1090157 - Failed to load resource: the server responded with a status of 502 ()
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Screenshots: Screenshot #1 (Code QR.) image required
eewee-flattr/index.php 92% from 13 tests
This is the main PHP file of "eewee flattr" version 1.1, 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: Please rename the main PHP file in this plugin to the plugin slug ("eewee-flattr.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected169 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 52 | 81 | 149 |
PO File | 1 | 29 | 58 | 20 |
CSS | 1 | 0 | 1 | 0 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.16 |
Average class complexity | 5.00 |
▷ Minimum class complexity | 5.00 |
▷ Maximum class complexity | 5.00 |
Average method complexity | 1.40 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.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 | 10 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 10 | 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 | 4 | |
▷ Global constants | 4 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
img/icon.png | 3.44KB | 0.99KB | ▼ 71.23% |