Skip to main content

Improve the performance of your web applications by adding one attribute

Images are critical for every website and web application today. As images can be quite large, they can have a big impact on the percieved performance (and than I don't even mention the bandwith cost).

Before you start converting all your images to the webp format or implementing all kind of crazy javascript and css hacks, I’ll learn you a simple trick that could help you a lot…

You can lazy load your images using the loading attribute.  By using lazy loading, the images in your application or site will only be loaded when they become in reach of the visible are of your website. So as long as a user doesn’t scroll, only what is visible at that moment will be loaded.

Here is a simple example:

<img src="example.jpg" loading="lazy" alt="..." />

The following values are supported by the loading attribute:

  • lazy - Deferring the loading of assets till it reaches a certain distance from the viewport.
  • eager - loading the assets as soon as the page loads, irrespective of where they are placed on the page, whether above or below the page fold.
  • auto - This value triggers default lazy loading. Basically, it's the same as not including the loading attribute.

This feature is supported on most browsers (check caniuse) and if your browser doesn’t know this attribute it will just be ignored and your image will load immediatelly(which I think is an OK fallback).

 

Remark: If you want the remaining content from reflowing when a lazy-loaded image is downloaded, you can set the height and width attributes to the <img> element up front.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...