Why would you put auxiliary resources on your critical path if they’re not required? What if google maps has an outage and suddenly your entire website breaks when the only part requiring google maps is the store locator? What if you’re on an airplane or some other network with limited connectivity?
If you engineer your application correctly with non-critical things outside the critical path you can have the best of both worlds.
Imagine going into the CTO’s office to explain why some vital tool or feature hasn’t been working for 35% of users because of some silly issue with Google Maps. “Why did Google Maps issues break our site?” … “well ackshually our entire app waits for maps.init()…” this is like the worst response imaginable.
Comments
Why would you put auxiliary resources on your critical path if they’re not required? What if google maps has an outage and suddenly your entire website breaks when the only part requiring google maps is the store locator? What if you’re on an airplane or some other network with limited connectivity?
If you engineer your application correctly with non-critical things outside the critical path you can have the best of both worlds.
Imagine going into the CTO’s office to explain why some vital tool or feature hasn’t been working for 35% of users because of some silly issue with Google Maps. “Why did Google Maps issues break our site?” … “well ackshually our entire app waits for maps.init()…” this is like the worst response imaginable.