also, about PageSpeed Insights, it tells me the following:
- High priority. These suggestions represent the largest potential performance wins for the least development effort. You should address these items first: Improve server response time<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=ServerResponseTime> , Leverage browser caching<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=LeverageBrowserCaching> , Defer parsing of JavaScript<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=DeferParsingJavaScript> - Medium priority. These suggestions may represent smaller wins or much more work to implement. You should address these items next: Minify JavaScript<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=MinifyJavaScript> , Serve resources from a consistent URL<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=ServeResourcesFromAConsistentUrl> , Specify a cache validator<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=SpecifyACacheValidator> , Enable compression<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=EnableGzipCompression> - Low priority. These suggestions represent the smallest wins. You should only be concerned with these items after you've handled the higher-priority ones: Inline Small CSS<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=InlineSmallCss> , Inline Small JavaScript<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=InlineSmallJavaScript> , Optimize the order of styles and scripts<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=OptimizeTheOrderOfStylesAndScripts> , Avoid bad requests<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=AvoidBadRequests> , Minify HTML<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=MinifyHTML> , Minify CSS<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=MinifyCss> , Optimize images<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=OptimizeImages> , Serve scaled images<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=ServeScaledImages> , Put CSS in the document head<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=PutCssInTheDocumentHead> , Remove query strings from static resources<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=RemoveQueryStringsFromStaticResources> , Specify a Vary: Accept-Encoding header<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=SpecifyAVaryAcceptEncodingHeader> - Experimental rules. These suggestions are experimental, but do not affect the overall PageSpeed Score. Consider this item as a pointer to an area to explore, but your mileage might vary: Avoid long-running scripts<https://developers.google.com/speed/pagespeed/insights#url=http_3A_2F_2Fmosaico.no-ip.org_2Fmosaico_2Fmortalidadeinfantil_2Fneonatalest.html_3Fbotao_3Dest_26ind_3Dneonatal&mobile=false&rule=AvoidLongRunningScripts> And when I check other sites that where made using web2py, PageSpeed addresses pretty much the same things. While some things are related to how we code, some could be done automatically. For ex, Minify CSS, JS and HTML. Resolved the Leverage browser caching by making small changes on nginx conf file (Virtual Host file, called Web2py). Default options would not make use of browser caching. Cheers, Marco Tulio 2013/4/11 Marco Túlio Cícero de M. Porto <mtcpo...@gmail.com> > on nginx.conf, all compression was commented by default (although it was > enabled on another files - gzip.conf and gzip_static.conf). > > I changed that, but I haven't seen much of a change on load time (despite > the fact that PageSpeed Insight ranked better the page). > > Still checking. > > > 2013/4/11 Marco Túlio Cícero de M. Porto <mtcpo...@gmail.com> > >> sounds nginx is not gzip compressing static files, such as css and js. Is >> that normal behavior ? >> >> >> 2013/4/11 Marco Túlio Cícero de M. Porto <mtcpo...@gmail.com> >> >> I'll double check that then... thanks for your help. >>> >>> >>> 2013/4/11 LightDot <light...@gmail.com> >>> >>>> You're absolutely correct. 6 seconds or even db timeouts an just a few >>>> connections mean that something is wrong. It's either much more connections >>>> than it seems or there is a problem in the code or even OS. >>>> >>>> Ricardo made a valid observation in regards to rogue bots. This problem >>>> is more wide spread than many people think and these suckers can literally >>>> grind your site to a halt... Check your logs for connections coming from: >>>> >>>> 208.115.96.0/19 >>>> 212.113.32.0/21 >>>> 213.186.96.0/19 >>>> 217.69.128.0/21 >>>> >>>> There might be others, these IP ranges are a subset from a research >>>> made a couple of months ago. >>>> >>>> >>>> >>>> On Thursday, April 11, 2013 3:49:22 PM UTC+2, Niphlod wrote: >>>>> >>>>> 6 seconds on a db connection (or query, btw) seems unlikely .... on >>>>> this scale, even if it's true that most of the development platform (read, >>>>> your home pc) are now faster than the various VPS lying around, when you >>>>> coded that particular page you probably noticed a huge loading time in the >>>>> first place..... >>>>> >>>>> if out of the blue the performances are dropping it's usually because >>>>> of deployment issues or "I've been slashdotted" scenarios. >>>>> A concurrency scenario of 5 pages shouldn't lead to a 504 even on the >>>>> poorest platform out there ("raspberrypi scale") >>>>> >>>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "web2py-users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to web2py+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>> >>> >>> >>> -- >>> []'s >>> Marco Tulio >>> >> >> >> >> -- >> []'s >> Marco Tulio >> > > > > -- > []'s > Marco Tulio > -- []'s Marco Tulio -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
