What's happening is that your data is 983840 bytes long. That's going to take at least 9.4 seconds to fetch over a 1Mb broadband connection.
To go significantly faster, you'll need to reduce the amount of data that gets fetched. One solution would be to do server-side marker management, so that the client only receives data for the markers that are to be displayed in the current viewport. A simpler approach would be to omit the htmllarge from the main data, and only fetch the track details when the user has clicked on a marker. I guess that would reduce the size of your main data, and therefore its Internet transfer time by a factor of about 20. There may well be other delays, but dealing with the size of that file should bring your page loading time down into the range where tools like Google Chrome Resource Inspector and PageTest will produce meaningful results. http://pagetest.patrickmeenan.com:8080/ -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
