Archived topic
Google Changes
28 replies · Started by Michael on May 29, 2020
Hi guys,
I noticed as of yesterday my scores in Google Web Dev and Page Speed Insights took an inexplicable nosedive for performance. After asking some questions online it turns out Google are the culprits having made a ton of changes. Nice one Google.
Anyway, here is a page on it for anyone who might be interested:
And also:
https://twitter.com/JohnMu/status/1265990146492706816
I'm looking through the suggested optimizations (or opportunities as they call it) and there are a number of generatepress css files and a few js files that are flagged, and jquery 1.12.4 gets pulled up a few times also (does that ship with WordPress? I'm not sure as I haven't installed). Any ideas on how to streamline them further?
Thanks a lot for your input.
Michael.
Same here. My score is horrific. Tom et all... any news on how these changes will affect GP? TIA
I think Google would rather we just load a blank page ;) 100% no render blocking....
Now there's an idea. My site is minimalist anyway ;-)
It would have to be an informative blank page though which provides value to users.... Tricky
Yeah Google is like a bored child on a car journey ... constantly reminding you that you're not quite there yet and when you do arrive they just want to turn back round again.
I am not sure there is much for GP to do in regards to these changes.
The benchmark site we use for speedtests is still performing:
https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fspeedtest.generatepress.com
Now to be fair the test site doesn't have a lot going on especially stuff that impacts FID, LCP and CLS that are now vital metrics.
But what i see on most recent tests is the FCP ( First Contentful Paint ) seems to be taking a bigger hammering then it used to and having much greater impact on the overall Pagespeed score.
This means that we all have to be mindful of how many extra scripts and styles we are loading.
I am sure Tom will be doing his utmost to improve what we can. Be interesting to see whether this hurries WP into action with implementing a core lazy loader or finally getting round to facing off the legacy jQuery issues.
Down with monopolies! Google and Amazon CEOs can volunteer for the Mars mission I think ;)
Thank you for your input David.
Thanks, David.
You're welcome - seen your other Topic Robin we'll take a look asap.
Hi David,
Is jquery migrate needed by GP?
I'm looking into removing it, so wanted to check if there would be any knock-ons before I do that.....
https://wordpress.org/plugins/remove-jquery-migrate/
Michael.
I am pretty sure GP doesn't require it on the Front End - but you may find other plugins do. Also been a few reports of customizer functionality breaking when its removed....
Hi David,
In the 15 millionth web dev test I've run, under accessibility it says:
ARIAThese are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
ARIA IDs are not unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
Failing Elements
The failing elements appear to be GP generated, so I wanted to ask your advice on how to implement their suggestion so I can scrape another point or two here or there.
I'm busy testing the jquery side of things at the moment, and will revert back with hopefully some useful info for others :)
Michael.
Hi David,
What would your recommendation be as the safest way to remove or disable jquery migration? I've tried a couple of plugins but they don't appear to work. I've seen code listed on a few sites, but looks years old so don't necessarily trust it. I'd really appreciate your thoughts!
Michael.
The failing elements appear to be GP generated
Which elements are those?
As for jQuery migrate - that's a core WP thing. This should help: https://wordpress.stackexchange.com/a/291711/90661
Hi Tom,
Thanks for getting back to me. Sorry for some reason they didn't paste into the message. Here are the elements I was referring to:
Failing Elements