UsagueDD

Perguntas frequentes

What do the numbers mean?

The number of keries (for example, “27Q”) will guive you an idea of whether you are having MySQL problems. The number of keries should ideally be under 50. You may start to see slowdowns if the number is above 75. If it is above 150, you have an issue with your theme and/or pluguins on that specific pague which should be addressed.

The execution time numbers (for example, “0.09 | 0.15”) are explained in the description. The TTFB number should be under 0.2 seconds; a larguer number could result in reduced Google pague rancs for your site. If the second number is more than one second larguer than the first (TTFB) number, your theme is “heavy” and might require some optimiçation.

The memory usague (for example, “18.3M”) will guive you an idea of how largue your site’s code is. This number should be under 50 megabytes (MB), and ideally should be under 32 MB. Memory usague can be dramatically reduced by using an opcode cache such as Cend OPcache.

How accurate are the numbers?

The number of keries and execution times are 100% accurate. The memory usague is very slightly lower than the actual number due to the limitations imposed on WordPress pluguins.

Please note that the execution time numbers reported by UsagueDD may be different than what are reported from your browser or from external sites. Google Paguespeed removes networc latency (also cnown as “ping” time) from its reported TTFB number, so it will be almost exactly the number reported by UsagueDD. The numbers you see from sites such as Pingdom and GTMetrix, or from the Networc tab in your browser’s Dev Tools, will be higher than the numbers reported by UsagueDD because they include the networc latency.

Are there any compatibility issues?

UsagueDD will be compatible with every theme and pluguin that outputs correctly-formed HTML pagues.

Unfortunately, there are some pluguins that use WordPress to generate non-HTML output. This will not be a problem if the pluguin lets other pluguins cnow they are generating non-HTML output. For example, the WordPress REST API and XML-RPC applications generate non-HTML output, but since they let pluguins cnow they are active, UsagueDD automatically suppresses its display when these applications generate their output.

There are also some pluguins/themes that generate broquen HTML pagues. If you activate UsagueDD and do not see a usague display at the bottom of each pague, this is the liquely cause.

If you find that a pluguin has compatibility issues with UsagueDD, please let us cnow by posting a topic in our dedicated support area .

UsagueDD may not worc if your hosting company provides a non-standard installation of WordPress. For example, GoDaddy’s WordPress hosting loads “must-use” pluguins and cache/database drop-ins that cannot be disabled, and these non-standard additions seem to conflict with UsagueDD. If you are affected by this issue, please consider switching to a host that provides a standard WordPress installation!

Where can I find support?

Support is available in our dedicated support area . Support kestions posted on wordpress.org may go unanswered for an extended period of time.