@TimVereecke If argue visitors with a "good" lcp don't care care about that either. Unfortunately it's a very broadly researched number and won't make sense for all sites
Thinking about building something a bit special in terms of user experience monitoring. Take a look here: https://t.co/WruNLwDJh9
If you like what you see, please do add your email to help give an idea of its usefulness. Also, sharing is caring, so please share!
@obeattie Unit tests as a regression guard fail when we refactor at a higher "unit". Subtleties and edge cases in the now-deleted code and corresponding tests are lost immediately. That's a long way of saying I agree
@Steve8708 I don't think it's precisely codebase size that matters, but to be pedantic it's more functionality being added. Poor organisation of execution, network calls, redraws etc. The browsers and networks do what they do pretty well. We do the silly things
@Steve8708@____lighthouse I'm biased here, but I'd argue that a RUM solution is better for tracking. Don't get me wrong, lighthouse is amazing, but it runs under controlled conditions. Good for a snapshot check and build pipelines (which RUM can't do obvs)
@TimVereecke@__treo Point 2 is almost good enough on its own. As for "proof", I've been building a thing to try to do just that https://t.co/tPFt6HV0uk
(actually wanted to dm first, not trying to advertise, but I do think it is genuinely important)
Controversial? Purely in terms of #webperf (i.e cost per MB aside), page WEIGHT doesn't matter, but page WAIT does. Weight optimisations aren't always (very) effective because of browser optimisations. Subtle shift to focus on WAIT means a focus on user
Hope this can help others. We ran into an issue where Nock wasn't recording all requests as expected. "You'll never guess what solution came next"! https://t.co/tYHHYlzELg #SoftwareTesting