breautek commented on issue #1363:
URL: https://github.com/apache/cordova-ios/issues/1363#issuecomment-1680513416

   Based on the image provided the issue is a connection issue.
   
   Your application code and assets should be embedded with the app. 
Downloading assets should be reserved for dynamic content.
   
   The image shows that you're downloading an image over the network on a 
`ss1.baidu.com` server and that request took almost 15 seconds to download a 
5kb image.
   
   The timeline line on the right shows it took an insignificant small time to 
resolve the domain which is represented by the purple block. This is the DNS 
query. it seems like 90% of the time spent was waiting on the TCP connection, 
represented by the yellow block. This means that `ss1.baidu.com` was slow to 
respond. The red block represents the SSL handshake, which appears normal, and 
the green block represents the time spent waiting on the content response. 
There is another block representing the download time but it's not really 
visible in the graphic, which means it probably took no time at all to actually 
downoad the 5kb image.
   
   What this highlights is opening the connection to `ss1.baidu.com` is slow.
   
   Like all network tasks, networks by their nature is not guaranteed and it is 
expected that poor or lack of a network connection will occur from time to 
time. It's the app developers responsibility to handle these situations.
   
   If this is affecting your app startup, embedding your core app assets would 
be the ideal solution, which eliminates the network variables. If you cannot 
embed these assets for whatever reason, then you're next best solution is to 
defer loading the assets (using the `defer` attributes where applicable or move 
to use `XMLHttpRequest` to load in the request instead of loading it in via 
`img`, or using some network load means that doesn't block the DOM from being 
"loaded".
   
   Closing as not a bug.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to