Recurring themes in code and how to optimize them.
A team to give web developers a voice in the standards process.
Wear a beanie today, build the web tomorrow.
How engines interpret and optimize your code.
Take time to develop and think about your craft.
Small things that can be performance bottlenecks.
A collection of Chrome DevTools extensions.
App development for multiple browsers.
“Sure flat design is a design trend, but it is good for performance.”
Cross-device testing with Browser-Sync.
“If a task can be done in less than two minutes, do it right now.”
Automation of all the tasks.
How to build tasks to remove unused CSS.
“The way that languages in the web platform evolve are in direct response to the pain caused by complexity.”
Five things to keep in mind.
Say goodbye to complicated data-binding code.
“Mutation Observers are certainly worth familiarising yourself with.”
Introducing PageSpeed Insights for Node.
How to effectively keep memory usage down.
“Linting your code early and often is the best way to avoid issues building up.”
Visualize what parts of a node have changed.
Work in progress, contributions are welcome.
Defining strings with domain-specific languages.
JSCS can now reformat code, not just validate it.
How to stay productive with web tooling.
Improved starting point for building web applications.
Tools for keeping images lean.
What it is and how it works.
How you can build a modern web app in your favorite framework.
How you can craft offline, lightning fast web apps.
Guidance and tooling for inclusive web experiences.
“2016 will hopefully be the year we build for network resilience.”
“The web’s success came from working together. Let’s collaborate more.”
What might slow down rendering and how you can fix it.
Service Worker, Web Push, Analytics libraries, and real-world sites.
Ways to reduce image size through modern compression techniques.
Best practices for making real-world sites load instantly today.
“Be humble, communicate clearly, and respect others. It costs nothing to be kind, but the impact is priceless.”
A benchmark for modern web app responsiveness.
How the bundling tool can help to optimize site resources.
What you can do to speed up things.
Many small changes can lead to big performance gains.
Let’s make performance part of project goals from the start.
“Keep code simple. Make it easy to read and maintain by others. Design patterns are great, but use them when it’s clear they add value.”
Where to implement logic and rendering in web apps.
How Chrome schedules and executes scripts.
Chrome soon supports the loading attribute.
New launches from Google I/O 2019.
The dominant costs are now download and CPU execution time.
“On projects: Done is better than none. It’s easy to set expectations so high you never finish. Sometimes ‘done’ is enough. Ship then iterate.”
Browser-level native lazy-loading is finally here.
A way to automate website performance measurement.
“It’s okay to admit when you don’t know something. One of the most important skills in software is being able to find answers and learn from them.”
“‘If you want to go fast, go alone. If you want to go far, go together.’ You can do so much with a great team.”
“If you want a fast site, test on slow hardware. Regularly.”
Recipes for automating web performance measurement.
How to find out what DOM nodes have an unexpected scrollbar.
A tiny library to speed next-page navigations by prefetching in-viewport links.
Steven Hoober’s guidelines for UI designers in a nutshell.
Google‘s tools for web developers now deliver essential UX metrics.
“border: 1px solid red; is the console.log of CSS.”
Browser-level native lazy-loading for iframes is here.