Skip to main content

Best practices to speed up your website

As mentioned by Jeff Atwood, ‘performance is a feature’. Having a fast and responsive web application really makes the difference. But how do you get there?

The best place to start is to have a look at the performance rules list created by the Exceptional Performance team at Yahoo. They have identified a number of best practices for making web pages fast. The list includes 35 best practices divided into 7 categories.

  • Content
    • Minimize HTTP requests
    • Reduce DNS lookups
    • Avoid redirects
    • Make Ajax cacheable
    • Post-load components
    • Preload components
    • Reduce the number of DOM elements
    • Split components across domains
    • Minimize the number of iframes
    • No 404s
  • Server
    • Use a Content Delivery Network
    • Add an Expires or a Cache-Control Header
    • Gzip components
    • Configre ETags
    • Flush the buffer early
    • Use GET for AJAX requests
    • Avoid empty image src
  • Cookie
    • Reduce cookie size
    • Use cookie-free domains for components
  • CSS
    • Put stylesheets at the top
    • Avoid CSS expressions
    • Make CSS external
    • Minify CSS
    • Choose <link> over @import
    • Avoid filters
  • JavaScript
    • Put scripts at the bottom
    • Make JavaScript external
    • Minify JavaScript
    • Remove duplicate scripts
    • Minimize DOM access
    • Develop Smart Event handlers
  • Images
    • Optimize images
    • Optimize CSS sprites
    • Don’t scale images in HTML
    • Make favicon.ico small and cacheable
  • Mobile
    • Keep components under 25K
    • Pack components into a multipart document

There’s also a tool available called YSlow which helps you to analyze web pages and suggests ways to improve their performance.

Popular posts from this blog

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.

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         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...