Site Performance - WebOsu-2/webosu-2.github.io GitHub Wiki
This page is dedicated to measuring and documenting the performance and carbon footprint of WebOsu-2 using webpagetest.org
The purpose of this page is to compare the performance stats of as many WebOsu versions as possible in order to give us insights on what our performance priorities should be. This page also serves as historical documentation for the site's performance.
Settings
| Option | Value |
|---|---|
| Location | Dulles, Virginia USA |
| Connectivity | 5000/1000 Kbps, 28ms Latency |
| Test Run Count | 3 |
| Test Type | Desktop |
NOTES
- A value with an asterisk (*) signifies a performance issue that should be fixed with minor priority.
- A value with two asterisks (**) signifies a performance issue that should be fixed with major priority.
V0.5.0
This is the first version of WebOsu with documented performance.
Stats
| Field | Value | Description |
|---|---|---|
| Time to First Byte | .162s | When did the content first start downloading? |
| Start Render | .400s | When did pixels first start to appear? |
| First Contentful Paint | .449 | How soon did text and images start to appear? |
| Speed Index | 1.112s | How soon did the page look usable? |
| Largest Contentful Paint | 3.574s* | When did the largest visible content finish loading? |
| Cumulative Layout Shifts | .282** | How much did the design shift while loading? |
| Total Blocking Time | .182s | Was the main thread blocked? |
| Page Weight | 1,386KB | How many bytes downloaded? |
| Carbon Footprint | .21g | How eco-friendly is it? |
Notes on WebOsu v0.5.0
- Layout shifts are too much and too often, we must lower the stat.
- Image loading severely worsens the Largest Contentful Paint stat. Lazy-loading could be used to defer off-screen images from loading.