V3 is too slow

I know that V3 is too slow for some people. It's a mix of hardware, browser, etc. But that doesn't matter. It's MY fault it's too slow. And we will not shut down V2 until this is fixed! We are currently working on slimming down the JavaScript and using a new library (Vue instead of Angular). So if V3 is slower than V2 for you, then I don't blame you for being mad! I have a really old laptop that I use for testing, and when I have to use V3 on it, it's just too frustrating. So, I hear you on this and I'm sorry! It's our TOP priority. 

Do you need code writer(s)?

Herein lies my major issue with v3,I mostly use my phone, V2 moves lightning fast,v3 super slow

Indeed. We are working feverishly to address this with a new javascript framework. 

Which phone do you have? V3 is super fast on my iPhone, but I know that is not everyone's experience. 

I use an Android

Can you be specific about which model?

Its a ZTE

Erik, also recall, please, I stopped using the V3 App for Android when I found the bug where illegal moves were not caught be the software.  I'm still using Classic Chess.com App for Android and intend to continue on as long as possible with that app.

Thanks! We did find and fix a few bugs with illegal moves (particularly around chess960) in the last few months. Perhaps you could give it another try. That said, I'm impressed with your commitment to Classic!

Works alot better on crappy HTC phone. 2 and 3. Actually on the kindle and windows 10 now. But I still like the v2. I think I noticed color a little better today on v3?

V2 versus V3.  v3's main issue---way too many GET requests for more data.  Sometimes, v3 even transfers less data than v2, but it still has far more GET requests than v2 does.  I gave up waiting for the v3 HOME page to finish loading entirely in v3 in the below comparison test... (I didn't even bother to uncache elements in v3's load, too).

You can see (with the pie charts) in v2, if one eliminated the Ads, the amount of 'images' information would reduce and even faster load times would occur.  The same would be true for v3; would be nice not to have to load the 7+ MB mp4 videos about plastic bags being banned in Bali.

Yes, that was my experience as well, B_e3, when I was a premium member myself. 

Even today, my old nemisis of type-echo came back when I switched to v3 (where one types a key and a delay occurs before one sees the character typed appear on the screen).

Erik, for the love of the site, please refrain from shutting down v2 on Sept. 30th.  v3 just isn't up to it.

I'm pretty sure it's not my hardware or internet connection, i have an 8-core machine running on a fast line. I also used Chrome, which one of the staff members was recommending.

Here's my line speed...

Its funny how we're rehashing all the same tried & tested arguments about how it cannot be v3 to blame for the sluggish performance when all the data, signs, and logic point to exactly that.

But, STAFF beg to differ...

Just for this page, you can see a 4-fold increase in time spent just rendering the basic structure of the page, the layout, also known as the DOM.

v2 DOMContentLoaded time:  378ms ~ 2.62s

v3 DOMContentLoaded time: 8.61s ~ 12.01s

That just give the browser the framework from which to load up each section in a page with content.  Then the content for each section is loaded and processed (depending no how many additional javascript functions exist for each section).

I know, I know, this is all factual data we should somehow not be impressed with as it cannot possibly be v3's fault that its so slow...

Nobody is saying it isn't the code's fault. Well, it is. It's the code, paired with computers which for some reason don't have fast enough CPUs to handle the amount of JavaScript. We are working HARD to reduce that. Again, can you please do me a favor and use the REPORT BUG button when you hit a particularly slow page? Just comment and say "Slow loading page" and we will be able to get a better look at what is happening. It will give us a waterfall of loading and all the timing. Thank you!

I hope V2 gets an extension until V3 is faster and bug free!

That would be a good move. Is there an absolutely necessary 10/1 deadline? 

Being a fairly popular framework, I wouldn't expect a move from Angular to Vue to really reduce the amount of javascript & GETs moved across the wires.  And, suffice to say, that he hasn't said, "hey, look, here's v4 with Vue now, look how fast it is!!", to me means it hasn't panned out that way... so, let's just kill v2 and be done with it.

Possibly. Still discussing options.