StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2359534
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-01T22:22:15.760
FavoriteCount
0
LastActivityDate
2010-03-02T00:30:10.290
LastEditDate
2017-05-23T12:07:05.010
LastEditorUserId
-1
OwnerUserId
138475
ParentId
2359515
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
There are two sides you can care about, when optimizing : <ul> <li>The server side : what matters is generating the ouput faster</li> <li>The client side : what matters is getting all that has to be displayed faster.</li> </ul> Note : we, as developpers, often think about optimizing the server-side first... Which in most cases only represents less than 10% percent of the loading-time of the page ! On the server side, you'll generally want to : <ul> <li>profile, to determine what's long</li> <li>optimize your SQL queries, and reduce their number</li> <li>use caching</li> </ul> For more informations, you can take a look to the answer I gave some time ago to this question : <a href="https://stackoverflow.com/questions/1260134/optimizing-kohana-based-websites-for-speed-and-scalability/1283195#1283195">Optimizing Kohana-based Websites for Speed and Scalability</a> On the client side, the biggest gains are generally achieved by : <ul> <li>Reducing the number of HTTP requests -- the easiest way being to reduce the number of JS/CSS/images files, by combining several files into one</li> <li>Compressing CSS/JS/HTML, using for instance Apache's <code>mod_deflate</code>.</li> </ul> About that, there is a lot of great stuff on <a href="http://developer.yahoo.com/performance/" rel="nofollow noreferrer">Yahoo's Exceptional Performance</a> : they've released lots of <a href="http://developer.yahoo.com/performance/rules.html" rel="nofollow noreferrer">good pratices</a> and tools, such as <a href="http://developer.yahoo.com/yslow/" rel="nofollow noreferrer">yslow</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOptimizations to reduce website loading time
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USPascal MARTIN
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.