Mobile app version of vmapp.org
Login or Join
Candy875

: Strategies for very fast delivery of webpages I run a website Cucumbertown with an initial pay load of nearly 9KB zipped. All my js is delayed loaded with requirejs and modernizer is the

@Candy875

Posted in: #Linux #PageSpeed #Performance

I run a website Cucumbertown with an initial pay load of nearly 9KB zipped.



All my js is delayed loaded with requirejs and modernizer is the only exception.
Now all my webpages are Nginx cached and only 10-15% hits go to the backend proxy. And the cache is invalidated by logged in users as proxy_cache_bypass. So for an anonymous user its nearly always a cache hit.

I have some basic OS tuning with

default via ip dev eth0 initcwnd 15
net.ipv4.tcp_slow_start_after_idle 0


Despite an all cache & large initcwnd my pages still take 2.5 – 3 seconds.

I have a yslow score of



And page speed at



Are there strategies that can help deliver webpages even faster than this? Deliver pages at 1+ second time for 10KB payload?

Notes: My servers run of a fairly good data center from Linode at Fremont.

10.04% popularity Vote Up Vote Down


Login to follow query

More posts by @Candy875

4 Comments

Sorted by latest first Latest Oldest Best

 

@Jennifer507

It looks like most of your page load time is your images. I know other answerers have said this, but I want to add a little evidence behind it because you seemed skeptical. See the Firebug profile below.



So, the first thing I want to point out is all of the gray/brown. That's blocking time where something - usually the other requests, but sometimes in-page javascript - is blocking the other requests from even beginning. If those images were in one request, or you had fewer images, then your site would load faster.

I'm also not seeing expires headers on your images, so even on reloads (which are much faster), there is still blocking going on as my browser has to actually check each image with the server to see if it's updated. An expires header would prevent this.

10% popularity Vote Up Vote Down


 

@Heady270

First of all: you are basically doing a lot of things very good at the moment. This results in good grades in PageSpeed for example. Also keep in mind that the biggest part of the waiting time is spent on the frontend, so it makes sense to optimize this before going deep into server configuration.

These are some ideas:


there are a lot of image requests, for example to your kitchen subdomain. If possible, combine them to one sprited image.
You are using some external Javascripts like Uservoice. They tend to slow down the loading a bit.
if you are not doing this already, try to serve your static JS, CSS and imagefiles from a cookieless CDN subdomain

10% popularity Vote Up Vote Down


 

@Shakeerah822

1.If your web host is farther you might want to look into getting a new host. you can do a ping test, if the response time is large try hosting service nearby.

2.If there is a problem with bandwidth site might be slow.

10% popularity Vote Up Vote Down


 

@Deb1703797

One thing is combine and consolidate your .css and .js files. Even though they are usually cached, it's faster to download 1 5k file than 5 1k files.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme