Closed kgpayne closed 1 year ago
Actually my first screenshot was premature π It took 8.8 minutes for DOMContentLoaded but some files took as long as 13.9 minutes. Top offenders are:
https://hub.meltano.com/assets/js/app.e09f6ba4.js at 1.3mb https://hub.meltano.com/assets/js/page--src--templates--plugins-vue.1ced4414.js at 1.2mb https://hub.meltano.com/assets/js/page--src--pages--extractors-vue~page--src--pages--files-vue~page--src--pages--loaders-vue~page--src~e555b7da.6477f79a.js at 1.2mb
@kgpayne holy crap! That's awful. Is there something we can adjust in Netlify to help with this @aaronsteers ?
I'm unassigning Pat b/c I don't think there's anything he or I can do to help π¬
@kgpayne - I can't infer much from the above screenshots in terms of root cause. I think it's important to distinguish time to 'fully load' the page/site, versus time to get responsiveness.
Gridsome is designed to progressively download first low-res images and then gradually higher and higher resolution images. That said, in the meanwhile while higher resolution images are downloading, there should still be an earlier-available ability to perform basic operations on the site.
We have not put any checks or limits on the logo sizes, but it could be worth reviewing the largest logos and downgrading quality for any that are outside an acceptable size limit. That said, I don't see any very large logos. Lots of them are about half an MB, which is possibly larger than they would need to be if we wanted to tune them for performance.
https://gridsome.org/docs/images/
Regarding network optimizations with Netlify, I can't speak to our options here but others might have ideas/options.
cc @rwfeather, @cjohnhanson
I think it's important to distinguish time to 'fully load' the page/site, versus time to get responsiveness.
Responsiveness was representatively awful π Search wasn't available until the full page load. It seems much better today (with browser cache disabled), so maybe I have triggered a CDN POP cache somewhere local to me. I'd be interested to know if Netlify gives us region page-view data, and region latencies stats too π€
As it seems to have resolved itself (full load in 23.40s), I'd be happy to close this issue as a transient bug.
It seems much better today (with browser cache disabled), so maybe I have triggered a CDN POP cache somewhere local to me
My guess would be something like this. I poked around in Netlify a bit, we can get location page view data if we upgraded our plan but I didn't immediately see any configuration options that could help out here.
+1 to closing as a transient bug.
Note: This issue template is for issues related to the MeltanoHub or plugin definitions. If you're having a problem with a tap or target, please open an issue on that repository so the maintainers can address it.
Describe the bug Loading hub.meltano.com with a clear browser cache takes 10.1 minutes from South Africa.
Expected behavior Ideally CDN coverage would support faster load times than that. Other regions experience millisecond load times.
Screenshots
Desktop (please complete the following information if applicable):