Benchmark: 8x addEventListener('resize') VS matchMedia()

8x addEventListener('resize') VS matchMedia() (version: 0)

This benchmark compares using `addEventListener('resize')` with window.innerWidth VERSUS window.matchMedia with its `addListener()` function to see which is faster, when checking multiple conditions (8 different sizes, in this case).

Comparing performance of: matchMedia + addListener vs resize + innerWidth

Created: 2 years ago by: Registered User

Jump to the latest result

HTML Preparation code:

<style>
  #before:before {
  	content: "a";
 	 display: none;
  }
  @media(min-width: 200px) {
  	#body {
  		background: red;
  	content: "b";
  	}
  }
  @media(min-width: 600px) {
  	#body {
  		background: blue;
  	content: "c";
  	}
  }
  @media(min-width: 1000px) {
  	#body {
  		background: yellow;
  	content: "d";
  	}
  }
</style>
<div id="body">
</div>

Tests:

matchMedia + addListener
const matchMedia400 = window.matchMedia("(min-width: 400px)"); matchMedia400.addListener((query) => { if (query.matches) { console.log("400", true); } }) const matchMedia500 = window.matchMedia("(min-width: 500px)"); matchMedia500.addListener((query) => { if (query.matches) { console.log("500", true); } }) const matchMedia600 = window.matchMedia("(min-width: 600px)"); matchMedia600.addListener((query) => { if (query.matches) { console.log("600", true); } }) const matchMedia700 = window.matchMedia("(min-width: 700px)"); matchMedia700.addListener((query) => { if (query.matches) { console.log("700", true); } }) const matchMedia450 = window.matchMedia("(min-width: 450px)"); matchMedia450.addListener((query) => { if (query.matches) { console.log("450", true); } }) const matchMedia550 = window.matchMedia("(min-width: 550px)"); matchMedia550.addListener((query) => { if (query.matches) { console.log("550", true); } }) const matchMedia650 = window.matchMedia("(min-width: 650px)"); matchMedia650.addListener((query) => { if (query.matches) { console.log("650", true); } }) const matchMedia750 = window.matchMedia("(min-width: 750px)"); matchMedia750.addListener((query) => { if (query.matches) { console.log("750", true); } })
resize + innerWidth
let currentWidth = window.innerWidth; window.addEventListener('resize', () => { currentWidth = window.innerWidth; }); switch (currentWidth) { case 400: console.log("400", true) break case 500: console.log("500", true) break case 600: console.log("600", true) break case 700: console.log("700", true) break case 450: console.log("450", true) break case 550: console.log("550", true) break case 650: console.log("650", true) break case 750: console.log("750", true) break }

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
matchMedia + addListener
resize + innerWidth

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 2 years ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36

Browser/OS: Chrome 110 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
matchMedia + addListener	64544.1 Ops/sec
resize + innerWidth	2723.5 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated 2 months ago):

LLMs can make mistakes. Check important info.

I'll break down the benchmark and its individual test cases.

**Benchmark Definition**

The benchmark compares two approaches for checking multiple conditions:

1. Using `addEventListener('resize')` with `window.innerWidth` (Test Case: "resize + innerWidth")
2. Using `matchMedia()` with `addListener()` function (Test Case: "matchMedia + addListener")

**Options Compared**

Both approaches have the following options:

* Minimum width for each condition (400px, 500px, 600px, 700px, 450px, 550px, 650px, 750px)
* Action to take when a condition is met (logging "condition value", true)

**Pros and Cons**

### `addEventListener('resize')` with `window.innerWidth`

Pros:

* Easy to implement
* No additional libraries needed
* Works on all devices (not just desktops)

Cons:

* Can be slower due to the need to listen for every resize event
* Requires more JavaScript code
* Not optimized for multiple conditions

### `matchMedia()` with `addListener()`

Pros:

* Optimized for multiple conditions, reducing unnecessary computations
* Faster than `addEventListener('resize')`
* Easier to manage and maintain, especially for complex media queries

Cons:

* Requires additional libraries (Media Query List)
* May not work on older browsers or devices without Media Query List support
* More complex to implement compared to `addEventListener('resize')`

**Library: Media Query List**

The `matchMedia()` function uses the Media Query List library, which provides a more efficient way to check multiple conditions. The `addListener()` method is used to listen for changes in the media query results.

**Special JS Features/Syntax**

None mentioned in this benchmark definition.

**Other Alternatives**

If you need an alternative approach, consider:

1. Using `requestAnimationFrame()` instead of `addEventListener('resize')` for smoother animations and updates.
2. Implementing your own custom media query system using JavaScript events or Web Workers.
3. Utilizing other libraries like `css-media-queries` or `media-query-list-lite` to simplify Media Query List usage.

These alternatives might be suitable depending on the specific requirements of your project, but they may also introduce additional complexity and overhead.

Related benchmarks: