Test Plugin 3 wordpress plugin resources analysis
| Download This Plugin | |
| Download Elegant Themes | |
| Name | Test Plugin 3 |
| Version | 1.1-20150204 |
| Author | Dion Hulse |
| Rating | 0 |
| Last updated | 2015-02-04 06:09:00 |
| Downloads |
18
|
| Download Plugins Speed Test plugin for Wordpress | |
Home page
Delta: 0%
Post page
Delta: 0%
Home page PageSpeed score has been degraded by 0%, while Post page PageSpeed score has been degraded by 0%
Test Plugin 3 plugin added 14 bytes of resources to the Home page and 10 bytes of resources to the sample Post page.
Test Plugin 3 plugin added 0 new host(s) to the Home page and 0 new host(s) to the sample Post page.
Great! Test Plugin 3 plugin ads no tables to your Wordpress blog database.For best README.md support, the fields under the plugin title, Contributors.. Tags.. etc, should be in a similar format to this readme example. This means that there should be no characters after the : other than the value, no formatting, just a value and new line.
This is the long description. No limit, and you can use Markdown (as well as in the following sections).
For backwards compatibility, if this section is missing, the full length of the short description will be used, and Markdown parsed.
A few notes about the sections above:
- "Contributors" is a comma separated list of wp.org/wp-plugins.org usernames
- "Tags" is a comma separated list of tags that apply to the plugin
- "Requires at least" is the lowest version that the plugin will work on
- "Tested up to" is the highest version that you've successfully used to test the plugin. Note that it might work on higher versions... this is just the highest one you've verified.
Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use
/trunk/for stable.Note that the
readme.txtof the stable tag is the one that is considered the defining one for the plugin, so if the/trunk/readme.txtfile says that the stable tag is4.3, then it is/tags/4.3/readme.txtthat'll be used for displaying information about the plugin. In this situation, the only thing considered from the trunkreadme.txtis the stable tag pointer. Thus, if you develop in trunk, you can update the trunkreadme.txtto reflect changes in your in-development version, without having that information incorrectly disclosed about the current stable version that lacks those changes -- as long as the trunk'sreadme.txtpoints to the correct stable tag.If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where you put the stable version, in order to eliminate any doubt.
