Benchmark: addEventListener('resize') + innerWidth VS matchMedia() + matchMedia.addEventListener('change')

addEventListener('resize') + innerWidth VS matchMedia() + matchMedia.addEventListener('change') (version: 0)

This benchmark compares using `addEventListener('resize')` with window.innerWidth versus window.matchMedia with it's`addEventListener()` function to see which is faster.

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 matchMedia = window.matchMedia("(min-width: 400px)"); matchMedia.addEventListener('change', event => { if (event.matches) { console.log(true); } })
resize + innerWidth
let currentWidth = window.innerWidth; window.addEventListener('resize', () => { currentWidth = window.innerWidth; }); if (currentWidth > 400) { console.log(true); }

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

Autogenerated LLM Summary (model llama3.1:latest, generated one month ago):

LLMs can make mistakes. Check important info.

Let's break down the benchmark.

**What is being tested?**

This benchmark compares two approaches to detect and respond to changes in the window size (i.e., resizing the browser):

1. Using `window.addEventListener('resize')` with `window.innerWidth` to monitor the current width of the window.
2. Using `window.matchMedia()` with its `addEventListener('change')` function to check if the media query `(min-width: 400px)` is matched.

**What are the options being compared?**

The two test cases compare different ways to detect when the window width exceeds a certain threshold (400 pixels in this case):

1. **Test Case 1:** `matchMedia + addListener` uses `window.matchMedia()` to create a media query listener and listens for changes to the `(min-width: 400px)` condition.
2. **Test Case 2:** `resize + innerWidth` uses `window.addEventListener('resize')` to listen for window resize events and updates the `currentWidth` variable with the new width.

**Pros and Cons of each approach:**

1. **MatchMedia + addListener (Test Case 1)**:
	* Pros:
		+ More accurate, as it checks if the media query is matched.
		+ Can handle cases where the window size is not exactly at the threshold value (e.g., 399px).
	* Cons:
		+ May be slower than using `window.addEventListener('resize')`, as it has to create a media query listener and check for changes.
2. **Resize + innerWidth (Test Case 2)**:
	* Pros:
		+ Generally faster, as it only listens for window resize events.
		+ Can be more efficient, especially if the threshold value is close to the current width.
	* Cons:
		+ May not account for cases where the window size is not exactly at the threshold value (e.g., 399px).

**Other considerations:**

* The benchmark results show that `matchMedia + addListener` performs significantly better than `resize + innerWidth` on Chrome 98, with an execution rate of ~175k/sec versus ~1.7k/sec.
* This suggests that using `window.matchMedia()` with its `addEventListener('change')` function is a more efficient approach for detecting window size changes.

**Library and special JS features used:**

None mentioned in the provided JSON data.

**Alternatives:**

Other alternatives to achieve similar functionality might include:

1. Using `ResizeObserver` API (available in Chrome 76+), which provides a more precise way of observing changes in the element's layout.
2. Implementing custom logic using `window.addEventListener('resize')` and checking for specific width values, as done in `resize + innerWidth`.

Latest run results:

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

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.102 Safari/537.36 Edg/98.0.1108.62

Browser/OS: Chrome 98 on Windows

View result in a separate tab

Test name	Executions per second
matchMedia + addListener	175344.1 Ops/sec
resize + innerWidth	1716.7 Ops/sec

Related benchmarks: