Adlago

I posted a reply here more than 5 minutes ago. Still this opinion of mine is missing in stream... Probably a bug.

Yes, sorry - I took the trouble to check. Although many supposedly responsible sites state what I wrote in the first sentence. Ok - you are using a 3rd party library - this library introduces delays that create poor quality in your product. Don't you have any programmers to eliminate this issue in browsers? I think there are very few improvements you can make to take your product much further. With a few simple (for me of course) revisions of some templates - without touching the CSS, I achieve, surprisingly for me, good results in tests from various well-known analysis sites. I.e. instead of putting effort into the CSS, just remove all the javascript annotations... I can share everything I do absolutely free - for me this loading speed game was and is just a hobby...

The unload() method was deprecated in jQuery version 1.8 and removed in version 3.0. Do you plan to change the jQuery version of the root_library?

This won't help you, but in the interest of your thread - after updating to 4.7.5, I created a new account on my site. There is no issue - at least for me everything is OK.

Managing a web business does not mean solving technological problems - there are other people working on relevant cases and solving them, and that has nothing to do with this topic here. You have not provided any solution to the site's fast loading issue. Maybe your "IT bees" etc. are more useful for this topic than you. I'm sorry.

How many times have you, with respect to you, tried to solve a similar case of a site sinking in speed? I would appreciate it if you could point to your example of a solution to this, not the comments of gurus who profit from their articles...

I don't use ads on my site, so I looked for other solutions for my site as well. For a site with ads, the CSS should be improved.

Since the CSS is unavailable for quick experiments, in the last month I have been looking for other solutions to speed up site loading. Especially on mobile… I split the Include JS template into two parts, used a preload for some resources, etc. subtle changes... and crash-free with good server responses. This is my maximum for now... There are more thoughts in my head - and strange for you - without me touching the CSS... ha ha ha...

You are only speaking with conjecture - could you support this statement of yours with an example please. Thanks. This is not true at all and is not worth commenting on…

Do not expect an improvement in site loading speed after changing the DB. There is such a change, but it is negligibly small to see it as a real indicator. Site loading speed is dependent on mutual loading of CSS and JS, and one more thing. But that's another topic.

There is a possibility - that you have changed one of your database tables to an unacceptable format. Try - change a few DBs, then remove cache site and so on until all databases are normal. It's a gratifying circumstance that you managed it yourself. And you will manage again but in slow steps. Only a few databases in change in one step.

Try clearing browser cache before ACP login, or try ACP login with another browser

Does your custom css look like this?

Excellent work:-)

I think that no one should be in a hurry - I will personally wait for a correct update.

Also my test site doesn't see an update - and in test site I'm on version 4.7.4 beta 1

I waited a bit on this download attempt then was redirected to this page - also not working...

This comparison is incorrect, that's why I wrote it. Below is an objective comparison from a test now from my friend's site @sadams101 1. IPS default theme - without ad blocks included - there are no reported web vitals indicators in the test because it does not pass the test successfully. Site load test 2. Test with a used theme - after numerous changes in the CSS loading method, without changing the content CSS rules, All advertising blocks included - more than 6-7 objects in a page. And of course - web vitals test Do you think it makes sense? Each site has its own specificity in displaying its content - (how much value content has - that's another topic). That's why every site uses css rules of different importance. In order to speed up the loading of all resources, it is essential to speed up the loading of the used rules, and postpone the unused css rules... This is impossible only using custom.css. This is also impossible using designer mode. And that is the point of this topic of mine. I understand the desire to improve the entire process of IPS development - but this process is slow and requires a lot of analysis and a lot of work. Therefore, it is better to IPS restore access to all available css files in ACP. When the IPS offers a successfully working project for the idea CSS to CDN - let this project go through online tests - who wishes to participate - and then go in for release... I think so.

Where do you find an estimate that the content is worth about 80%? Content rating also depends on users - slow loading speed content is ignored by many users... PS. Also Please note, above images from @Mattare from different site...

And you think please. This topic does not address changes to CSS rules. What this thread is about is being able to other loading this CSS... Think for yourself - how much time does a server use to process php requests, and the CSS minimizer that IPS has implemented (this is a particularly good hit) for all possible external CSS? Even the fact that all external CSS are downloaded in parallel does not change the delay in page rendering. Yes, when a site has no special claims for this - it is irrelevant. But when a site relies on advertising revenue - every millisecond of delay is a lost cent. The point of my topic is that the CSS that is used by a site (and this in volumetric weight is about 15% of the total volume of available external CSS) should be loaded as a priority. This is possible only if you move used CSS rules for each site (for each site it is individual - according to the needs of the community) in one common external CSS, which you understand yourself will load quickly... All other CSS rules in files, in which they are created can be moved before the close body tag... They are not important for site rendering - and can load with low priority... Site speed, which is strangely underestimated - costs money, and any site using ads knows this very well...

If the question was only about me and my site, this thread here would not have been created by me. I optimize various sites - I cannot leave fixed rules that a site owner will not be able to change in ACP ie. I store everything as functionality and performance that you have created. I rely on my acceleration principles, which do not change the content of your product - I only change the way of initial loading - which actually speeds up the site loading and improves Web Vitals parameters - which is a requirement of Google and all sites using ads suffer financially for poor performance . The metod of using a browser inspector to extract code is only applicable when using critical css like inline css (an idea I gave up on a year ago) Your disabling access to basic css terminated my project when with just css changes loading I reached a score level of 88-94 for mobile. I.e. I failed to finish the second stage of my project - binding with acceleration loading JS. And now if you do a PSI test on my site, you will still get the same results 88-94 for a mobile test, because I applied my idea on the JS, which also made the site load faster. If I had managed to finish my project - mobile loading speed would have had a minimum reading of over 90... what was the basic idea... Yes probably your css over CDN idea will work better at some future time, but I'm personally skeptical... And what would prevent you from having an option in the ACP - with CDN CSS or CSS Own installation?

@Matt Isn't it better to try the JS from the CDN - anyway, too few users try to change the JS. And JS is a resource that makes the biggest TBT time for mobile. If the JS is loaded from your server through CDN - all sites will have much better performance indicators. And CSS - leave it as in previous versions - there are enthusiasts like me who are looking for other solutions - maybe you like some solution...

As I wrote, I use it and I know it. But you tell me, how in the inspector to find and copy this code, for example? .ipsLayout_container { {{if theme.enable_fluid_width}} {{if theme.fluid_width_size}} max-width: {theme="fluid_width_size"}%; {{else}} max-width: 100%; {{endif}} {{else}} max-width: var(--container--width); {{endif}} padding: 0 15px; margin: 0 auto; position: relative; } Because in my project I don't want just the result of one page or one device, but your exact code that works as you created it...

This using an inspector is not a good idea - because an inspector sees ready code, and only for a page that is tested with an inspector - for my project it is important to use responsive code that uses php in original file css, etc. etc I, like you, have been using inspector for a long time and a first version of my project started like this - but I quickly noticed unpleasant changes in various pages and gave up copy/pasting from inspector...

No, I can't do what I used to do again, you'll ask why? - First, I don't change rules in main css - But for more than 6 months I have been working on a project where custom css is the only css that is loaded in the head, main css is loaded before closing the body tag. - in the custom css content, all the framework and responsive file names are found, and some others. But with numbering, for example 1fr_global.css or 2res_ responsive.css, etc. - In these new files, I move used rules when analyzing site pages, i.e. in the main css all the rules are contained (as they have been moved they are stopped from execution only) - or here in the main css all the rules are loaded that are unused effectively when loading the site pages. This new layout greatly speeds up site loading. The custom.css file also exists in custom directory and there are my customizations - and as you know, the rules there are the latest and are executed by the browser as they are there. Since IPS introducing restrictions for visibility on css main, I abandoned a project where mobile view loads on PSI test data between 88 and 94 points depending on server busyness. And believe me - during the time I was working on this project - several updates were completed - without any site issues...