Today's update makes the WebGL Unity app load much more quickly on repeated loads.

On my machine, in Firefox 58, the app loads in about 4.8 seconds when loading from cache.

By "loading from cache" I mean I open it once, let it finish loading, then close it and load it again. The first time it has to download the app, all subsequent times it loads it from cache. So I'm looking here at the load speed of loading it out of the cache.

In Chrome it's still much slower (about 10 seconds), so I recommend switching to Firefox if you're still on Chrome.

If you use this special url, it will show the load times in the top right corner after loading, which helps for benchmarking: https://www.warzone.com/SinglePlayer?Unity=1&UnityStats=1 . The key number is the last one, where it says "Loading=XXXms" which is a number in milliseconds.

Want to experiment with faster loading times? Try going to https://www.warzone.com/ChangeUnityWebGL and switch your mode to the one marked "WebAssembly". In this mode, Firefox loads out of cache in 4.0 seconds, which is the fastest loading time I've been able to get. What speeds do you see here, and does everything else in the game work correctly in WebAssembly mode?

I recommend switching to Firefox if you're still on Chrome.

http://gph.to/2EcNiL8

Edited 2/8/2018 18:30:54

For me on Chrome it was around 16s and in Firefox around 7.5s.

FF 58


web assembly

jumps to 80% immediately, then loads a bit.

Edited 2/8/2018 18:31:02

3.5 seconds! Nice, that's even faster than my PC. That's getting to the point of almost being as fast as Flash.

Main Conditions:
OS: Windows 10 Home version 1709.
OS Build: 16299.214
Processor: AMD A8-7410 APU with AMD Radeon R5 Graphics 2.20GHz.
RAM: 8GB.

Stats for FF:
Initial using FF58.0.1 (64-bit) using automatic memory: DL+Inst=36570ms EngineInit=10314ms Loading=46884ms.

From cache using FF58.0.1 (64-bit) using automatic memory: DL+Inst=7139ms EngineInit=8286ms Loading=15425ms.

From cache using FF58.0.2 (64-bit) using automatic memory: DL+Inst=5242ms EngineInit=7712ms Loading=12954ms.
From cache using FF58.0.2 (64-bit) using automatic memory: DL+Inst=5966ms EngineInit=7969ms Loading=13935ms.
From cache using FF58.0.2 (64-bit) using automatic memory: DL+Inst=5898ms EngineInit=8206ms Loading=14104ms.
From cache using FF58.0.2 (64-bit) using automatic memory: DL+Inst=6700ms EngineInit=8126ms Loading=14826ms.
From cache using FF58.0.2 (64-bit) using automatic memory: DL+Inst=6994ms EngineInit=8103ms Loading=15097ms.
From cache using FF58.0.2 (64-bit) using automatic memory: DL+Inst=8321ms EngineInit=7984ms Loading=16305ms.

From cache using FF58.0.2 (64-bit) using WebAssembly: DL+Inst=8226ms EngineInit=11285ms Loading=19511ms.
From cache using FF58.0.2 (64-bit) using WebAssembly: DL+Inst=3921ms EngineInit=12467ms Loading=16388ms.
From cache using FF58.0.2 (64-bit) using WebAssembly: DL+Inst=4583ms EngineInit=11463ms Loading=16046ms.
From cache using FF58.0.2 (64-bit) using WebAssembly: DL+Inst=3797ms EngineInit=11479ms Loading=15276ms.
From cache using FF58.0.2 (64-bit) using WebAssembly: DL+Inst=4099ms EngineInit=11398ms Loading=15497ms.
From cache using FF58.0.2 (64-bit) using WebAssembly: DL+Inst=4432ms EngineInit=11683ms Loading=16115ms.

Stats for Edge:
Microsoft EdgeHTML 16.16299
Microsoft Edge 41.16299.15.0

Initial using Edge using automatic memory: DL+Inst=32192ms EngineInit=15767ms Loading=47959ms.

From cache using Edge using automatic memory: DL+Inst=26388ms EngineInit=15605ms Loading=41993ms.
From cache using Edge using automatic memory: DL+Inst=26644ms EngineInit=15600ms Loading=42244ms.
From cache using Edge using automatic memory: DL+Inst=26328ms EngineInit=15794ms Loading=42122ms.
From cache using Edge using automatic memory: DL+Inst=26551ms EngineInit=15841ms Loading=42392ms.
From cache using Edge using automatic memory: DL+Inst=27208ms EngineInit=16045ms Loading=43253ms.
From cache using Edge using automatic memory: DL+Inst=26245ms EngineInit=16252ms Loading=42497ms.

Initial using Edge using WebAssembly: DL+Inst=8058ms EngineInit=16685ms Loading=24743ms.

From cache using Edge using WebAssembly: DL+Inst=3504ms EngineInit=16447ms Loading=19951ms.
From cache using Edge using WebAssembly: DL+Inst=3821ms EngineInit=16443ms Loading=20264ms.
From cache using Edge using WebAssembly: DL+Inst=3470ms EngineInit=17208ms Loading=20678ms.
From cache using Edge using WebAssembly: DL+Inst=3512ms EngineInit=16396ms Loading=19908ms.
From cache using Edge using WebAssembly: DL+Inst=3777ms EngineInit=16569ms Loading=20346ms.
From cache using Edge using WebAssembly: DL+Inst=3542ms EngineInit=16429ms Loading=19971ms.

Stats for Chrome:
Version 64.0.3282.140 (Official Build) (64-bit)

Initial using Chrome using automatic memory: DL+Inst=26674ms EngineInit=16198ms Loading=42872ms.

From cache using Chrome using automatic memory: DL+Inst=21462ms EngineInit=13154ms Loading=34616ms.
From cache using Chrome using automatic memory: DL+Inst=21814ms EngineInit=13286ms Loading=35100ms.
From cache using Chrome using automatic memory: DL+Inst=21247ms EngineInit=13368ms Loading=34615ms.
From cache using Chrome using automatic memory: DL+Inst=21258ms EngineInit=13198ms Loading=34456ms.
From cache using Chrome using automatic memory: DL+Inst=21653ms EngineInit=13211ms Loading=34864ms.
From cache using Chrome using automatic memory: DL+Inst=21505ms EngineInit=13517ms Loading=35022ms.

From cache using automatic memory caused a generic Chrome error to appear every 2 or 3 refreshes.

Initial using Chrome using WebAssembly: DL+Inst=36582ms EngineInit=4045ms Loading=40627ms.

From cache using Chrome using WebAssembly: DL+Inst=32765ms EngineInit=4084ms Loading=36849ms.
Chrome error.
From cache using Chrome using WebAssembly: DL+Inst=33282ms EngineInit=4236ms Loading=37518ms.
From cache using Chrome using WebAssembly: DL+Inst=32823ms EngineInit=4080ms Loading=36903ms.
Chrome error.
From cache using Chrome using WebAssembly: DL+Inst=32565ms EngineInit=4116ms Loading=36681ms.
From cache using Chrome using WebAssembly: DL+Inst=33082ms EngineInit=4109ms Loading=37191ms.
Chrome error.
From cache using Chrome using WebAssembly: DL+Inst=34002ms EngineInit=4233ms Loading=38235ms.

Order of speed:

1. Firefox - crashed 0 times.
2. Chrome - crashed up to 12 times when gathering this data.
3. Edge - crashed 0 times.

Edited 2/8/2018 20:43:59

Im not moving to Firefox just for warlight are you going to carry on trying to get the load times for web gl shorter?

Why is firefox that much faster than chrome?

Chrome Crashing?
wow, that looks bad news.

Chrome:

DL+Inst=11526ms EngineInit=7107ms Loading=18633ms

Chrome:

Loading=18760ms

103 seconds. Ick. Its about half that for firefox at about ~50 seconds. I dunno if something funky is going on, but it seems my performance is still poor.

EDIT: As an aside, my phone's loading time is about 10 seconds. Which is really nice.

Edited 2/11/2018 21:07:42

Chrome: DL+Inst=8615ms EngineInit=4425ms Loading=13040ms

FF: DL+Inst=2420ms EngineInit=2744ms Loading=5164ms

Multiple errors with new update. I can create my own games. Everytime I try to join another's game I get an error and the game does not load. I am on a chromebook.

Edited 2/12/2018 00:24:00

Have you reported the bug? Bug report link: https://www.warzone.com/ReportBug. Does opening games that you have already joined work correctly no matter who/what created the game? Include screenshots of the error message/s as well.