<<harsh criticism - i feel bad for, yet I also feel the standards are too low in general>>
pre-rendering the board on the server would have solved his perceived problem immediately.
then in more detail:
layout thrashing only now a consideration? (advice use a mock dom and see what your operations do in your testing if you decide to handle dom manipulation yourself)
as a developer you only started using the profiler when?
too many http request, can be much optimised (yes i realise cdn, but ttl there can be managed nicely even for a single delivery)
css not remaned and compressed
own js badly minified
using jquery ffs!
>>
anyway, perceived rendering would have solved this by the metrics solved is measured here and simply rendering on the server and giving a 500ms ttl on the cdn would have been faster + not overburden their servers.
I don't know their stack so perhaps the next staement is useless: is this api with the big taskboard open aka can I have a stab at it and try to explain and proof what I am talking about.
pre-rendering the board on the server would have solved his perceived problem immediately.
then in more detail:
layout thrashing only now a consideration? (advice use a mock dom and see what your operations do in your testing if you decide to handle dom manipulation yourself)
as a developer you only started using the profiler when?
too many http request, can be much optimised (yes i realise cdn, but ttl there can be managed nicely even for a single delivery)
css not remaned and compressed
own js badly minified
using jquery ffs!
>> anyway, perceived rendering would have solved this by the metrics solved is measured here and simply rendering on the server and giving a 500ms ttl on the cdn would have been faster + not overburden their servers. I don't know their stack so perhaps the next staement is useless: is this api with the big taskboard open aka can I have a stab at it and try to explain and proof what I am talking about.