getBoundingClientRect width vs offset width (version: 1)

Comparing performance of: getBoundingClientRect vs Access offset properties directly

Created: one year ago by: Guest
Go to the latest result
HTML Preparation code:
Script Preparation code:
Tests:

Historical Performance Data aggregated from 5 community runs

Desktop Results:
Chrome 5 runs
Access offset properties directly
3.7M/s
getBoundingClientRect
2.3M/s

Fastest: Access offset properties directly (1.6x faster)

View exact numbers
  • ✓ Access offset properties directly: 3,681,533 ops/sec
  • • getBoundingClientRect: 2,270,326 ops/sec

Results show median performance across all community submissions. Run this benchmark yourself to verify on your device.

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results
  • Test case name Result
    getBoundingClientRect
    Access offset properties directly

    Fastest: N/A

    Slowest: N/A

Latest run results:
Run details: (Test run date: 8 months ago)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36
Chrome 142 on Windows
View result in a separate tab
Access offset properties directly
2.0M/s
getBoundingClientRect
1.3M/s
View exact numbers
Test name Executions per second
✓ Access offset properties directly 2,042,353 Ops/sec
getBoundingClientRect 1,262,629 Ops/sec

Related benchmarks