It’s easy to get excited about new techniques for measuring and improving site speed but this focus on the technical side of performance can lead us to think of speed as a technical issue, rather than a business issue with technical roots.
Automation typically includes purely code-based tasks that don’t even think about a browser, but some tasks need to interact and use the browser as a human would like performing a search on a site. How can we leverage tools that can automate the browser and pack it into a serverless API endpoint to make easily accessible?
Render-blocking resources are a common hurdle to rendering your page faster. They impact your Web Vitals which now impact your SEO. Slow render times also frustrate your users and can cause them to abandon your page.
You now have a simple, platform-reliant way of preventing unnecessary requests. You have another tool in your belt to save your users time and money. Also you’ve got a way to save a little carbon from being released into our atmosphere to power a server farm. And you can use this tool with any style of website: static file sites, single page applications, and server rendered applications. It’s a superpower.
One of the great things about Eleventy is its flexibility and its lack of assumptions about how your projects should be organized. However, in order to preserve my own sanity, I needed to come up with a default files and folders architecture that made sense to me.
Putting images on websites is incredibly simple, yes? Actually, yes, it is. You use <img> and link it to a valid source in the src attribute and you’re done. Except that there are (counts fingers) 927 things you could (and some you really should) do that often go overlooked. Let’s see…
As we have seen, the for-of loop beats for, for-in, and .forEach() w.r.t. usability.
Any difference in performance between the four looping mechanisms should normally not matter. If it does, you are probably doing something very computationally intensive and switching to WebAssembly may make sense.
Nous avons demandé à Hubert Guillaud, Rédacteur en chef d’InternetActu et analyste des grands mouvements et phénomènes qui traversent le champ du numérique et de la politique, son avis sur la possibilité d’une politique publique (progressiste) du numérique. « Nous sommes cernés par des systèmes néolibéraux augmentés par le numérique et les systèmes numériques de gauche sont...
Hey John! In France, we don't learn to give positive feedback. A few months ago, I started working with many more people from other cultures and I felt unable to show them appreciation as I would have liked. Your article has helped me to better understand how to express my gratitude and have it received in a constructive way. Thank you for continuing to write such helpful articles.
Ces technologies peuvent apporter un confort supplémentaire à certains utilisateurs. Cependant, les outils de surcouche d’accessibilité sont des solutions partielles qui ne doivent pas occulter le véritable enjeu de l’accessibilité numérique : le développement de sites et applications accessibles pour tous, uniquement garanti aujourd’hui par le respect du RGAA.