(In reply to Alexandru Ionescu (needinfo me) :alexandrui from comment #6)
Sparky, I'm thinking we could standardize the way the config is built as this framework based approach seems fairly simple to make structure app (perfdocs) wide. Doing this will be simpler to add descriptions without missing something (because the structure of the config will be the same as the one in html) and will save us extra processing in the code (pretty error prone).
The config is already standardized but I see what you mean. Although, you should provide a more concrete example of what you are proposing because it's not very clear.
I agree that we could change the config structure to better reflect the HTML page, but it is already very close to mirroring it. Regardless of this point, we should still implement the two changes in comment #5 (1, and 2) so that we can let the framework classes handle their own descriptions - it'll get rid of the "browsertime" from the main code which shouldn't be there since it's framework-specific.
We can build off this in any config changes that come afterwards.