Hi, changelog to what exactly? (sorry)
Hi
no longer updating this thread as have moved onto the torment of http/2 + PHP 7.2 and the fact Google no longer using pagespeed metrics but Chrome user experience via Lighthouse, etc., etc.
HOWEVER — I did want to update on issue from my various suggestions, from when I was using mod_pagespeed a lot, and found loading jquery locally vs from WordPress, or my hook to load jquery off Google’s CDN vs locally …
be aware, a *lot* of versions of JQUERY are insecure with XSS and other issues.
If you did setup your site to load jquery locally or via Google CDN, by unhooking the version from WP; you should run the ‘audit’ query in Google CHROME Console (F12), and do the ‘best practices’ audit, to see if your version of jquery has an exploit, and update the link to newer version.
Stupidly, I missed this on my last internal systems audit, and only just noticed it this week, when doing some ‘tuning’ with Lighthouse since pagespeed insights was saying ‘not available’ on a new project, since they don’ts use that as they once did.
(Put another way, the old ‘pagespeed insights’ no longer useful; and ideally you can use GTMetrix.com for a baseline; but you need to also use the ‘audit’ feature in CHROME for the ‘new way’ in 2018 of tuning/testing issues!)
PEACE OUT PARTY PEOPLE!
1 / 17 / 2018
###
Book?
Hi. .. sorry …
got major sidetrack due to being diagnosed with type II diabetes in 2014; then spent 2 years getting that under control, and 2 years “curing” it — I am now cured and drug free as of Jan 1, but I was moving a bit slowly on all fronts due to taking drugs several times a day, losing 50 lbs, hour of cardio every day, blah blah ….
Finally got around to moving our web server to HTTP/2 on May 12, 2018 (that’s how far behind I was on THAT…) …
Right now, I’ve been working through the different strategies for optimizing website based on:
A) HTTP/2
B) mod_pagespeed “on” – but tuned for bandwidth by default, then turning on select elements; optimizing config to load images via /server/path/ vs http in order to auto-generate webp format images for mobile; necessary for removing comments dynamically including stuff like TagDiv still putting in the theme version in the comments readable by bots which is invitation for hacking for edge issues with XSS and whatnot (BAD!).
C) changing approach to above the fold, due to the way HTTP/2 works; testing whether or not “front loading critical CSS” inline is needed or not; so far, using Lighthouse in Chrome, it seems to matter after all…
D) big trick is optimizing CSS to remove “unused” CSS entirely; using an online tool to scan pages, then basically generate a CSS file that is 40% smaller prior to anything else; Google’s Lighthouse now counsels on this issue, quite nicely — problem with *all* themes out there, sadly.
Since I have my own server, my optimizations are based on running number of daily updated news portals; and trying not to use external CDN and trying not to use static caching beyond opcache for PHP 7.2x and HTTP/2 et al.
Since this subject has been changing so quickly the past couple of years, the whole book thing became a bit pointless as the landscape keeps shifting.
So, again – I kind of moved over to seeing how far we could go with
– https
– php 7.2x with opcache on
– no cdn, or caching plugin in WP
– mod_pagespeed for dynamic optimizations; static /paths/to/images/
– optimized CSS and JS files
– HTTP/2 for nextgen page delivery
– yes/no above the fold critical CSS testing (still in progress!)
– yes/no placement of css/scripts header or footer (still testing!)
– yes/no on combining css and js into single files or not
I request you or the Tagdiv community, Please make a simple step by step video tutorial for us. So, we can optimize our website and increase the speed, as the new update will provide slighter less speed than the older one.
Dear simchris,
how do you improve my site telebari.it ?
(i’m on shared hosting but i can hold about 350 visit in the same moment).
Thanks
