User Profile

Hello,We're using MapKit JS for the web in a very simple way. The problem is that PageSpeed Insights or Lighthouse raises question reguarding poor performance caused by MapKit JS.For example, on this pagespeed insights (but you get more detailed results if you run the test straight from your browser using chrome devtools audit section):Script evaluation takes about 2,5 to 3 seconds on a simulated slow 4G, 4x CPU slowdown (see this screenshot).Assets are not served using HTTP2, and since a lot of assets transfer through (on my example, I count 120 HTTP requests to cdn*.apple-mapkit.com). I think multiplexing could do a lot of good there if it were using HTTP2 protocol;I ran locally the chrome audit on my MacbookPro 15" 2019, with 2,3Ghz Intel Core I9, 32Go ram. We're using the latest version of MapKit JS (5.x.x).No fancy stuff was done, it's a "default" map (~650x220px) , zoom 13, and place a single marker on it to show a particular address)Other "minors":- it complains about the image format that are not using next-gen formats.Is there a thing I'm missing ? Is it something you're working on or/and aware ?Thank you;