Thank you @Adam !
I followed the list at PageSpeed Insights, and implemented almost every recommendation they have.
I tested a few hundreds of times to get it right, making small steps and testing each.
Their list is very acurate and links to articles about every step, then I researched more online and did my best to implemnent every recommendation.
Most was done by editing the code of the theme HTML/CSS, some script loading optimization (the order is important), and using embed code widgets to replace some widgets and get nore control, such as the video header and image widgets. By the way, please check the video header widget, it doubles the size of mildly compressed uploaded videos, so it seems to encode them in an "expensive" way for speed.
I reduced CLS to zero (very hard, performance tab in dev-tools helped identifying issues), inlined above the fold code, re-ordered loading of scripts and images etc, and every other PageSpeed Insights recommendation that I could control. The focus is on above the fold content, but not only.
Last steps were targeted in time to first byte vs time to interactive vs Largest contentful paint, that was hard and required testing of different loading order about a 100 times, until I found the optimal script and content loading order 
I found that by giving up a little time to first byte, I was able to improve time to interactive and largest contentful paint, and keep all "green" (the last 2 were "orange" in the mobile test, now all green.
Yesterday I made another progress with the above entioned parameters, and got 97 on mobile (100 on desktop).
I apppreciate Weebly's open access to the HTML / CSS / and some JS, it helps greatly and can't be done in some other platforms. ๐
Weebly has a great mix of easy editing (easiest as far as I know) and ability to dig deep in the code in a convenient way.
I would be happy if Weebly could test what code (mainly JS) is really necesary and load only it, for example I worked on a client's website, and found that the blog CSS file is loaded on every page, not only on blog pages. I also would like to be able to switch off the native analytics, since I use Google's (like most websites), so no need to double load analytics (it is quite taxing for speed).
I'm very happy to get to this point, I can rest soon - 3 more points to go
Thanks @Adam for your support and Weebly for making it possible ๐
Thank you @Adam !
I followed the list at PageSpeed Insights, and implemented almost every recommendation they have.
I tested a few hundreds of times to get it right, making small steps and testing each.
Their list is very acurate and links to articles about every step, then I researched more online and did my best to implemnent every recommendation.
Most was done by editing the code of the theme HTML/CSS, some script loading optimization (the order is important), and using embed code widgets to replace some widgets and get nore control, such as the video header and image widgets. By the way, please check the video header widget, it doubles the size of mildly compressed uploaded videos, so it seems to encode them in an "expensive" way for speed.
I reduced CLS to zero (very hard, performance tab in dev-tools helped identifying issues), inlined above the fold code, re-ordered loading of scripts and images etc, and every other PageSpeed Insights recommendation that I could control. The focus is on above the fold content, but not only.
Last steps were targeted in time to first byte vs time to interactive vs Largest contentful paint, that was hard and required testing of different loading order about a 100 times, until I found the optimal script and content loading order
I found that by giving up a little time to first byte, I was able to improve time to interactive and largest contentful paint, and keep all "green" (the last 2 were "orange" in the mobile test, now all green.
Yesterday I made another progress with the above entioned parameters, and got 97 on mobile (100 on desktop).
I apppreciate Weebly's open access to the HTML / CSS / and some JS, it helps greatly and can't be done in some other platforms. ๐
Weebly has a great mix of easy editing (easiest as far as I know) and ability to dig deep in the code in a convenient way.
I would be happy if Weebly could test what code (mainly JS) is really necesary and load only it, for example I worked on a client's website, and found that the blog CSS file is loaded on every page, not only on blog pages. I also would like to be able to switch off the native analytics, since I use Google's (like most websites), so no need to double load analytics (it is quite taxing for speed).
I'm very happy to get to this point, I can rest soon - 3 more points to go
Thanks @Adam for your support and Weebly for making it possible ๐
