-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature requests: Search, Themes, Guides for image optimizations #1221
Comments
In general PageSpeed can only provide heuristics. Not everything is recommends is always correct, nor applicable. We are working with that team to improve their recommendations and we are addressing some of the points. But not because some tool says so, but because we have data that says it would be faster. |
Edited the title to reflect the content of the request. |
Thank you very much so far, @cramforce. I'll check it out as soon as my calendar allows me to. PageSpeed: Yes, I figured out that its recommendations are not always useful and/or correct indeed. However, I'm happy to read that Google does know that also and hope they don't take its results blindly to grade website speed quality... |
We can track form support at #1286, which is mostly a stub for right now but can be expanded in the future. |
Also, following up within Google on the Material template and Page Speed, so closing this out. |
I would love to use AMP HTML for our mobile website. However, it would need two things to be available in order to switch:
And finally: Not really a reason, but an AMP HTML page should score 100% on the Google PageSpeed Insights test which it currently doesn't. So either change/correct the test or improve performance ;)
The text was updated successfully, but these errors were encountered: