3 ms·
I loaded the front page of Mangadex and it made 114 web requests including 10 first-party XHR requests, 30(!!!!) Javascript resource requests and somehow 4 font
by mdoms 5y ago
I loaded the front page of Mangadex and it made 114 web requests including 10 first-party XHR requests, 30(!!!!) Javascript resource requests and somehow 4 font requests, without me interacting with the page. Clicking one of the titles on the front page resulted in nearly 40 additional requests.
Perhaps if you are limited by requests per second you could consider how many requests a single user is making per interaction, and if this is a reasonable number.
The website is impressively fast though, I'll give you that.
- m45t3r 5y agoThey're probably more limited by bandwidth than requests per second, but anyway you look the number of requests are still impressive considered the budget. BTW, the site is not just fast: they serve images on high quality (same as the original [1], that can be multiple MBs per page [2]) at an pretty impressive speed too. [1]: before someone asks why they don't optimize the images, this is by design since they want to serve high quality images. There is an optional toggle to reduce the image size, but this is disabled by default. [2]: for those not familiar, the average number of pages on a manga is something like ~20, and this can be read in ~5 minutes depending on the density of the text. So you can easily consume 50MB+ per chapter.
- deleted 5y ago[deleted]
- watermelon0 5y agoFrontend framework they use (NUXT) uses code splitting [1], which means that: - first request is fast, because you only need to download chunks required for a single page/controller (and you prefetch others in the background) - changing some parts of codebase requires to re-download only affected chunks, instead of the whole bundle [1] https://www.telerik.com/blogs/what-you-should-know-code-splitting-nuxtjs https://www.telerik.com/blogs/what-you-should-know-code-spli...