Performances

Hi
Just made a test with Google Chrome Dev tools Coverage analysis on some sample pages, and I’ve discovered that

99.4% of 634 KB of td_standard_pack_main.css is unused.
99.7% of 484 KB of js_comoposer.min.css is unused

but even td_legacy_main.css is mostly unused…. 🙁

Is there any chance to optimize this great waste of resources in order to increase site load speed and performance?

https://developers.google.com/web/tools/chrome-devtools/coverage

This answer should be pinned at the top of the sale page on themeforest.
When Google increasingly talks about page load speed as a ranking factor and introduces special tools right in the browser, such as coverage and lighthouse, this kind of answer means: you already gave us money and you are not interesting to us, we wanted to spit on you. Goodbye loser!

• This reply was modified 5 years by usc-shift.

This.

Did anyone get this issue resolved yet?

I wrote a script that accepts the coverage.json at the input, and generates a file with the only used styles, but js does not work (menu, pictures), as we can see, the authors of the theme will not help us and will answer in style: this is a very individual problem that requires bla bla bla give us money, or give link to the google…

You can look on any demo provided by tagdiv, the same situation with pro ‘optimised’ demos. Look at the coverage in chrome devtools, and lighthouse scores

Vlad, I’m not talking about content! The topic is that the connected styles contain a lot of unnecessary code, especially with the standard pack. I attach a screen
and standart demo

Next, go to the lighthouse and see what’s in the main problems (don’t look at the content), and you will understand what is meant
If you follow the SEO news and Google announcements, then of course you understand that these are problems that it is very desirable to solve and this will be an excellent advertisement for your template and a reason to recommend it. In addition, these tools are cov and light and were implemented directly into the browser for a more accurate assessment of problems than in Google Page Speed ​​and before Google rolled out an update about the user experience on the page. Therefore, it makes a lot of sense to be guided by these tools. For you, as developers, this is not such a difficult task and it is much more efficient to solve it in a centralized way than everyone will solve it independently. Thanks in advance.

• This reply was modified 5 years by usc-shift.

Okey but 1 screen is a PRO!)))

Hi, I agreee with usc-shift. TagDiv should be highly concerned by the perf’ problem (a lot of posts mentioned this by the way). I like the theme but it is now penalizing us because of too many js or css (obsolete, not used etc.).

• This reply was modified 5 years by hildi.

all pro demos

Everything listed by you, Vlad, is not related to the topic of discussion! I’m trying to tell you that any pro demo still has a bunch of extra code connected to the header
and loading the first screen is far from ideal, we are not talking about content! I get the feeling that the main task is not admit the problem and fix it. Just write that we don’t care about Google’s December update and we do not recognize the problem as these improvements are not included in our plans. I do not want to give the address of my site because the problem is the same in all demos as well as on my site.

I believe we need to do the job for TD. OK.
So, Vlad :
1. go to dareboost.com
2. enter https://demo.tagdiv.com/newspaper_pro/
3. Look at the results : 9 issues, 13 improvements and quite bad perfs for the first byte and fully loading.
4. You can download the analysis and have a precise look at the results and recommendations.

• This reply was modified 5 years by hildi.

Thank you friend, but Vlad are not writing to us, but to those who do not really understand the technical details and will not check what we are writing here and trying to prove, but simply read that the update is focused. Pure marketing, nothing personal, but for us it can be translated as go anв …. yourself.(( It is calculated that 99% of people will simply decide not to waste their time and not write the same thing 300 times.

• This reply was modified 5 years by usc-shift.

Screen about focusing on optimization… instead of 1000 words

• This reply was modified 5 years by usc-shift.

Thanks for the answer, Calin. At this stage, I tried to get at least recognition of the problem. There are a lot of assurances in the topic of selling, about the best SEO practices, and about speed (I will not sprinkle screenshots, you already know), but at the moment this is far from reality.
At the very least, I wanted to hear that you know about the problem. And that in the next release we will do this and that, for example.
I can provide your developers with the script that cuts out all unnecessary css on the basis of the сoverage, but I need much more time to correctly connect a clean css file, because of javascrit with which I am not very friendly.
I’m just trying to convey that this is very important now and this is a problem. I understand that the support does not cover this, but I do not understand the formal replies that we are doing well with this. Few of those who bought your template make a website for their mother on it. It is necessary to promote the site and display ads on it, which, by the way, will even more affect the site speed indicators, so I (and I think other buyers) would like to understand that updates are taking into account the situation and priorities of the clients, and not the personal goals of the developers (nothing personally).
In the end, it is the clients pay for the entire work of the support team and developers.
You can of course deceive them, or you can listen to them and gets better every day, here is your decision which is more profitable for you.

update

• This reply was modified 5 years by pyro2212.