Are you over 18 and want to see adult content?
More Annotations
Kids’ photo journal for family | Lifecake
Are you over 18 and want to see adult content?
Best Electric Smokers (August 2019) | Buyer's Guide and Reviews
Are you over 18 and want to see adult content?
Favourite Annotations
A complete backup of https://sfsuitescsa.com
Are you over 18 and want to see adult content?
A complete backup of https://minnesotafringe.org
Are you over 18 and want to see adult content?
A complete backup of https://blugolds.com
Are you over 18 and want to see adult content?
A complete backup of https://meglio.it
Are you over 18 and want to see adult content?
A complete backup of https://411freedirectory.com
Are you over 18 and want to see adult content?
A complete backup of https://nofxofficialwebsite.com
Are you over 18 and want to see adult content?
A complete backup of https://auone.jp
Are you over 18 and want to see adult content?
A complete backup of https://dimulik.ru
Are you over 18 and want to see adult content?
A complete backup of https://goshango.com
Are you over 18 and want to see adult content?
A complete backup of https://autoserviceoosterhout.nl
Are you over 18 and want to see adult content?
A complete backup of https://dcnepal.com
Are you over 18 and want to see adult content?
A complete backup of https://nsttv.com
Are you over 18 and want to see adult content?
Text
STEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
BROWSER BUSY INDICATORS MEASURING LOCALSTORAGE PERFORMANCE The only variable that changed between these two tests was the amount of data in localStorage: 10K vs 5M. Thus, we can conclude that the increase from 13 ms to 156 ms is due to Firefox precaching taking longer when there is more localStorage data. Table 2. 10K localStorage. User Agent. SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing DOMAIN SHARDING REVISITEDHTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
PREFERRED CACHING
Preferred Caching. September 12, 2012 8:06 am | 9 Comments. In Clearing Browser Data I mentioned Internet Explorer’s “Preserve Favorites website data” option. It first appeared in Internet Explorer 8’s Delete Browsing History dialog: This is a great idea. I advocated this to all browser makers at Velocity 2009 under the name 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets.STEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
BROWSER BUSY INDICATORS MEASURING LOCALSTORAGE PERFORMANCE The only variable that changed between these two tests was the amount of data in localStorage: 10K vs 5M. Thus, we can conclude that the increase from 13 ms to 156 ms is due to Firefox precaching taking longer when there is more localStorage data. Table 2. 10K localStorage. User Agent. SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing DOMAIN SHARDING REVISITEDHTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
PREFERRED CACHING
Preferred Caching. September 12, 2012 8:06 am | 9 Comments. In Clearing Browser Data I mentioned Internet Explorer’s “Preserve Favorites website data” option. It first appeared in Internet Explorer 8’s Delete Browsing History dialog: This is a great idea. I advocated this to all browser makers at Velocity 2009 under the name 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets. HIGH PERFORMANCE WEB SITES Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Critical Metric: Critical Resources. February 10, 2016 7:37 pm | 6 Comments A big change in the World of Performance for 2015 is the shift to metrics that do a better job of measuring the user experience.The performance industry grew up focusing on page load time, but teams with more advanced websites have started replacing DOMAIN SHARDING REVISITED The HTTP Archive counts the number of requests made on each domain. The domain with the most requests is the “max domain” and the number of requests on that domain is the “maxDomainReqs”. The average maxDomainReqs value has risen from 47 to 50 over the past year. That’s not a huge increase, but the fact that the averagenumber of
MOBILE CACHE FILE SIZES Mobile cache file sizes. July 12, 2010 10:07 am | 8 Comments Mobile is big, but knowledge about how to make a mobile web site fast is lacking. The state of mobile web performance is in a similar place as desktop was six years ago when I started my performance deep dive. THE PERFORMANCE GOLDEN RULE The average frontend time is 76%, slightly lower than the 80-90% advertised in the Performance Golden Rule. But remember that these sites have highly optimized frontends, and two of them are search pages (not results) that have very few resources. For a more typical view I looked at 10 sites ranked around 10,000. DOMINTERACTIVE: IS IT? REALLY? Fonts: The results for the domInteractive Font – too optimistic have a domInteractive time of about half a second in all browsers, but the time at which the critical content is visible varies. In Safari, the critical content isn’t visible for 8+ seconds while waiting for the font file to load. In Chrome and Firefox, the critical content is USING IFRAMES SPARINGLY Using Iframes Sparingly. June 3, 2009 10:42 pm | 18 Comments. This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, PositioningInline
PREFERRED CACHING
Preferred Caching. September 12, 2012 8:06 am | 9 Comments. In Clearing Browser Data I mentioned Internet Explorer’s “Preserve Favorites website data” option. It first appeared in Internet Explorer 8’s Delete Browsing History dialog: This is a great idea. I advocated this to all browser makers at Velocity 2009 under the name APPENDCHILD VS INSERTBEFORE Then insertBefore is used to insert the new dynamic SCRIPT element into the document. Normally, this is when the script would start downloading (asynchronously), but in this case the src hasn’t been set. Instead, the script’s URL has been put inside a string of JavaScript code that does a document.write of a SCRIPT HTML tag. DON’T DOCWRITE SCRIPTS Don’t docwrite scripts. April 10, 2012 5:29 pm | 32 Comments In yesterday’s blog post, Making the HTTP Archive faster, one of the biggest speedups came from not using a script loader. It turns out that script loader was using document.write to load scripts dynamically. I wrote about the document.write technique in Loading Script Without Blocking back in April 2009, as well as in EvenSTEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
BROWSER BUSY INDICATORS MOVING BEYOND WINDOW.ONLOAD() For these websites, window.onload reports a value that is faster than the user’s perception. A good example of this kind of dynamic web app is Gmail. Looking at the WebPagetest results for Gmail we see that window.onload is 3.3 seconds, but at that point only the progress bar is visible. The above-the-fold content snaps into place at 4.8seconds.
SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, FlushingCACHE IS KING
Cache is King. October 11, 2012 8:11 pm | 10 Comments I previously wrote that the keys to a fast web app are using Ajax, optimizing JavaScript, and better caching.. Using Ajax reduces network traffic to just a few JSON requests.; Optimizing JavaScript (downloading scripts asynchronously, grouping DOM modifications, yielding to the UI thread, etc.) allows requests to happen in parallel andHTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
APPENDCHILD VS INSERTBEFORE Then insertBefore is used to insert the new dynamic SCRIPT element into the document. Normally, this is when the script would start downloading (asynchronously), but in this case the src hasn’t been set. Instead, the script’s URL has been put inside a string of JavaScript code that does a document.write of a SCRIPT HTML tag. 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets.STEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
BROWSER BUSY INDICATORS MOVING BEYOND WINDOW.ONLOAD() For these websites, window.onload reports a value that is faster than the user’s perception. A good example of this kind of dynamic web app is Gmail. Looking at the WebPagetest results for Gmail we see that window.onload is 3.3 seconds, but at that point only the progress bar is visible. The above-the-fold content snaps into place at 4.8seconds.
SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, FlushingCACHE IS KING
Cache is King. October 11, 2012 8:11 pm | 10 Comments I previously wrote that the keys to a fast web app are using Ajax, optimizing JavaScript, and better caching.. Using Ajax reduces network traffic to just a few JSON requests.; Optimizing JavaScript (downloading scripts asynchronously, grouping DOM modifications, yielding to the UI thread, etc.) allows requests to happen in parallel andHTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
APPENDCHILD VS INSERTBEFORE Then insertBefore is used to insert the new dynamic SCRIPT element into the document. Normally, this is when the script would start downloading (asynchronously), but in this case the src hasn’t been set. Instead, the script’s URL has been put inside a string of JavaScript code that does a document.write of a SCRIPT HTML tag. 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets. HIGH PERFORMANCE WEB SITES Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
MEASURING LOCALSTORAGE PERFORMANCE The only variable that changed between these two tests was the amount of data in localStorage: 10K vs 5M. Thus, we can conclude that the increase from 13 ms to 156 ms is due to Firefox precaching taking longer when there is more localStorage data. Table 2. 10K localStorage. User Agent.HTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
CACHE IS KING
Cache is King. October 11, 2012 8:11 pm | 10 Comments I previously wrote that the keys to a fast web app are using Ajax, optimizing JavaScript, and better caching.. Using Ajax reduces network traffic to just a few JSON requests.; Optimizing JavaScript (downloading scripts asynchronously, grouping DOM modifications, yielding to the UI thread, etc.) allows requests to happen in parallel and PERFORMANCE AND CUSTOM ELEMENTS Performance and Custom Elements. November 26, 2013 3:43 pm | 6 Comments This past week I dug into the performance of custom elements and found some surprises.. In my previous blog post, Async Ads with HTML Imports, I complained that HTML imports block the page from rendering when a SCRIPT tag is found and lamented the fact that the spec doesn’t provide a mechanism to make THE PERFORMANCE GOLDEN RULE The average frontend time is 76%, slightly lower than the 80-90% advertised in the Performance Golden Rule. But remember that these sites have highly optimized frontends, and two of them are search pages (not results) that have very few resources. For a more typical view I looked at 10 sites ranked around 10,000. HTTP ARCHIVE: ADDING FLUSH HTTP Archive: adding flush. January 31, 2013 12:09 am | 8 Comments In my previous post, HTTP Archive: new schema & dumps, I described my work to make the database faster, easier to download, consume less disk space, and contain more stats.Once these updates were finished I was excited to start going through the code and make pages faster using the new schema changes.PREFERRED CACHING
Preferred Caching. September 12, 2012 8:06 am | 9 Comments. In Clearing Browser Data I mentioned Internet Explorer’s “Preserve Favorites website data” option. It first appeared in Internet Explorer 8’s Delete Browsing History dialog: This is a great idea. I advocated this to all browser makers at Velocity 2009 under the name DON’T DOCWRITE SCRIPTS Don’t docwrite scripts. April 10, 2012 5:29 pm | 32 Comments In yesterday’s blog post, Making the HTTP Archive faster, one of the biggest speedups came from not using a script loader. It turns out that script loader was using document.write to load scripts dynamically. I wrote about the document.write technique in Loading Script Without Blocking back in April 2009, as well as in Even BROWSER SCRIPT LOADING ROUNDUP Thankfully, newer browsers now load scripts in parallel! This is a big win for today’s web apps that often contain 100K+ of JavaScript split across multiple files. Loading the same test page in IE8, Firefox 3.6, Chrome 4, and Safari 4 produces an HTTP waterfall chart like this: Things look a lot better, but not as good as they shouldbe.
STEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
BROWSER BUSY INDICATORS MOVING BEYOND WINDOW.ONLOAD() For these websites, window.onload reports a value that is faster than the user’s perception. A good example of this kind of dynamic web app is Gmail. Looking at the WebPagetest results for Gmail we see that window.onload is 3.3 seconds, but at that point only the progress bar is visible. The above-the-fold content snaps into place at 4.8seconds.
SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, FlushingCACHE IS KING
Cache is King. October 11, 2012 8:11 pm | 10 Comments I previously wrote that the keys to a fast web app are using Ajax, optimizing JavaScript, and better caching.. Using Ajax reduces network traffic to just a few JSON requests.; Optimizing JavaScript (downloading scripts asynchronously, grouping DOM modifications, yielding to the UI thread, etc.) allows requests to happen in parallel andHTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
APPENDCHILD VS INSERTBEFORE Then insertBefore is used to insert the new dynamic SCRIPT element into the document. Normally, this is when the script would start downloading (asynchronously), but in this case the src hasn’t been set. Instead, the script’s URL has been put inside a string of JavaScript code that does a document.write of a SCRIPT HTML tag. 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets.STEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
BROWSER BUSY INDICATORS MOVING BEYOND WINDOW.ONLOAD() For these websites, window.onload reports a value that is faster than the user’s perception. A good example of this kind of dynamic web app is Gmail. Looking at the WebPagetest results for Gmail we see that window.onload is 3.3 seconds, but at that point only the progress bar is visible. The above-the-fold content snaps into place at 4.8seconds.
SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, FlushingCACHE IS KING
Cache is King. October 11, 2012 8:11 pm | 10 Comments I previously wrote that the keys to a fast web app are using Ajax, optimizing JavaScript, and better caching.. Using Ajax reduces network traffic to just a few JSON requests.; Optimizing JavaScript (downloading scripts asynchronously, grouping DOM modifications, yielding to the UI thread, etc.) allows requests to happen in parallel andHTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
APPENDCHILD VS INSERTBEFORE Then insertBefore is used to insert the new dynamic SCRIPT element into the document. Normally, this is when the script would start downloading (asynchronously), but in this case the src hasn’t been set. Instead, the script’s URL has been put inside a string of JavaScript code that does a document.write of a SCRIPT HTML tag. 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
BROWSER BUSY INDICATORS Each result is essentially a bitmask indicating whether the busy indicator was triggered. For example, the first result for “Chrome 27 (Mac OS)” and the “click link” test is T S C P R N.This means the Tab icon, Status bar, and Reload icon indicators were triggered; but the Cursor, Progress bar, and Network indicators were not triggered.A few notes about the indicators:DO U WEBVIEW?
do u webview? October 9, 2014 3:52 am | 2 Comments A “webview” is a browser bundled inside of a mobile application producing what is called a hybrid app.Using a webview allows mobile apps to be built using Web technologies (HTML, JavaScript, CSS, etc.) but still package it as a native app and put it in the app store.CACHE IS KING
Cache is King. October 11, 2012 8:11 pm | 10 Comments I previously wrote that the keys to a fast web app are using Ajax, optimizing JavaScript, and better caching.. Using Ajax reduces network traffic to just a few JSON requests.; Optimizing JavaScript (downloading scripts asynchronously, grouping DOM modifications, yielding to the UI thread, etc.) allows requests to happen in parallel andHTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
HTTP ARCHIVE: ADDING FLUSH HTTP Archive: adding flush. January 31, 2013 12:09 am | 8 Comments In my previous post, HTTP Archive: new schema & dumps, I described my work to make the database faster, easier to download, consume less disk space, and contain more stats.Once these updates were finished I was excited to start going through the code and make pages faster using the new schema changes. AUTOHEAD – MY FIRST BROWSERSCOPE USER TEST AutoHead – my first Browserscope user test. May 12, 2010 3:17 pm | 18 Comments In the comments from my last blog post (appendChild vs insertBefore) someone asked which browsers do and don’t automatically create a HEAD element.This is important when you’re deciding how to dynamically add scripts to your web page.PREFERRED CACHING
Preferred Caching. September 12, 2012 8:06 am | 9 Comments. In Clearing Browser Data I mentioned Internet Explorer’s “Preserve Favorites website data” option. It first appeared in Internet Explorer 8’s Delete Browsing History dialog: This is a great idea. I advocated this to all browser makers at Velocity 2009 under the name DON’T DOCWRITE SCRIPTS Don’t docwrite scripts. April 10, 2012 5:29 pm | 32 Comments In yesterday’s blog post, Making the HTTP Archive faster, one of the biggest speedups came from not using a script loader. It turns out that script loader was using document.write to load scripts dynamically. I wrote about the document.write technique in Loading Script Without Blocking back in April 2009, as well as in Even ROUNDUP ON PARALLEL CONNECTIONS Roundup on Parallel Connections. March 20, 2008 1:40 am | 36 Comments A lot of blogging and follow-up discussion ensued with the announcement that IE8STEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
DO U WEBVIEW?
do u webview? October 9, 2014 3:52 am | 2 Comments A “webview” is a browser bundled inside of a mobile application producing what is called a hybrid app.Using a webview allows mobile apps to be built using Web technologies (HTML, JavaScript, CSS, etc.) but still package it as a native app and put it in the app store. RULE 6 - PUT SCRIPTS AT THE BOTTOM - STEVE SOUDERS Move scripts to the bottom of the page. This avoids two problems: the blank white screen and delayed downloads.. Example 1 - Scripts in the Middle; Example 2 - Scripts Top vs. Bottom; Example 3 -HTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing WINDOW.POSTMESSAGE TEST This page provides a demonstration of window.postMessage.It's in the HTML 5 spec.It's implemented in Internet Explorer 8 and Firefox 3, but the implementation in IE8 deviates from the spec. . Test 1 should thrown an exception. The HTML 5 spec says, "If the value of the targetOrigin argument is neither a single U+002A ASTERISK character ("*") nor a valid URI or IRI, then throw a SYNTAX_ERR YUI COMBO HANDLER: PRESERVING ORDER This page uses the YUI Combo Handler to load the YUI Rich Text Editor.The Combo Handler is a way that developers can choose a subset of YUI modules but still get them loaded in 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets.STEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
DO U WEBVIEW?
do u webview? October 9, 2014 3:52 am | 2 Comments A “webview” is a browser bundled inside of a mobile application producing what is called a hybrid app.Using a webview allows mobile apps to be built using Web technologies (HTML, JavaScript, CSS, etc.) but still package it as a native app and put it in the app store. RULE 6 - PUT SCRIPTS AT THE BOTTOM - STEVE SOUDERS Move scripts to the bottom of the page. This avoids two problems: the blank white screen and delayed downloads.. Example 1 - Scripts in the Middle; Example 2 - Scripts Top vs. Bottom; Example 3 -HTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing WINDOW.POSTMESSAGE TEST This page provides a demonstration of window.postMessage.It's in the HTML 5 spec.It's implemented in Internet Explorer 8 and Firefox 3, but the implementation in IE8 deviates from the spec. . Test 1 should thrown an exception. The HTML 5 spec says, "If the value of the targetOrigin argument is neither a single U+002A ASTERISK character ("*") nor a valid URI or IRI, then throw a SYNTAX_ERR YUI COMBO HANDLER: PRESERVING ORDER This page uses the YUI Combo Handler to load the YUI Rich Text Editor.The Combo Handler is a way that developers can choose a subset of YUI modules but still get them loaded in 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets.STEVE SOUDERS
CONTACT. @souders. This email form is the best way to contact me. It's guaranteed to reach me. Name: BROWSER BUSY INDICATORS Each result is essentially a bitmask indicating whether the busy indicator was triggered. For example, the first result for “Chrome 27 (Mac OS)” and the “click link” test is T S C P R N.This means the Tab icon, Status bar, and Reload icon indicators were triggered; but the Cursor, Progress bar, and Network indicators were not triggered.A few notes about the indicators: MOBILE STATE MACHINE TEST PAGE About this test: Mobile carriers demote network connections to conserve battery power. But this has the potential to slow down web pages because it can take ~2 seconds toDO U WEBVIEW?
do u webview? October 9, 2014 3:52 am | 2 Comments A “webview” is a browser bundled inside of a mobile application producing what is called a hybrid app.Using a webview allows mobile apps to be built using Web technologies (HTML, JavaScript, CSS, etc.) but still package it as a native app and put it in the app store. SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing MOVING BEYOND WINDOW.ONLOAD() But the opposite is also true. Heavily dynamic websites load much of the visible page after window.onload.For these websites, window.onload reports a value that is faster than the user’s perception.A good example of this kind of dynamic web app is Gmail.Looking at the WebPagetest results for Gmail we see that window.onload is 3.3 seconds, but at that point only the progress bar is visible.CACHE IS KING
Cache is King. October 11, 2012 8:11 pm | 10 Comments I previously wrote that the keys to a fast web app are using Ajax, optimizing JavaScript, and better caching.. Using Ajax reduces network traffic to just a few JSON requests.; Optimizing JavaScript (downloading scripts asynchronously, grouping DOM modifications, yielding to the UI thread, etc.) allows requests to happen in parallel and MAKING A MOBILE CONNECTION Making a mobile connection. September 21, 2011 11:03 pm | 11 Comments I just returned from Breaking Development Conference, an amazing gathering of many of the brightest minds in mobile web development.On the flight home I watched the video and slides from Rajiv Vijayakumar’s talk on Understanding Mobile Web Browser Performanceat Velocity 2011.
HTTP ARCHIVE: ADDING FLUSH HTTP Archive: adding flush. January 31, 2013 12:09 am | 8 Comments In my previous post, HTTP Archive: new schema & dumps, I described my work to make the database faster, easier to download, consume less disk space, and contain more stats.Once these updates were finished I was excited to start going through the code and make pages faster using the new schema changes.PREFERRED CACHING
Preferred Caching. September 12, 2012 8:06 am | 9 Comments. In Clearing Browser Data I mentioned Internet Explorer’s “Preserve Favorites website data” option. It first appeared in Internet Explorer 8’s Delete Browsing History dialog: This is a great idea. I advocated this to all browser makers at Velocity 2009 under the nameSTEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
DO U WEBVIEW?
do u webview? October 9, 2014 3:52 am | 2 Comments A “webview” is a browser bundled inside of a mobile application producing what is called a hybrid app.Using a webview allows mobile apps to be built using Web technologies (HTML, JavaScript, CSS, etc.) but still package it as a native app and put it in the app store. RULE 6 - PUT SCRIPTS AT THE BOTTOM - STEVE SOUDERS Move scripts to the bottom of the page. This avoids two problems: the blank white screen and delayed downloads.. Example 1 - Scripts in the Middle; Example 2 - Scripts Top vs. Bottom; Example 3 -HTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing WINDOW.POSTMESSAGE TEST This page provides a demonstration of window.postMessage.It's in the HTML 5 spec.It's implemented in Internet Explorer 8 and Firefox 3, but the implementation in IE8 deviates from the spec. . Test 1 should thrown an exception. The HTML 5 spec says, "If the value of the targetOrigin argument is neither a single U+002A ASTERISK character ("*") nor a valid URI or IRI, then throw a SYNTAX_ERR YUI COMBO HANDLER: PRESERVING ORDER This page uses the YUI Combo Handler to load the YUI Rich Text Editor.The Combo Handler is a way that developers can choose a subset of YUI modules but still get them loaded in 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets.STEVE SOUDERS
WPO – Web Performance Optimization. WebPagetest.org – top tool. Zen and the Art of Web Performance. HTTP Archive Specification: Firebug and HttpWatch. Simplifying CSS Selectors. Using Iframes Sparingly. Flushing the Document Early. Sharding Dominant Domains. Positioning Inline Scripts. EVANGELIZING PERFORMANCE Evangelizing Performance. While working at Yahoo! I was able to share these best practices with web developers worldwide. This web site of performance examples is the companion site for my book, High Performance Web Sites, from O'Reilly Media . I created the performance analysis tool, YSlow, an extension to the popular Firebug webdevelopment tool.
HIGH PERFORMANCE WEB SITES Developer Network Performance Blog . There you will find a brief summary of the rule along with comments. Rule 1 - Make Fewer HTTP Requests. Rule 2 - Use a Content Delivery Network. Rule 3 - Add an Expires Header. Rule 4 - Gzip Components. Rule 5 - Put Stylesheets at the Top. Rule 6 - Put Scripts at the Bottom. Rule 7 - Avoid CSSExpressions.
DO U WEBVIEW?
do u webview? October 9, 2014 3:52 am | 2 Comments A “webview” is a browser bundled inside of a mobile application producing what is called a hybrid app.Using a webview allows mobile apps to be built using Web technologies (HTML, JavaScript, CSS, etc.) but still package it as a native app and put it in the app store. RULE 6 - PUT SCRIPTS AT THE BOTTOM - STEVE SOUDERS Move scripts to the bottom of the page. This avoids two problems: the blank white screen and delayed downloads.. Example 1 - Scripts in the Middle; Example 2 - Scripts Top vs. Bottom; Example 3 -HTML5 VIDEO PRELOAD
Observation #3: Browsers preload too much by default. Developers are most likely not going to specify any value for PRELOAD. As shown in Table 1, this situation results in IE 9 buffering 2 seconds of video, Opera 12 buffers 10 seconds, Chrome 26 buffers 25 seconds, and Safari6
SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing WINDOW.POSTMESSAGE TEST This page provides a demonstration of window.postMessage.It's in the HTML 5 spec.It's implemented in Internet Explorer 8 and Firefox 3, but the implementation in IE8 deviates from the spec. . Test 1 should thrown an exception. The HTML 5 spec says, "If the value of the targetOrigin argument is neither a single U+002A ASTERISK character ("*") nor a valid URI or IRI, then throw a SYNTAX_ERR YUI COMBO HANDLER: PRESERVING ORDER This page uses the YUI Combo Handler to load the YUI Rich Text Editor.The Combo Handler is a way that developers can choose a subset of YUI modules but still get them loaded in 5A MISSING SCHEMA DOUBLE DOWNLOAD Developers should avoid using protocol relative URLs for stylesheets if they want their pages to be as fast as possible in Internet Explorer 7 & 8. The five posts in this series are: 5a Missing schema double download. 5b document.write scripts block in Firefox. 5c media=print stylesheets.STEVE SOUDERS
CONTACT. @souders. This email form is the best way to contact me. It's guaranteed to reach me. Name: BROWSER BUSY INDICATORS Each result is essentially a bitmask indicating whether the busy indicator was triggered. For example, the first result for “Chrome 27 (Mac OS)” and the “click link” test is T S C P R N.This means the Tab icon, Status bar, and Reload icon indicators were triggered; but the Cursor, Progress bar, and Network indicators were not triggered.A few notes about the indicators: MOBILE STATE MACHINE TEST PAGE About this test: Mobile carriers demote network connections to conserve battery power. But this has the potential to slow down web pages because it can take ~2 seconds toDO U WEBVIEW?
do u webview? October 9, 2014 3:52 am | 2 Comments A “webview” is a browser bundled inside of a mobile application producing what is called a hybrid app.Using a webview allows mobile apps to be built using Web technologies (HTML, JavaScript, CSS, etc.) but still package it as a native app and put it in the app store. SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing MOVING BEYOND WINDOW.ONLOAD() But the opposite is also true. Heavily dynamic websites load much of the visible page after window.onload.For these websites, window.onload reports a value that is faster than the user’s perception.A good example of this kind of dynamic web app is Gmail.Looking at the WebPagetest results for Gmail we see that window.onload is 3.3 seconds, but at that point only the progress bar is visible.CACHE IS KING
Cache is King. October 11, 2012 8:11 pm | 10 Comments I previously wrote that the keys to a fast web app are using Ajax, optimizing JavaScript, and better caching.. Using Ajax reduces network traffic to just a few JSON requests.; Optimizing JavaScript (downloading scripts asynchronously, grouping DOM modifications, yielding to the UI thread, etc.) allows requests to happen in parallel and MAKING A MOBILE CONNECTION Making a mobile connection. September 21, 2011 11:03 pm | 11 Comments I just returned from Breaking Development Conference, an amazing gathering of many of the brightest minds in mobile web development.On the flight home I watched the video and slides from Rajiv Vijayakumar’s talk on Understanding Mobile Web Browser Performanceat Velocity 2011.
HTTP ARCHIVE: ADDING FLUSH HTTP Archive: adding flush. January 31, 2013 12:09 am | 8 Comments In my previous post, HTTP Archive: new schema & dumps, I described my work to make the database faster, easier to download, consume less disk space, and contain more stats.Once these updates were finished I was excited to start going through the code and make pages faster using the new schema changes.PREFERRED CACHING
Preferred Caching. September 12, 2012 8:06 am | 9 Comments. In Clearing Browser Data I mentioned Internet Explorer’s “Preserve Favorites website data” option. It first appeared in Internet Explorer 8’s Delete Browsing History dialog: This is a great idea. I advocated this to all browser makers at Velocity 2009 under the nameSTEVE SOUDERS
Your script just killed my site. High Performance Mobile. Even FasterWeb Sites
EVANGELIZING PERFORMANCE 14 Rules for Faster-Loading Web Sites. from the book High Performance Web Sites by Steve Souders How these rules came about In 2004 I became Chief Performance Yahoo!. My job description was clear: quantify and improve the performance of all Yahoo! products worldwide. HIGH PERFORMANCE WEB SITES 14 Rules for Faster-Loading Web Sites These rules are the key to speeding up your web pages. They've been tested on some of the most popular sites on the Internet and have successfully reduced the response times of those pages by 25-50%.DO U WEBVIEW?
do u webview? October 9, 2014 3:52 am | 2 Comments A “webview” is a browser bundled inside of a mobile application producing what is called a hybrid app.Using a webview allows mobile apps to be built using Web technologies (HTML, JavaScript, CSS, etc.) but still package it as a native app and put it in the app store.HTML5 VIDEO PRELOAD
Observation #1: Mobile devices don’t preload anything. The VIDEO spec calls the preload values “hints”, so it makes sense that mobile browsers would choose not to preload anything in order to save on data costs. Instead, the video doesn’t start downloading until the user initiates playback. When I saw this I decided to add a test for the AUTOPLAY attribute. SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing RULE 6 - PUT SCRIPTS AT THE BOTTOM - STEVE SOUDERS Move scripts to the bottom of the page. This avoids two problems: the blank white screen and delayed downloads.. Example 1 - Scripts in the Middle; Example 2 - Scripts Top vs. Bottom; Example 3 - WINDOW.POSTMESSAGE TEST This page provides a demonstration of window.postMessage.It's in the HTML 5 spec.It's implemented in Internet Explorer 8 and Firefox 3, but the implementation in IE8 deviates from the spec. . Test 1 should thrown an exception. The HTML 5 spec says, "If the value of the targetOrigin argument is neither a single U+002A ASTERISK character ("*") nor a valid URI or IRI, then throw a SYNTAX_ERR YUI COMBO HANDLER: PRESERVING ORDER This page uses the YUI Combo Handler to load the YUI Rich Text Editor.The Combo Handler is a way that developers can choose a subset of YUI modules but still get them loaded in 5A MISSING SCHEMA DOUBLE DOWNLOAD Browsers substitute the protocol of the page itself for the resource’s missing protocol. Problem solved! In fact, today’s HttpWatch Blog posted about this: Using Protocol Relative URLs to Switch between HTTP and HTTPS.. However, if you try this in Internet Explorer 7 and 8 you’ll see that stylesheets specified with a protocol relative URL are downloaded twice.STEVE SOUDERS
Your script just killed my site. High Performance Mobile. Even FasterWeb Sites
EVANGELIZING PERFORMANCE 14 Rules for Faster-Loading Web Sites. from the book High Performance Web Sites by Steve Souders How these rules came about In 2004 I became Chief Performance Yahoo!. My job description was clear: quantify and improve the performance of all Yahoo! products worldwide. HIGH PERFORMANCE WEB SITES 14 Rules for Faster-Loading Web Sites These rules are the key to speeding up your web pages. They've been tested on some of the most popular sites on the Internet and have successfully reduced the response times of those pages by 25-50%.DO U WEBVIEW?
do u webview? October 9, 2014 3:52 am | 2 Comments A “webview” is a browser bundled inside of a mobile application producing what is called a hybrid app.Using a webview allows mobile apps to be built using Web technologies (HTML, JavaScript, CSS, etc.) but still package it as a native app and put it in the app store.HTML5 VIDEO PRELOAD
Observation #1: Mobile devices don’t preload anything. The VIDEO spec calls the preload values “hints”, so it makes sense that mobile browsers would choose not to preload anything in order to save on data costs. Instead, the video doesn’t start downloading until the user initiates playback. When I saw this I decided to add a test for the AUTOPLAY attribute. SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing RULE 6 - PUT SCRIPTS AT THE BOTTOM - STEVE SOUDERS Move scripts to the bottom of the page. This avoids two problems: the blank white screen and delayed downloads.. Example 1 - Scripts in the Middle; Example 2 - Scripts Top vs. Bottom; Example 3 - WINDOW.POSTMESSAGE TEST This page provides a demonstration of window.postMessage.It's in the HTML 5 spec.It's implemented in Internet Explorer 8 and Firefox 3, but the implementation in IE8 deviates from the spec. . Test 1 should thrown an exception. The HTML 5 spec says, "If the value of the targetOrigin argument is neither a single U+002A ASTERISK character ("*") nor a valid URI or IRI, then throw a SYNTAX_ERR YUI COMBO HANDLER: PRESERVING ORDER This page uses the YUI Combo Handler to load the YUI Rich Text Editor.The Combo Handler is a way that developers can choose a subset of YUI modules but still get them loaded in 5A MISSING SCHEMA DOUBLE DOWNLOAD Browsers substitute the protocol of the page itself for the resource’s missing protocol. Problem solved! In fact, today’s HttpWatch Blog posted about this: Using Protocol Relative URLs to Switch between HTTP and HTTPS.. However, if you try this in Internet Explorer 7 and 8 you’ll see that stylesheets specified with a protocol relative URL are downloaded twice. EVANGELIZING PERFORMANCE 14 Rules for Faster-Loading Web Sites. from the book High Performance Web Sites by Steve Souders How these rules came about In 2004 I became Chief Performance Yahoo!. My job description was clear: quantify and improve the performance of all Yahoo! products worldwide.STEVE SOUDERS
*Anti-Spam: Type "ocean" in the field below to get past my (lame) spamblocker.
BROWSER BUSY INDICATORS Each result is essentially a bitmask indicating whether the busy indicator was triggered. For example, the first result for “Chrome 27 (Mac OS)” and the “click link” test is T S C P R N.This means the Tab icon, Status bar, and Reload icon indicators were triggered; but the Cursor, Progress bar, and Network indicators were not triggered.A few notes about the indicators: MOBILE STATE MACHINE TEST PAGE About this test: Mobile carriers demote network connections to conserve battery power. But this has the potential to slow down web pages because it can take ~2 seconds to MOVING BEYOND WINDOW.ONLOAD() But the opposite is also true. Heavily dynamic websites load much of the visible page after window.onload.For these websites, window.onload reports a value that is faster than the user’s perception.A good example of this kind of dynamic web app is Gmail.Looking at the WebPagetest results for Gmail we see that window.onload is 3.3 seconds, but at that point only the progress bar is visible. SIMPLIFYING CSS SELECTORS Simplifying CSS Selectors. June 18, 2009 12:55 pm | 25 Comments This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, FlushingCACHE IS KING
Cache is King. October 11, 2012 8:11 pm | 10 Comments I previously wrote that the keys to a fast web app are using Ajax, optimizing JavaScript, and better caching.. Using Ajax reduces network traffic to just a few JSON requests.; Optimizing JavaScript (downloading scripts asynchronously, grouping DOM modifications, yielding to the UI thread, etc.) allows requests to happen in parallel and MAKING A MOBILE CONNECTION Making a mobile connection. September 21, 2011 11:03 pm | 11 Comments I just returned from Breaking Development Conference, an amazing gathering of many of the brightest minds in mobile web development.On the flight home I watched the video and slides from Rajiv Vijayakumar’s talk on Understanding Mobile Web Browser Performanceat Velocity 2011.
HTTP ARCHIVE: ADDING FLUSH HTTP Archive: adding flush. January 31, 2013 12:09 am | 8 Comments In my previous post, HTTP Archive: new schema & dumps, I described my work to make the database faster, easier to download, consume less disk space, and contain more stats.Once these updates were finished I was excited to start going through the code and make pages faster using the new schema changes.PREFERRED CACHING
Preferred Caching. September 12, 2012 8:06 am | 9 Comments In Clearing Browser Data I mentioned Internet Explorer’s “Preserve Favorites website data” option. It first appeared in Internet Explorer 8’s Delete Browsing History dialog: This is a great idea.STEVESOUDERS.COM
* about
* contact
*
I'm now at SpeedCurve! HIGH PERFORMANCE WEB SITES BLOG HTTP ARCHIVE NEW LEADERSHIP April 12, 2017 8:01 am | Comments Off on HTTP Archive New Leadership I announced the HTTP Archive six years ago. Six years ago! It has exceeded my expectations and its value continues to grow. In order to expand the vision, I’ve asked Ilya Grigorik , Rick Viscomi, and Pat Meenan
to take over leadership of theproject.
The HTTP Archive is part of the Internet Archive. The code
and data
are open source. The project is funded by our generous sponsors: Google ,Mozilla , New Relic
, O’Reilly Media
, Etsy , dynaTrace
, Instart Logic
, Catchpoint Systems, Fastly , SOASTA
mPulse , and Hosting Facts.
From the beginning, Pat and WebPageTest made the HTTP Archive possible. Ilya and Rick will join Pat to make the HTTP Archive even better. A few of the current items on theagenda:
* Enrich the collected data during the crawl: detect JavaScript libraries in use on the page, integrate and capture LightHouse audits, feature counters, and so on. * Build new analysis pipelines to extract more information from thepast crawls
* Provide better visualizations and ways to explore the gathereddata
* Improve code health and overall operation of the full pipeline* … and lots more
– please chime in with your suggestions! Since its inception, the HTTP Archive has become the goto source for objective, documented data about how the Web is built. Thanks to Ilya, that data was brought to BigQuery so the community can perform their own queries and follow-on research.
It’s a joy to see the data and graphs from HTTP Archive used on a daily basis in tech articles, blog posts, tweets, etc. I’m excited about this next phase for the HTTP Archive. Thank you to everyone who helped get the HTTP Archive to where it is today. (Especially Stephen Hay for our awesome logo!) Now let’s make the HTTP Archive even better! Comments Off on HTTP Archive New Leadership_recent posts:_
VELOCITY FAREWELL
November 9, 2016 5:45 am | 5 Comments Velocity Origin Story In 2007, my first book, High Performance Web Sites, was selling very well. That, plus the launch of YSlow, brought more attention to web performance. As a result, Jon Jenkins invited me to give a tech talk at Amazon. Afterward, he, John Rauser, and I, plus a few other performance-minded folk, had a HTTP ARCHIVE SWITCHES TO CHROME May 23, 2016 9:08 am | 8 Comments The HTTP Archive crawls the world’s top URLs twice each month and records detailed information like the number of HTTP requests, the most popular image formats, and the use of gzip compression. In addition to aggregate stats, the HTTP Archive has the same data for individual websites plus images and video of the site loading. CRITICAL METRIC: CRITICAL RESOURCES February 10, 2016 7:37 pm | 6 Comments A big change in the World of Performance for 2015 is the shift to metrics that do a better job of measuring the user experience. The performance industry grew up focusing on page load time, but teams with more advanced websites have started replacing PLTBOOKS
High Performance Web Sitesby: Steve Souders
website
Even Faster
Web Sites
by: Steve Souders
website
Web Performance
Daybook Volume 2
edited by: Stoyan Stefanovwebsite
TWEETS
PROJECTS
* HTTP Archive
* Browserscope
* Episodes
* ControlJS
* Mobile Perf
TALKS
More
VIDEOS
Make JavaScript FasterMetrics of Joy
Design+Performance
High Speed UX
Prebrowsing
Perception of Speed
How fast are we going now? Dive into PerformanceCache is King
High Performance HTML5 Your script just killed my site High Performance Mobile Even Faster Web SitesMore
Steve Souders
Details
Copyright © 2024 ArchiveBay.com. All rights reserved. Terms of Use | Privacy Policy | DMCA | 2021 | Feedback | Advertising | RSS 2.0