In Discourse, all js and css files are presented separately. For years I thought it was better to combine, optimize and present these files. Please warn me if I am missing some important things here, but unfortunately the initial boot speed is very slow and would it be beneficial to reduce the number of these files? For example, if there were 1 or 2 css files instead of 30 css files, could it speed up the processes even more? Imagine this, if your site opens in 1-2 seconds when you type it in the address bar and press enter. Hmm that would be great. WebPageTest View this on WebPageTest.org... [video] I agree, it is very functional, very fast after opening and we are in love with it.. Let’s improve it a little more and make it the best of the best :slight_smile:

it seems logical. [image] Javascript Aggregation Feature Discourse sites are all hosted on HTTP/2 the practice of bundling is a best practice on HTTP/1.1 and can in fact be a bad practice in many cases on HTTP/2

Still, there is a waiting period of at least 5-6 seconds. When I test it outside, the waiting time can be really long.

I will test this at the first opportunity.

[image] Jakke Flemming: Those lab-tests are different world Some of that, I think, will be that they do a cold start and have to load all the assets. Most of the time, forum users will have those assets cached in their browsers. I do suspect there are possible improvements to load times, and maybe some of the tips from these lab tests are worth following up on.

[image] kuaza: For example, if there were 1 or 2 css files instead of 30 css files, could it speed up the processes even more? evidence is required here, bundling is something that yields big benefits on HTTP 1.1 sites, not on 2.0 sites. HTTP/2 technology demo I sure want stuff to be faster, but when eval in JavaScript is where the bottleneck is then fiddling with bundling is not the right place.

I think this is not just limited to the HTTP standard. Some sites open in 2-3 seconds. The Discourse 10 second wait screen is a bit of a pain. There is a saying in Turks: Every beauty has a flaw. I hope the discourse will correct this flaw over time.

Again — it comes from server of a forum AND user’s connections AND user’s device I don’t know how the team can fix differences between all districts of the States, Finland or Turkey, or make crowded 4G network giving 3M speed any faster. Or if an user uses entry level chinese mobile lacking enough RAM and mass memory is full of funny cat photos. Sure. The first time could be faster if Discourse would build as ”normal” web sites. But then every page load would be equally or more slow. It is bummer, if Dicourse is slow to you, honestly. But for me in Finland iPhone SE behind home wifi that gets signal from 4G and marketing speed is 200M gives around 2 sec waiting time.

Actually, you know what crossed my mind today. The app feature is always fast. I will tell you how to introduce and install this to every user. In this way, it will both look like an application and give a quick impression. I love Discourse. I have no intention of leaving him for now. I will try every way to make the most of it,

In Discourse, all js and css files are presented separately. Why don't we combine them into one or two files and present them?

Development

Jagster (Jakke Flemming) May 5, 2024, 2:50pm 3

Well, for me reality here is 2 secs. Those lab-tests are different world.

Topic		Replies	Views
Javascript Aggregation Feature	1	550	June 6, 2020
Optimise speed - js and images Product Support	6	1048	December 31, 2019
Optimizing Site For Speed - How To Improve? Development	13	894	April 6, 2024
How to solve super slow loading time for site? Self-hosting	8	3808	August 12, 2023
Combining static JS/CSS assets Product Support	1	474	February 4, 2021

In Discourse, all js and css files are presented separately. Why don't we combine them into one or two files and present them?

Related topics