![]() ![]() The timeout of the profiler’s process was increased from 180 to 300 seconds.Added screen reader accessibility to all 3 graphs (Plugins and Theme, File I/O, Disk I/O).It is possible to edit the name of a profile by clicking the “Quick Edit” row action link below its name in the profiles list.Fixed a potential “404 Not Found” HTTP error when the site home page is different from the WordPress installation directory.Added a warning if the WordPress MU folder is not writable.Added a “Debug” checkbox below the log that can be used to increase its verbosity.The log will be automatically deleted when it reaches 100KB.: When viewing a file, its name will be displayed in the title bar of the browser.Improved the system information report.It shows all HTTP connections originating from your WordPress website and includes the URL, the HTTP status code, the duration and, as usual, a full backtrace. : We added a new section: Remote Connections.Added a hook to prevent a timeout if a plugin changed cURL timeout options (props Several small fixes and adjustments.Fixed an issue where the execution time in the “Plugins & Theme Performance” section did not include any occurred remote connection.The profiler will disable the PHP display_errors directive so that potential notice, warning and error messages won’t mess up with the AJAX response.It can be found in “Settings > Buffer size”. A new option was added to tweak the size of the memory buffer used by the profiler.See “Advanced Options > HTTP headers” in the profiler’s main page. Added the possibility to send custom HTTP headers when profiling a site.Fixed potential PHP error when calling number_format function.Your website can run Code Profiler and be compliant with the General Data Protection Regulation (GDPR) or other similar privacy laws. What are the requirements for running Code Profiler?Ĭode Profiler does not collect any private data from you or your visitors. Note however that for security reasons, only the superadmin can run it. Is Code Profiler multisite compatible?Ĭode Profiler is multisite compatible. There’s no need to deactivate Code Profiler when you don’t use it, it has no performance impact on your site.īecause an update can affect the performance of your site, you should consider running it after every plugin or theme update. Do I need to deactivate Code Profiler when I’m not using it ? Google PageSpeed and GTmetrix, instead, analyze the content of a web page from a browser’s perspective. They are completely different: Code Profiler analyzes the code performance of your plugins and themes on your server, at the PHP level. Export all tables and charts in CSV file format.įAQ What are the differences between Code Profiler and services such as Google PageSpeed or GTmetrix?.GET/POST methods, custom cookies and HTTP headers.Methods & functions performance profiling. ![]() ![]() Plugins & themes performance profiling.Install, activate it and you can start profiling your site right away. It makes it very simple to locate any bottleneck problem in your themes or plugins in order to solve it and speed up your website. It displays many useful additional information such as database queries, file I/O operations and disk I/O usage as well. It generates an extremely detailed and easy to read analysis in the form of charts and tables that shows not only which plugin or theme, but also which PHP script, class, method and function is slowing down your website. You can profile the frontend and backend of WordPress, a custom URL, or even send a POST payload, custom cookies and HTTP headers to profile a contact form, a checkout process or an AJAX action among many other possibilities. ![]() Description A profiler to measure the performance of your WordPress plugins and themes.Ĭode Profiler helps you to measure the performance of your plugins and themes at the PHP level and to quickly find any potential problem in your WordPress installation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |