Extension talk:PerformanceInspector

About this board

Does it work at all under MediaWiki 1.35?

Alex Mashin (talkcontribs)

I have it installed and enabled in my user preferences. However, the hook function PerformanceInspectorHooks::onBaseTemplateToolbox is never called, although PerformanceInspectorHooks::onBeforePageDisplay is. It seems that the hook BaseTemplateToolbox is gone from MediaWiki 1.35, although it is documented as deprecated.

Reply to "Does it work at all under MediaWiki 1.35?"

The inspector does not show up

Gryllida (talkcontribs)
Quiddity (WMF) (talkcontribs)

I think that's covered by phab:T186789. Thanks for the bug-report. :)

Reply to "The inspector does not show up"

Looks like a wikia tool (Special:ParserSpeed)

2 (talkcontribs)

This is interesting and works a lot like the wikia tool, ParserSpeed. Maybe it can either use the description from there, or add more things based on its usefulness.

Krinkle (talkcontribs)

Thanks. I looked through the source code but didn't find anything salvageable. It mainly displays the stats from the Parser, which we report already.

Meanwhile, the extension was removed by Wikia per https://github.com/Wikia/app/pull/12542.

Make it more user friendly

2 (talkcontribs)

It is easy to understand why the developers of this extension designed it with emphasis on numbers. But one should consider that 99% of users aren't technically inclined.

Instead of focusing on those numbers it would be more useful to hide these as advanced options, and make it possible for the average user to understand the impact of the page. For example, some actionable data might be recommended sizes:

Data Cur tot size Recom. size Cur no. Recom. No. Mobile load times (200KB/s)
Images 500KB <300KB 60 < 50 30s
Markup (links , tags) 700 <200 2s
Other (CSS, js, other) 100KB <50KB 10s
Total 600KB <350KB <200 42s

These are just made up numbers that hopefully make it is easy to get the general idea. The difference is that this is something that users can see and do something about (reduce images, reduce markup) without understanding core principles about website design or performance or worrying too much about things they can't do anything about (e.g. CSS, JS, etc).

Pie charts and colors for performance status, might also be meaningful way to indicate general page status (e.g. RED - very bad performance, green - fine), although people can just implement that using userscripts. (talkcontribs)
Reply to "Make it more user friendly"
There are no older topics