21–30 of 40 posts
1.) I have 306 Bytes of inline JavaScript
2.) Minifying https://grepular.com/ more than it already is could save 794 Bytes, ie less than 1% of the page size.
3.) They want me to defer javascript until after page load. It's the last thing in the body anyway...
None of those are valid complaints. Where's my 100% damnit
Earlier quoted context omitted.
I just noticed that your screenshot isn't even of Page Speed. It is of the Audits tab in Chrome Developers Tools.
It is not mine, but gautaml's one, and it use the independent tool of chrome that perform the same test. But when using the webservice it shows different results.
Are you sure they perform the same tests though? Why would Google build a Page Speed Chrome extension if the exact same algorithms were already built in? I suspect they are working towards the same goal but are approaching it differently.
This suggestion from Google especially looks fun: The following publicly cacheable, compressible resources should have a "Vary: Accept-Encoding" header: * http://www.google.com/buzz/api/button.js However, it's a useful tool. It gives me useful suggestions for improving. Anybody knows a simple tool to minify javascript?
I often use the Closure Compiler at http://closure-compiler.appspot.com/ (online) and http://code.google.com/closure/compiler/ (offline)
So, I've written my own script, which minified seven js-files with total size 84.8 KB to one file with size 26.7 KB. Plus gzip and it will be very small.
Thanks again.
This suggestion from Google especially looks fun: The following publicly cacheable, compressible resources should have a "Vary: Accept-Encoding" header: * http://www.google.com/buzz/api/button.js However, it's a useful tool. It gives me useful suggestions for improving. Anybody knows a simple tool to minify javascript?
The page Hacker News got an overall Page Speed Score of 86 (out of 100).
* Enable gzip compression. * Specify img dimensions. * Leverage browser caching: Add Expires headers; Configure entity tags (ETags). * Minify JavaScript
Earlier quoted context omitted.
It is not mine, but gautaml's one, and it use the independent tool of chrome that perform the same test. But when using the webservice it shows different results.
My bad. I wasn't paying attention to the usernames. Are you sure they perform the same tests though? Why would Google build a Page Speed Chrome extension if the exact same algorithms were already built in? I suspect they are working towards the same goal but are approaching it differently.
I just found it funny that the web gave google.ca 100/100