Fixed PageSpeed Insights & 2.2
- Thread starter Anatoliy
- Start date
but what if a forum will get out of Google index as G will think that it's a site crashed?
That just would not happen, please stop being dramatic.
There's clearly a bug itself with https://web.dev/measure/ and it will either be resolved in due course or you may wish to report it as an issue to them directly here.
Alternatively, you can (successfully) perform a Lighthouse check on any URL using the functionality built into the Chrome developer tools.
There's clearly a bug itself with https://web.dev/measure/ and it will either be resolved in due course or you may wish to report it as an issue to them directly here.
Alternatively, you can (successfully) perform a Lighthouse check on any URL using the functionality built into the Chrome developer tools.
When a man describes a world he describes himself. (c)
I'm taking my question back, if it triggers such your reaction.
For NonDevelopers, HowTo?
That just would not happen you say, huh? What do you say now?
Upgraded on 27th. In 3 days 2184 pages listed as valid mobiles turned into 867.
You mean those noobs from Google can't write correct code? )
How speeding up your mobile site can improve your bottom line
Google's Official Digital Marketing Publication. Discover helpful mobile tools and resources to optimize your site or app, check page speed, and more.
www.thinkwithgoogle.com
Googling your problem comes up with a GitHub repo with an outstanding bug...
Lighthouse returned error: INTERNAL: APP::1: Abnormal renderer termination, status = crashed exit_code = 1 · Issue #10547 · GoogleChrome/lighthouse
Provide the steps to reproduce Run LH on https://www.sodexoengage.com/ This BUG is reported only from https://developers.google.com/speed/pagespeed/insights/ usign LH in local work as normal What i...
github.com
opened this issue on Apr 6Googling your problem comes up with a GitHub repo with an outstanding bug...
Lighthouse returned error: INTERNAL: APP::1: Abnormal renderer termination, status = crashed exit_code = 1 · Issue #10547 · GoogleChrome/lighthouse
Provide the steps to reproduce Run LH on https://www.sodexoengage.com/ This BUG is reported only from https://developers.google.com/speed/pagespeed/insights/ usign LH in local work as normal What i...
Assignees No one assigned
They're fast as bullets )
I would very much believe that is entirely unrelated to Lighthouse. Surely if it was the pages would be shown as an error instead of just disappearing?
But, regardless, it doesn’t change the very simple fact that the INTERNAL error is something that XF has no control over whatsoever as it is internal to Lighthouse.
do you accept "because I could" as an answer? )
Listen, I'm not crying about loss & not blaming anyone. I'm reporting an error.
Just scanned tickets on google help, and here is a reply to someone with the same error: " This issue seems site specific to you, I suspect it's down to the 302 redirect to ?m=1 then javascript redirect to ?m=0 that's throwing lighthouse off, I'd look into why you are sending mobile user agents on that chain of redirects."
So, xF2.2 just became pwa, and I would bet a dollar, that there is some similar reason. I don't know about all that stuff, but I saw something similar, related to webmanifest and start url /?_pwa=1
@Chris D @Mike
So here is additional information for consideration.
I created a page and as usual went to Google Search Console to submit it for Google to index it quick.
First I hit the "Test live url" and got an error (attach 1). Then I hit the "Request indexing" and got an error (attach 2).
So I did "Test live url" for old pages marked as "URL is on Google". Got the same error.
Soo... it's not just PageSpeed Insight thinks that xF 2.2 pages are invalid. Google refuses to list them. And it will not surprise me that already indexed pages will start disappear after several re-crawls with error results.
So here is additional information for consideration.
I created a page and as usual went to Google Search Console to submit it for Google to index it quick.
First I hit the "Test live url" and got an error (attach 1). Then I hit the "Request indexing" and got an error (attach 2).
So I did "Test live url" for old pages marked as "URL is on Google". Got the same error.
Soo... it's not just PageSpeed Insight thinks that xF 2.2 pages are invalid. Google refuses to list them. And it will not surprise me that already indexed pages will start disappear after several re-crawls with error results.
Attachments
We have been looking into this a little but not finding anything conclusive. Regardless of what we find and whatever workarounds we could implement this is still fundamentally a Google issue. Everything we have written is to spec - many of which Google themselves have written 
yeah, and global warming also
Similar threads
