Preview popups are common and requires careful scripting and styling; they can generate useful learning about performance as a reference for other front-end tasks.
The story of how we decided to commission the implementation of Paint Timing API, a feature that lets us observe web performance from an end-user perspective. This web browser feature tells us at what point in time content started to appear on the screen for a visitor.
We have been collecting microbenchmark scores for over a year. This lets us see the long-term evolution of our audience as a whole. The information gives us an idea of how fast device/operating system/browser environments improve on their own.
For FOSDEM 2020, the Wikimedia Performance Team organized a Web Performance devroom. In this post, they share their experience.
WikimediaDebug is a set of tools for debugging and profiling MediaWiki web requests in a production environment. WikimediaDebug can be used through the accompanying browser extension, or from the command-line. This post highlights changes we made to WikimediaDebug over the past year, and explains more generally how its capabilities work.
We’re taking part in the ongoing Event Timing Chrome origin trial, in order to experiment with that API early and give feedback to its designers.
When we set out to ask Wikipedia visitors their opinion of page load performance, our main hope was to answer an age-old question: which RUM metric matters the most to users? And more interestingly, which ones matter the most to our users on our content.
Unlike most websites, Wikipedia and its sister projects are ad-free. This is actually one of the reasons why our performance is so good. We don’t have to deal with slow and invasive third-parties.
We’ve recently published research on performance perception that we did last year. The micro survey used in this study is still running on multiple Wikipedia languages and gives us insights into perceived performance.