The deployment of this gadget caused the size of JS loaded on first view for loggedin users on mobile enwiki to jump by more than 500%:
Where the extra JS requests are:
This might only affect articles that have a location set. The two articles we happen to track for JS size in WPT (Facebook and Sweden) happen to both have one.
The feature this is for is behind an icon that needs to be clicked on:
It might make more sense to lazy-load that JS when the feature is actually clicked on, instead of downloading it defensively like it seems to do at the moment. Thankfully after the pageload, but still, seems like wasted bandwidth when most visits won't see a click on that feature.