Podcasts about yslow

Hello fellow Web Performance enthusiasts! Just like in the song, this podcast has been coming for some time. Quite some time. In fact, this first episode was recorded about a year ago. So please add 1 year to any time-sensitive bits you hear.The first guest is Steve Souders. I think Steve has done more than any other living person when it comes to raising awareness about Web Performance and how important it is to both users and companies. He also showed us the way to enlightenment with his books High-Performance Web Sites and its follow up Even Faster Web Sites. He was the brains behind the YSlow browser extension. Some of you younger folks may have not used YSlow, since you have all these powerful dev tools shipped with modern browsers. But in my opinion YSlow is right there after Firebug in terms of influence and showing the browser vendors what tools they should be providing.I'm lucky enough to have worked with Steve at Yahoo on YSlow and other stuff. He then moved on to do his magic at Google, and is now at SpeedCurve. We talk about all of this in the interview.One thing people may not know about Steve is that he plays ukulele. We jammed a bit after recording this podcast and then I thought I should cut up some of these sounds and mix them with the interview. Enjoy!

Artikel: http://www.frankwatching.com/archive/2015/07/07/7-mythes-betere-laadtijd-website/ “Deze podcast wordt mede mogelijk gemaakt door Byte. De hostingpartner die je website helpt groeien.” Auteur: http://www.frankwatching.com/archive/author/suzanne-de-lange/ Over Suzanne de Lange: In haar rol als contentmarketeer en communicatiemanager bij webhoster Byte is Suzanne dagelijks bezig met het creëren van content waar webprofessionals enthousiast van worden en van leren. Haar passie ligt bij het enthousiasmeren en activeren van de juiste doelgroep via de juiste middelen. En bij hardlopen, goede wijn en lekker eten … Contact: Twitter: @SuzannedLange https://www.linkedin.com/in/sadelange Werkt bij: https://www.byte.nl Bellen op 020-5216226 & vragen naar Suzanne 1e alinea van het artikel: “Een snelle website is een betere website.” Het zal vast niet de eerste keer zijn dat je dit hoort. Verschillende onderzoeken wijzen uit dat de laadtijd van een website een directe invloed heeft op het succes van een site. Er wordt echter nog wel eens wat geroepen dat niet of maar gedeeltelijk waar blijkt te zijn. In dit artikel bespreek ik 7 van die mythes die ik regelmatig voorbij hoor komen. Vragen: - Welke 3 redenen kun je noemen waarom je een website wilt hebben die snel laadt? (Bezoekers hebben een hekel aan wachten / risico op snel vertrek, Gebruiksvriendelijker door sneller door je site klikken, Google beloont snel ladende sites) - Is er één magische oplossing om mijn site sneller te maken? - Grote afbeeldingen zijn dodelijk voor de laadtijd toch? Ik zie wel eens sites met afbeeldingen van 3MB (2000 x 2000 pixels) die vervolgens op de site in een frame van 200 x 200 wordt weergegeven. - Als je veel traffic/bezoekers hebt, wordt je site dan ook trager? Of moet je dan vooral op zoek naar een andere hosting partij? - Is de Hoster dan de heilige graag als het gaat om een snelle laadtijd op je website? - Een CDN maakt mijn site sneller. CDN staat voor Content Distribution Network of Content Distribution Network). Kun je uitleggen wat zo’n CDN doet en wat het kan bijdragen in de laadtijd? Ik maak voor mijn sites Jelle Drijver.nl en MegaExposure.nl bijvoorbeeld gebruik van Cloudflare. Welke CDN netwerken kun je aanbevelen? - SSL certificaten vertragen de boel maar aan de andere kant hecht Google juist waarde aan websites die beveiligd zijn middels SSL certificaten. Wat is nou wijsheid? - En maakt social media buttons je site ook (veel) trager? Is hier wat aan te doen? VRAGEN PUBLIEK: VRAAG 1: Roel Braam | @roelbr | 7 juli 2015 om 11:47 uur Als je benieuwd bent naar de snelheid van je website, kun je dat online testen met Pingdom Tools (http://tools.pingdom.com, wel even bij settings Amsterdam als testserver aanvinken) of Google Pagespeed Insights (https://developers.google.com/speed/pagespeed/insights/) EN ySlow (vergelijkbaar maar dan van Yahoo) Je krijgt dan ook een mooie rapportage waaruit meteen blijkt waar wat vertragingen op je site veroorzaakt. VRAAG 2: Rolf Diepeveen | 7 juli 2015 om 13:07 uur een CDN is voor een nederlandse website in de meeste gevallen helemaal niet nodig. Doe het zeker niet als je niet weet hoe je het in moet richten; voordat je het weet ben je bijvoorbeeld niet meer vindbaar in Google afbeeldingen. De beste resultaten halen wij door een kale VPN te kiezen bij een goede hosting partij en die zelf in te richten met WordPress, NGINX en Google Pagespeed module en caching op de server. Snelheden van 0,2 seconden zijn dan haalbaar! - Links: https://www.byte.nl/ https://www.byte.nl/whitepaper/ https://nl.linkedin.com/in/sadelange http://twitter.com/SuzannedLange Http://Frankwatching.com Http://Frankwatching.com/podcast http://twitter.com/Frankwatching http://jelledrijver.nl http://twitter.com/JelleDrijver https://nl.linkedin.com/in/JelleDrijver Tools: http://tools.pingdom.com/fpt/ https://developers.google.com/speed/pagespeed/insights http://NewRelic Een snelle website heeft een directe invloed op de vindbaarheid, usability en je omzet. Maar hoe zorg je dat jouw site net zo snel laadt als de echt succesvolle sites wereldwijd? Hoe snel is dat? En wie moet dat voor je regelen? Met de whitepaper “Mythes over snelheid, en wat wel werkt om je site sneller te maken” bieden we marketeers, e-commercemanagers en projectmanagers een ideaal overzicht over de snelheid van een website. GA NAAR https://www.byte.nl/whitepaper/ en download gratis het Whitepaper van Byte voor meer uitgebreide tip’s & Tricks t.a.v. het optimaliseren van je website. “Deze podcast werd mede mogelijk gemaakt door Byte. De hostingpartner die je website helpt groeien.” Keywords: Byte, Hosting, Snelheid website, laadtijd, Mythes, Frankwatching, Jelle Drijver, Suzanne de Lange, Websites, Website, SEO, Yslow, Newrelic, Pingdom

We tuned the databases - for scaling up and scaling out - grids and clouds and no-sql. We tuned the servers - for scaling up and scaling out - farms and clusters and automated deployment. We tuned the network - accelerations and caching and CDNs. What's next? Web Performance Optimization - appealing to developers and designers alike, we are focusing on that last (or maybe first) piece of the puzzle: the client-side. There's been an explosion of tools and techniques around browser optimization and performance analysis, since the first time Steve Souders released the first version of YSlow! Now we have a twitter hash tage #WPO, meetup groups from New York to Seattle, to Frankfurt and Beijing. Vendors are rampantly adding "web performance" capabilities in their existing tools - trying to catch-up with the myriad open-source utilities employed by engineers learning the #WPO craft. This episode of PerfBytes will jump into the party and pass around a wealth of advice and context to understand the Web Performance Optimization fad.Original Air Date: Tuesday, January 8th, 2013 8AM EST

Vou te contar, se perder KG fosse tão fácil quando perder MB, eu era modelo e não programador! Mas já que, mesmo com uma força do Crockford pra perder KG ainda é difícil, vamos ficar com todas as dicas do Marcel Duran pra perder MB no front-end e ganhar velocidade e performance.

We tuned the databases - for scaling up and scaling out - grids and clouds and no-sql. We tuned the servers - for scaling up and scaling out - farms and clusters and automated deployment. We tuned the network - accelerations and caching and CDNs. What's next? Web Performance Optimization - appealing to developers and designers alike, we are focusing on that last (or maybe first) piece of the puzzle: the client-side. There's been an explosion of tools and techniques around browser optimization and performance analysis, since the first time Steve Souders released the first version of YSlow! Now we have a twitter hash tage #WPO, meetup groups from New York to Seattle, to Frankfurt and Beijing. Vendors are rampantly adding "web performance" capabilities in their existing tools - trying to catch-up with the myriad open-source utilities employed by engineers learning the #WPO craft. This episode of PerfBytes will jump into the party and pass around a wealth of advice and context to understand the Web Performance Optimization fad.Original Air Date: Tuesday, January 8th, 2013 8AM EST

Schnelle Websites haben bessere Conversion Rates, weil die Besucher sich unbekümmerter auf der Seite bewegen. Die Navigation fällt einfacher. Auch Google will schnelle Websites in seinen Suchergebnissen bevorzugen. In dieser Conversion Clinic zeigen wir Tools und Methoden, die rasch zu schnelleren Seiten und somit höheren Conversion Rates führen können.

Steve works at Google on web performance and open source initiatives. His book, Even Faster Web Sites, explains his best practices for performance. Steve is the creator of YSlow, one of the top 25 Firefox add-ons.

Web 2.0 is adding more and more content to our pages, especially features that are implemented in Ajax. But our web applications are evolving faster than the browsers that they run in. We don't have to rely on or wait for the release of new browsers to make our web applications faster. In this session, Steve Souders discusses web performance best practices from his second book, Even Faster Web Sites. These time-saving techniques are used by the world's most popular web sites to create a faster user experience, increase revenue, and reduce operating costs. Steve provides technical details about reducing the pain of JavaScript, as well as secrets for making your page load faster in emerging markets where network connectivity is a challenge. Steve works at Google on web performance and open source initiatives. He previously served as Chief Performance Yahoo!. Steve is the author of High Performance Web Sites and Even Faster Web Sites. He created YSlow, the performance analysis plug-in for Firefox. He serves as co-chair of Velocity, the web performance and operations conference from O’Reilly, and is co-founder of the Firebug Working Group. He recently taught CS193H: High Performance Web Sites at Stanford University. Follow Steve on Twitter: @souders Licensed as Creative Commons Attribution-Share Alike 3.0 (http://creativecommons.org/licenses/by-sa/3.0/).

After harvesting the performance low-hanging fruits suggested by YSlow and PageSpeed, what do you do next to improve the performance of your web application? You work on improving the user's perception of speed and time. We all know perceptions lie and perceptions of time and duration even more so. So how do you make users believe the application is fast and responsive? The word is "progressive". When the page components download in parallel and don't block each other, the page loads quicker. And when the page renders progressively, it not only gives the user confidence and assurance that the applications works fine and they'll soon complete their task but it also appears that the app is snappier and more responsive. More info at: https://fronteers.nl/congres/2010/sessions/progressive-downloads-and-rendering-stoyan-stefanov

After harvesting the performance low-hanging fruits suggested by YSlow and PageSpeed, what do you do next to improve the performance of your web application? You work on improving the user's perception of speed and time. We all know perceptions lie and perceptions of time and duration even more so. So how do you make users believe the application is fast and responsive? The word is "progressive". When the page components download in parallel and don't block each other, the page loads quicker. And when the page renders progressively, it not only gives the user confidence and assurance that the applications works fine and they'll soon complete their task but it also appears that the app is snappier and more responsive. More info at: https://fronteers.nl/congres/2010/sessions/progressive-downloads-and-rendering-stoyan-stefanov

Web 2.0 is adding more and more content to our pages, especially features that are implemented in Ajax. But our web applications are evolving faster than the browsers that they run in. We don’t have to rely on or wait for the release of new browsers to make our web applications faster. In this session, Steve Souders discusses web performance best practices from his second book, Even Faster Web Sites. These time-saving techniques are used by the world’s most popular web sites to create a faster user experience, increase revenue, and reduce operating costs. Steve provides technical details about reducing the pain of JavaScript, as well as secrets for making your page load faster in emerging markets where network connectivity is a challenge. Steve works at Google on web performance and open source initiatives. He previously served as Chief Performance Yahoo!. Steve is the author of High Performance Web Sites and Even Faster Web Sites. He created YSlow, the performance analysis plug-in for Firefox. He serves as co-chair of Velocity, the web performance and operations conference from O’Reilly, and is co-founder of the Firebug Working Group. He recently taught CS193H: High Performance Web Sites at Stanford University. Licensed as Creative Commons Attribution-Share Alike 3.0 (http://creativecommons.org/licenses/by-sa/3.0/).

Nick Zadrozny takes us on a tour of basic website performance optimization, covering 13 optimizations you shouldn't deploy your site without. He'll also go over some sample implementations for a typical Rails app, including a demo of how to serve your public assets from Amazon's new CloudFront CDN.

Episode 001 We talk about web services and client vs server side computation. Links: cURL (http://curl.haxx.se) Cairngorm (http://labs.adobe.com/wiki/index.php/Cairngorm) Cairngorm Diagram (http://cairngormdocs.org/cairngormDiagram/index.html) Yahoo Performance (http://developer.yahoo.com/performance) YSlow (http://developer.yahoo.com/yslow/ FireBug (http://getfirebug.com) Amazon Web Services (http://aws.amazon.com) Mechanical Turk (http://www.amazon.com/Mechanical-Turk-AWS-home-page/b/ref=sc_fe_l_4/002-2198112-8561623?ie=UTF8&node=15879911&no=3440661&me=A36L942TSJ2AJA) Mechanical Turk Workers (http://mturk.com)

Ajaxians interview Joe Hewitt of Firebug and iUI fame about debugging tips, YSlow, iPhones, the history of Firefox, and more.

Carl and Richard talk to Steven Souders, creator of YSlow, an analysis tool for finding website bottlenecks on the client side of the equation.Support this podcast at — https://redcircle.com/net-rocks/donations