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.
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.
In the search for a better user experience metric, we have tried out the upcoming Element Timing for Images API in Chrome.
Should we be skeptical of performance guidelines which state that 100 milliseconds feels instantaneous to everyone?
We use both synthetic and RUM testing for Wikipedia. These two ways of testing performance are best friends and help us verify regressions. Today, we will look at two regressions where it helped us to get metrics both ways.
Let’s explore our web performance data from an angle we haven’t explored before: mobile device type.
Here is how we measure and interpret load times on Wikipedia. Let’s also look at what real-user metrics are, and how percentiles work.