At least 10% of our user population has a non-default theme installed.

That's pretty sizeable, and it makes sense to have some performance test coverage for that case (where we've been otherwise flying pretty blind).

I suggest we create variations of ts_paint, tpaint and startup_about_home_paint using these two themes:

Non-animated: https://addons.mozilla.org/en-US/firefox/addon/dark-fox-18066/?src=search (Creative Commons Attribution-ShareAlike 3.0)

Animated: https://addons.mozilla.org/en-US/firefox/addon/-animated-dark-fox/?src=search (Creative Commons Attribution-NonCommercial 3.0)

I think both have permissive licenses, so long as we give attribution to the authors.

See also comment #0 from the duplicate bug:

Here are some configurations worth measuring:

• Lightweight theme parity (accentcolor/textcolor/headerURL)
• Extreme theme (all properties)
• Sidebar properties
• In-content properties

For the animated theme case, bug 1457759 is about a CPU issue with a animated SVG theme. (might be a good stress test ?)

Hi Mike,
I just wanted to followup with you and see if this is still an issue

Hi andrej,

Yeah, I think this is still a good idea - especially as we promote more and more non-default themes with things like Colorways, we're going to want to make sure we've got some startup perf coverage for those states (and right now, we don't).