Size: 435
Comment:
|
Size: 1157
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
= Improving Page Load Performance = |
|
Line 15: | Line 13: |
* See why the Librarian is '''not reusing connections''' * Remove SSL * Cut payloads * Uglification: Remove newlines, spaces, and comments from returned HTML * Remove Mochikit * Are we serving static data from cookieless domains? * Domain sharding for librarian lookups (need numbers to back this up) * CDN or poor man's CDN to help US, Southwest Pacific, and South American users |
|
Line 16: | Line 24: |
* Chameleon (numbers?) * Memcached * Detailed profiling numbers * Time spent in session authentication? * Time spent in the database? * Time spent rendering the response? |
|
Line 17: | Line 34: |
* Load JavaScript using the `deferred` attribute * Lazy-loading JavaScript for key pages * Change inline script node ordering to maximize parallel downloads |
This page is a collection of ideas for improving the Time To Interact of pages on Launchpad.net.
Contents
Which Users Should We Target?
Numbers for Firefox, OEM/IE in China, Europe vs. USA, new vs. repeat visitors
How do these factors affect TTI?
What Can We Improve?
Network Time
See why the Librarian is not reusing connections
- Remove SSL
- Cut payloads
- Uglification: Remove newlines, spaces, and comments from returned HTML
- Remove Mochikit
- Are we serving static data from cookieless domains?
- Domain sharding for librarian lookups (need numbers to back this up)
- CDN or poor man's CDN to help US, Southwest Pacific, and South American users
Generation Time
- Chameleon (numbers?)
- Memcached
- Detailed profiling numbers
- Time spent in session authentication?
- Time spent in the database?
- Time spent rendering the response?
Render Time
Load JavaScript using the deferred attribute
Lazy-loading JavaScript for key pages
- Change inline script node ordering to maximize parallel downloads