When vectors are drawn on the display, browser performance suffers tremendously. This is very clear with the METAR display and can be plainly traced to memory intensiveness within the display rendering.
1. Investigate the root cause of vector performance issues.
2. Perform necessary updates.
3. Test existing METAR module code for improvements.
4. (If necessary) Revise METAR module code for better performance (display only within map bounds, etc.)
Other vector overlays seem to perform fine (Fronts, etc.) due to their restriction to the CONUS. Before the GFS was transitioned to a tile-based overlay for heights (Polylines), the application still performed very well globally.