Closed marians closed 10 years ago
Some in-page optimizations have now been done:
Here is a test result after these optimizations: http://www.webpagetest.org/result/140624_D7_A8N/
Comparison:
Did some re-configuration on the server end. In fact requests were proxied by nginx and served by Apache. I changed this to make nginx directly handle the request. Results are here:
http://www.webpagetest.org/result/140624_D7_A8N/
Surprisingly, the Time to First Byte hasn't changed at all. Seems like the proxying to Apache didn't affect times. Since only 3 requests are made to that server, the impact is small.
It turns out that the time to first byte result is mainly influenced by the 3G network setting for the test. Here is a test result with Cable Modem settings: http://www.webpagetest.org/result/140624_XV_BHX/
Here, time to first byte is down to 170 ms.
Closing for now.
Even with good UMTS network bandwidth, loading the webapp feels slow and the app looks broken in the meantime. Both actual and perceived load duration should be improved.
Here is a test that shows details on the current loading behaviour: http://www.webpagetest.org/result/140624_WD_8FF/1/details/
The test has been performed with the "3G" network setting and slow roundtrip time (300ms), location: Falkenstein, Germany.
Without cached elements, it takes 5.2 seconds until the application is loaded.
Here are some pain points: