Continuing the gentle intro to #webperf series - How to load #javascript for faster web pages using the async and defer attributes
https://t.co/HuK8cDmXAn #frontenddev
Part of a SUPER gentle intro series (for noobs). Showing some base knowledge required for web performance. Part 1 begins to introduce the fundamentals of #javascript execution order https://t.co/sIx9EVETIi
#webdev
Thinking about building something a bit special in terms of user experience monitoring. Take a look here: https://t.co/lqfCUn3H0v
If you like what you see, please sign up for notifications. Also, sharing is caring, so please share!
#webperf#Analytics
New Feature! Resource Analysis gives you strong indicators where to focus effort when optimising perf https://t.co/fkg1w2aWoc #webperf#FrontEnd#performance#javascript
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
Waterfalls made of RUM! Our latest feature makes it easy to figure out exactly what is making real user loads slow! https://t.co/5GPf7lH6qU #webperf#frontenddev
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
Hot off the press. New post in the series Diagnosing website issues: Part 2 Let your systems tell you what is wrong #webdev#FrontEndDevelopment https://t.co/2bqqvghoGe
@simonhearne Any idea why that call is seen on wpt but not devtools ? We thought perhaps the calls might be quite platform specific though I’m not sure
Audited your Core Web Vitals (LCP, FID, CLS) recently?
1. Deploy RUM analytics to get a baseline & monitor.
2. Use Search Console to identify where to invest.
3. PageSpeed Insights+Lighthouse for page diagnostics.
4. Fix, launch, validate, go to 2.