Hi there,
I just don’t get it. I want to use F12 to check which plugins load slowly, but I just don’t understand the totals I see. The WordPress core gives a load time of 2+ seconds in admin (which might be a problem, but this is in a staging site full of plugins), but the total status 434 seconds!
What does this mean? And what does it mean when a simple script like jquery.imgareaselect.min.js has a time of 4.35 seconds? Is this the time since the First byte of the site or something?
Sorry for my ignorance,
Jelmer
]]>Hello,
There’s an issue with the 1.3.6 version download link. I use it because of bedrock and composer plugin updates, when updating it throws me an 404 error.
You can see the issue going to “Advanced View” on the plugin home page and clicking download in the 1.3.6 version.
]]>I have the exactly same issue another user had a year ago: the plugin is installed and activated but nothing is shown in the admin bar. I don’t see any error in the JavaScript console and there are no F12 scripts loaded. All empty.
]]>Hi!
On my website, I see this code:
<script type='text/javascript' src='https://mysite.com/wp-content/plugins/f12-profiler//assets/measure.js?ver=c11e08bdb4bde06fe2dcbc28ddad802d' id='f12p_measure-js'></script>
– double slash before assets
It can be fixed?
Hi, I was hoping to find a way to analyse the long TTFB time I get on my website.
For instance, the linked page shows TTFB of 2s on local geography connection.
F12 plugin reports 0.22s consumed by core and various plugins and themes.
A static file has TTFB of 20-60ms so it is still about unknown PHP processes that consumes the remainder of 1.8s
Any idea how to pinpoint this problem?
]]>This plugin definitely fills the gap left by P3 Profiler. I’m also happy to report it is working fine with WordPress 5.5 RC2 and jQuery 3.5.1 (with Migrate 3.3).
My frustration is there is no documentation. Yes, what it does is pretty basic and helpful but there are results in 3 colours.
Green – means good (the obvious understanding)
White – what purpose is this colour, is this the baseline?
Red – means bad but why, what is it measured against and what can be done?
Please take a few minutes and put together some basic info to help us along.
Thanks
]]>Hello,
I tried to install the plugin in my wordpress website. After installing it and activating it, I found nothing shown in the admin menu bar like the screenshot you show. My wordpress version is 5.2.4.
Is there any ideas the profiler not display?
Thank you.
I don’t mind a plugin having a required PHP version, but when it stops all pages on the site from loading, that is unreasonable.
Due to problems with my hosting company, the version of PHP was switched to an earlier version and suddenly all pages on the website displayed a message about F12 requiring PHP 7.
It seems to me that if a plugin cannot work with some of the available support software, then it should fail silently, or with a log message, but it should not take down the entire site!
]]>So I get the concept, wp-admin loading.
Causing a 503 on front-end, so that’s a deal breaker.
Also at the top of my list in dashboard is WP native scripts, and everything below is green, except:
Core: 0.2683s at top
then
f12-profiler *Core: 0.1301s*
No idea what ‘core’ means the 2nd time.
And given I’m running elementor it’s clearly missing the ton of scripts that come with that, and not sure what I’m meant to do with this info, also the whole not loading pages, so it’s only for dashboard?
So, confused as to what this is *meant* to be doing . . . ?
]]>Terrific plugin! After P3 doesn’t work anymore with PHP7+, F12 Profiler seems finally filling the gap.
A few suggestions:
a) Make the resource hogs go to the top of the list:
\plugins\f12-profiler\f12-profiler.php
~line 60 add the following line:
$data = \f12_profiler\includes\TimeTracker::get();
arsort($data); //<-- add
b) When the list of plugins is too large and goes beyond the screen bottom, need to make that list scrollable. It can be achieved with the following adjustment in styles.css of the child theme:
#wp-admin-bar-f12_profiler_1-default
{ height: 200px; overflow: auto }
Hope you’d consider adding similar to those tweaks for the next version.
Thanks!
]]>