Steve Souders - High Performance Web Sites: Essential Knowledge for Front-End Engineers
Here you can read online Steve Souders - High Performance Web Sites: Essential Knowledge for Front-End Engineers full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2007, publisher: OReilly Media, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:High Performance Web Sites: Essential Knowledge for Front-End Engineers
- Author:
- Publisher:OReilly Media
- Genre:
- Year:2007
- Rating:3 / 5
- Favourites:Add to favourites
- Your mark:
High Performance Web Sites: Essential Knowledge for Front-End Engineers: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "High Performance Web Sites: Essential Knowledge for Front-End Engineers" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Steve Souders: author's other books
Who wrote High Performance Web Sites: Essential Knowledge for Front-End Engineers? Find out the surname, the name of the author of the book and a list of all author's works by series.
![Souders - Even faster web sites: [performance best practices for web developers]](/uploads/posts/book/137083/thumbs/souders-even-faster-web-sites-performance-best.jpg)
High Performance Web Sites: Essential Knowledge for Front-End Engineers — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "High Performance Web Sites: Essential Knowledge for Front-End Engineers" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
Copyright 2008 Steve Souders
"If everyone would implement just 20% of Steve's guidelines, the Web would be a dramatically better place. Between this book and Steve's YSlow extension, there's really no excuse for having a sluggish web site anymore."
"Steve Souders has done a fantastic job of distilling a massive, semi-arcane art down to a set of concise, actionable, pragmatic engineering steps that will change the world of web performance."
"As the stress and performance test lead for Zillow.com, I have been talking to all of the developers and operations folks to get them on board with the rules Steve outlined in this book, and they all ask how they can get a hold of this book. I think this should be a mandatory read for all new UE developers and performance engineers here."
" High Performance Web Sites is an essential guide for every web developer. Steve offers straightforward, useful advice for making virtually any site noticeably faster."
You're lucky to be holding this book. More importantly, your web site's users are lucky. Implement even a few of the 14 techniques Steve shares in this groundbreaking book and your site will be faster immediately. Your users will thank you.
Here is why it matters. As a frontend engineer, you hold a tremendous amount of power and responsibility. You're the users' last line of defense. The decisions you make directly shape their experience. I believe our number one job is to take care of them and to give them what they wantquickly. This book is a toolbox to create happy users (and bosses, too). Best of all, once you put these techniques in placein most cases, a one-time tweakyou'll be reaping the rewards far into the future.
This book will change your approach to performance optimization. When Steve began researching performance for our Platform Engineering group at Yahoo!, I believed performance was mainly a backend issue. But he showed that frontend issues account for 80% of total time. I thought frontend performance was about optimizing images and keeping CSS and JavaScript external, but the 176 pages and 14 rules you're holding in your hand right now are proof that it's much more.
I've applied his findings to several sites. Watching already-fast sites render nearly twice as quickly is tremendous. His methodology is sound, his data valid and extensive, and his findings compelling and impactful.
The discipline of frontend engineering is still young, but the book in your hands is an important step in the maturation of our craft. Together we'll raise expectations about the Web by creating better and faster (and therefore more enjoyable) interfaces and experiences.
Cheers to faster surfing!
Nate Koechley
Senior Frontend Engineer Yahoo! User Interface (YUI) Team, Platform Engineering, Yahoo! Inc. San Francisco, August, 2007
In eighth grade, my history class studied the efficiency experts of the Industrial Revolution. I was enthralled by the techniques they used to identify and overcome bottlenecks in manufacturing. The most elegant improvement, in my mind, was the adjustable stepstool that afforded workers of different heights the ability to more easily reach the conveyor belta simple investment that resulted in improved performance for the life of the process.
Three decades later, I enjoy comparing the best practices in this book to that 19th-century stepstool. These best practices enhance an existing process. They require some upfront investment, but the cost is smallespecially in comparison to the gains. And once these improvements are put in place, they continue to boost performance over the life of the development process. I hope you'll find these rules for building high performance web sites to be elegant improvements that benefit you and your users.
After two quick introductory chapters, I jump into the main part of this book: the 14 performance rules. Each rule is described, one per chapter, in priority order. Not every rule applies to every site, and not every site should apply a rule the same way, but each is worth considering. The final chapter of this book shows how to analyze web pages from a performance perspective, including some case studies.
, explains that at least 80 percent of the time it takes to display a web page happens after the HTML document has been downloaded, and describes the importance of the techniques in this book.
, provides a short description of HTTP, highlighting the parts that are relevant to performance.
, describes why extra HTTP requests have the biggest impact on performance, and discusses ways to reduce these HTTP requests including image maps, CSS sprites, inline images using data: URLs, and combining scripts and stylesheets.
, highlights the advantages of using a content delivery network.
, digs into how a simple HTTP header dramatically improves your web pages by using the browser's cache.
, explains how compression works and how to enable it for your web servers, and discusses some of the compatibility issues that exist today.
, reveals how stylesheets affect the rendering of your page.
, shows how scripts affect rendering and downloading in the browser.
, discusses the use of CSS expressions and the importance of quantifying their impact.
, talks about the tradeoffs of inlining your JavaScript and CSS versus putting them in external files.
, highlights the often-overlooked impact of resolving domain names.
, quantifies the benefits of removing whitespace from your JavaScript.
, warns against using redirects, and provides alternatives that you can use instead.
, reveals what happens if a script is included twice in a page.
, describes how ETags work and why the default implementation is bad for anyone with more than one web server.
, emphasizes the importance of keeping these performance rules in mind when using Ajax.
, gives examples of how to identify performance improvements in real-world web sites.
The following typographical conventions are used in this book:
Indicates new terms, URLs, email addresses, filenames, file extensions, pathnames, directories, Unix utilities, and general emphasis.
Constant widthIndicates computer code in a broad sense. This includes commands, options, switches, variables, attributes, keys, functions, types, classes, namespaces, methods, modules, properties, parameters, values, objects, events, event handlers, XML tags, HTML tags, macros, the contents of files, and the output from commands.
HTTP requests and responses are designated graphically as shown in the following example.
GET / HTTP/1.1 is an HTTP request headerHTTP/1.1 200 OK is an HTTP response headerOnline examples can be found on this book's companion web site:
| http://stevesouders.com/hpws |
Examples are included in each chapter in the context in which they are discussed. They are also listed here for easy review.
Font size:
Interval:
Bookmark:
Similar books «High Performance Web Sites: Essential Knowledge for Front-End Engineers»
Look at similar books to High Performance Web Sites: Essential Knowledge for Front-End Engineers. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book High Performance Web Sites: Essential Knowledge for Front-End Engineers and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.