High Performance Web Sites
and over one million other books are available for Amazon Kindle .
Learn more
| |||||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Amazon.co.uk Trade-In Store for more details. |
Frequently Bought Together
Product details
|
More About the Author
Product Description
Michael J. Ross, Slashdot.org, October 2007
highly recommended to all Web developers seriously interested in improving their site visitors' experiences.
Book Description
14 Steps to Faster-Loading Web Sites
Inside This Book
(Learn More)
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
5 of 5 people found the following review helpful
Format:Paperback
For once, it's nice to have an dev book not full of useless screenshots and blatitudes going beyond 500 pages. This little gem is a delightful stroll through a field I see ignored in most projects too often.
While the authors does not say everthing there is to say about web site optimization, the advice here will be more than enough to out do competitors, to set you a level or two above fellow developers and to show some light on issues that you will probably never find out for yourself unless you do a lot of testing, which you never have time to do, considering the strict deadlines imposed on most projects. Fortunately, Steve Souders has already done this for us.
I love the concept of just doing 14 chapters, each for a given solution, explanining it concisely, giving real world metrics and sticking to the point. Good also that he shows how he did the tests and how he analysis top web sites.
To sum it up, I think this should be a must not only for the front-end engineers, as the book suggests, but also for any developer having to do with the web (asp.net, php, whatever) and architects, project leads, whatever. The book is short and plain, so you have no excuse. It will benefit you no matter what.
While the authors does not say everthing there is to say about web site optimization, the advice here will be more than enough to out do competitors, to set you a level or two above fellow developers and to show some light on issues that you will probably never find out for yourself unless you do a lot of testing, which you never have time to do, considering the strict deadlines imposed on most projects. Fortunately, Steve Souders has already done this for us.
I love the concept of just doing 14 chapters, each for a given solution, explanining it concisely, giving real world metrics and sticking to the point. Good also that he shows how he did the tests and how he analysis top web sites.
To sum it up, I think this should be a must not only for the front-end engineers, as the book suggests, but also for any developer having to do with the web (asp.net, php, whatever) and architects, project leads, whatever. The book is short and plain, so you have no excuse. It will benefit you no matter what.
10 of 11 people found the following review helpful
Format:Paperback
Wow. What a great book.
I took this book, because it is very short, just 168 pages. I asked myself, what this guy can say in just 168 pages about performance? Maybe some introduction to the topic? First two chapters just confirmed my assumptions. There is nothing new, just some general information that I already knew.
How big was my surprise when I finished chapter 3 - first rule (out of 14). Author was able to explain what is the problem with too many http requests and how to make fewer requests. Even I am not a performance guru (just a developer) it was clear enough how should I build my web pages in the future. Even more, he gave me a felling that I should change my current pages.
Next couple chapters are even better, especially description how important is to put css and js imports in the correct place on web page, and how big impact they might have when they are in wrong place. The chapters about Expiry headers and ETags are also awesome. Author describes how cache in web browser works, what are conditional gets and how to make a proxy more efficient.
I finished a book with a feeling that I can easily change my pages to work much faster than they are today. And you know what - I will not spend much time for that one.
I recommend this book for everybody who writes web pages even for personal use. You will be surprised how big amount of knowledge you can get from 168 pages.
I took this book, because it is very short, just 168 pages. I asked myself, what this guy can say in just 168 pages about performance? Maybe some introduction to the topic? First two chapters just confirmed my assumptions. There is nothing new, just some general information that I already knew.
How big was my surprise when I finished chapter 3 - first rule (out of 14). Author was able to explain what is the problem with too many http requests and how to make fewer requests. Even I am not a performance guru (just a developer) it was clear enough how should I build my web pages in the future. Even more, he gave me a felling that I should change my current pages.
Next couple chapters are even better, especially description how important is to put css and js imports in the correct place on web page, and how big impact they might have when they are in wrong place. The chapters about Expiry headers and ETags are also awesome. Author describes how cache in web browser works, what are conditional gets and how to make a proxy more efficient.
I finished a book with a feeling that I can easily change my pages to work much faster than they are today. And you know what - I will not spend much time for that one.
I recommend this book for everybody who writes web pages even for personal use. You will be surprised how big amount of knowledge you can get from 168 pages.
10 of 11 people found the following review helpful
Format:Paperback
The book I reviewed is called High Performance websites ( Essential Knowledge for Frontend Engineers ). It is written by Steve Souders who is Chief Performance at Yahoo. The book explains common causes of pages taking a long time to display then offers 14 performance rules for front end engineers to consider implementing .
I am reviewing this book having been involved in front-end development since 1998 and worked on some of the most visited sites in the UK.
I was sceptical when I heard about this book. I feared it would be a rehash of hoary old advice such as optimise images by using jpegs for photographs, however the high quality of the O'Reilly library persuaded me that Mr Souders might have something more to offer.
When the book arrived on my desk I was pleasantly surprised by its size. It is only 145 pages long. Considerably shorter then my credit card statements and a much more enjoyable read.
The first two chapters are introductory. The first chapter ( 5 pages) explains the importance of front end development. This is useful because it concisely presents the technical case for investing time and resources in optimising the front end layer of a website.
The second chapter explains what happens to a server when a html page loads and where the major delays are. I enjoyed reading it. It bought to together bits of information I'd picked up from a disparate range of sources. It was nice to see them together and in context. The restricted focus on the effects of code on performance (and not databases meant) that I could extract useful information quickly.
The remaining 14 chapters each described one point in a 14 point plan to increase the speed of a website. Obviously this plan is available on-line. There are two advantages to buying the book. The first is that you will obtain supporting information such as graphs and useful code samples. The second is that the in-depth explanations will demonstrate to you why each particular point is a good idea. In a commercial environment this will enable you to better argue your corner when competing with conflicting interests within the organisation.
Rather then replace the content of the book, the online content supports it and makes it easier to produce a useful end product. The YSlow tool is available via the Yahoo developer network. I recommend every developer download this.
In an ideal world the online advertising managers and Emedia studios would read this book and it would influence the creation and display of online media content. In my opinion and according to the research I've done using YSlow, this is the main thing slowing them down.
Summary
In summary this book deserved to be an addition to every professional web developers library.
The advice contained within can be used immediately to make low cost and effective changes to benefit the visitor experience on your site.
However its benefits won't be fully realised until its finding are understood and accepted by the ecommerce marketing audience.
I am reviewing this book having been involved in front-end development since 1998 and worked on some of the most visited sites in the UK.
I was sceptical when I heard about this book. I feared it would be a rehash of hoary old advice such as optimise images by using jpegs for photographs, however the high quality of the O'Reilly library persuaded me that Mr Souders might have something more to offer.
When the book arrived on my desk I was pleasantly surprised by its size. It is only 145 pages long. Considerably shorter then my credit card statements and a much more enjoyable read.
The first two chapters are introductory. The first chapter ( 5 pages) explains the importance of front end development. This is useful because it concisely presents the technical case for investing time and resources in optimising the front end layer of a website.
The second chapter explains what happens to a server when a html page loads and where the major delays are. I enjoyed reading it. It bought to together bits of information I'd picked up from a disparate range of sources. It was nice to see them together and in context. The restricted focus on the effects of code on performance (and not databases meant) that I could extract useful information quickly.
The remaining 14 chapters each described one point in a 14 point plan to increase the speed of a website. Obviously this plan is available on-line. There are two advantages to buying the book. The first is that you will obtain supporting information such as graphs and useful code samples. The second is that the in-depth explanations will demonstrate to you why each particular point is a good idea. In a commercial environment this will enable you to better argue your corner when competing with conflicting interests within the organisation.
Rather then replace the content of the book, the online content supports it and makes it easier to produce a useful end product. The YSlow tool is available via the Yahoo developer network. I recommend every developer download this.
In an ideal world the online advertising managers and Emedia studios would read this book and it would influence the creation and display of online media content. In my opinion and according to the research I've done using YSlow, this is the main thing slowing them down.
Summary
In summary this book deserved to be an addition to every professional web developers library.
The advice contained within can be used immediately to make low cost and effective changes to benefit the visitor experience on your site.
However its benefits won't be fully realised until its finding are understood and accepted by the ecommerce marketing audience.
Would you like to see more reviews about this item?
Were these reviews helpful?
Let us know
Most Recent Customer Reviews
Very good, but why not...?
I own this book and I have to say it is very good and is spot on... but If you use Mozilla Firefox there is an add-on called Firebug (essential for front-end developers) which has... Read more
Published 16 months ago by Will Hancock
The most original tech book for years
The best way to improve the user experience of your web site in by not making the user wait between pages. Read more
Published 16 months ago by Dave C
Essential Reading for Web Systems Managers & Engineers
I work full time in the field of website delivery performance, and spend much of my time examining commercial websites of large and small companies for issues hindering their... Read more
Published on 26 Aug 2009 by Robert Groom
High Performance Web Sites
I remember when I first started using the Internet. Dial ups were extremely slow at the time, so I'd type in a URL, then go make a sandwich. Read more
Published on 9 Oct 2008 by Tami Brady
Listmania!
|
|
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
