It struck me as basically somebody saying "if you care about it for your app, I'd be happy to help you care about it for your website".
I feel like you're assuming bad faith, and the person confused as to why the comment was being downvoted was applying the principle of charity instead.
http://www.webpagetest.org/result/151027_FV_1ATV/1/details/
I didn't get the idea that grk was pitching consulting services but just to be clear that I have no interest in that market, here are the most obvious things:
1. Enable gzip transfer compression for static assets like Bootstrap
2. Compress the large images more aggressively and perhaps turn on progressive JPEG, although that latter step might be CPU-costly on mobile devices
3. Set cache headers on all static resources so regular users and anyone behind a caching proxy will avoid the full server RTT
4. If you use www.hike.in, optimize the redirect to go directly to get.hike.in instead of having a full RTT to get the intermediate hike.in redirect.
Beyond that, I'd look into a front-end diet – do you need so many images, can you lazy-load images or that 350KB of youtube, etc?
No SSL, No HTTP2/PageSpeed. Html not concated.
No additional server in america. It sucks to connect from Germany. It's twice as fast to connect to Servers in America so ALWAYS have a US Region.
I hope their messenger is better.
"Happy Dussehra! Join hike this weekend & get a festive bonus of Rs. 51 free talktime on joining. It's 5 times faster with 10 new features. http://hike.in"
I'm thinking of reporting this to relevant authorities.
Also, after the hike fiasco, I kept getting callbacks from many of my contacts that I had given them a missed calls.
Very shady. I don't even know how they do it. I thought it was illegal to pretend as another mobile number.
>Free Group Calls With Upto 100 People With The Tap Of A Single Button!
"Upto" should be two words
It helped a us lot to improve our product for India market.