How many photo carousels have you built? Date pickers? Dynamic tables and charts? Wouldn't it be great if there was a way to make these custom elements encapsulated and reusable? Welcome to Web Components! The building blocks are well known: HTML templates, custom elements, HTML imports, and shadow DOM. It's fairly easy to build simple examples. But what happens when performance degrades? Join this discussion of the synchronous and asynchronous nature of web components, and how they can impact the rendering of the entire page.
The document discusses techniques for loading JavaScript files to optimize website performance. It describes methods like splitting the initial payload, loading scripts asynchronously without blocking parsing and rendering, and deferring non-critical scripts. Examples of major sites like Gmail, Facebook, Google and Wikipedia that use these techniques are also provided.
The document discusses techniques for improving frontend web performance, including splitting codepayloads, loading scripts without blocking, and not scattering scripts across pages. It recommends focusing first on optimizing frontend performance since 80-90% of end user response time is spent loading frontend resources. Specific techniques include splitting JavaScript payloads into above-the-fold and below-the-fold code, using techniques like XHR and iframes to load scripts asynchronously without blocking page rendering, and avoiding placing inline scripts between stylesheets and other page resources.
Web Directions South - Even Faster Web SitesSteve Souders
The document discusses techniques for optimizing web page performance, including loading scripts asynchronously without blocking page rendering, splitting scripts into critical and non-critical parts, leveraging content delivery networks, minimizing downloads, and using new web standards like the Navigation Timing API. It emphasizes the importance of front-end optimization and progressive enhancement to improve site speed. Examples are given of how major sites like Google, Facebook, and Wikipedia optimize script loading.
High Performance Mobile (SF/SV Web Perf)Steve Souders
1. The document discusses optimizing websites for high performance mobile experiences. It provides 14 best practices for mobile optimization, including making fewer HTTP requests, using content delivery networks, gzipping components, and optimizing images.
2. Mobile optimization is important because mobile internet usage is growing rapidly. Performance impacts metrics like user experience and revenue.
3. Tools for measuring and improving mobile performance are introduced, such as PcapPerf for analyzing network traffic and Weinre for debugging JavaScript on mobile devices. Faster mobile sites will have an advantage as mobile becomes the primary internet platform.
Which would you rather have: A rich design or a fast user experience? Users want both, but sometimes the interplay between design and performance feels like a fixed sum game: One side’s gain is the other side’s loss. Design and performance are indeed connected, but it’s more like the yin and yang. They aren’t opposing forces, but instead complement each other. Users want an experience that is rich and fast. The trick for us as designers and developers is figuring out how to do that.
The answer is to adopt an approach that considers both design and performance from the outset. With this approach, designs are conceived by teams of designers and developers working together. Developers benefit by participating in the product definition process. Designers benefit from understanding more about how designs are implemented. There’s an emphasis on early prototyping and tracking performance from the get-go.
With new metrics that focus on what a user actually sees as the page loads, we can now bridge the technical and language gaps that have hindered the seamless creation of great user experiences. In this presentation, Steve Souders, former Chief Performance Yahoo! and Google head performance engineer, explains how promoting a process that brings design and performance together at the beginning of a project helps deliver a web experience that is both fast and rich.
The document discusses techniques for prebrowsing or prefetching resources to improve page load performance. It describes how developers can use <link> tags with rel="dns-prefetch", rel="prefetch", and rel="prerender" to hint to browsers on resources that could be pre-resolved, pre-downloaded or pre-rendered before they are needed. It also explains how browsers perform internal prefetching optimizations like DNS pre-resolution, TCP pre-connection and prefetching of likely-needed resources during page transitions using predictors. The goal is to get resources the browser will need before it needs them to reduce load times.
How many photo carousels have you built? Date pickers? Dynamic tables and charts? Wouldn't it be great if there was a way to make these custom elements encapsulated and reusable? Welcome to Web Components! The building blocks are well known: HTML templates, custom elements, HTML imports, and shadow DOM. It's fairly easy to build simple examples. But what happens when performance degrades? Join this discussion of the synchronous and asynchronous nature of web components, and how they can impact the rendering of the entire page.
The document discusses techniques for loading JavaScript files to optimize website performance. It describes methods like splitting the initial payload, loading scripts asynchronously without blocking parsing and rendering, and deferring non-critical scripts. Examples of major sites like Gmail, Facebook, Google and Wikipedia that use these techniques are also provided.
The document discusses techniques for improving frontend web performance, including splitting codepayloads, loading scripts without blocking, and not scattering scripts across pages. It recommends focusing first on optimizing frontend performance since 80-90% of end user response time is spent loading frontend resources. Specific techniques include splitting JavaScript payloads into above-the-fold and below-the-fold code, using techniques like XHR and iframes to load scripts asynchronously without blocking page rendering, and avoiding placing inline scripts between stylesheets and other page resources.
Web Directions South - Even Faster Web SitesSteve Souders
The document discusses techniques for optimizing web page performance, including loading scripts asynchronously without blocking page rendering, splitting scripts into critical and non-critical parts, leveraging content delivery networks, minimizing downloads, and using new web standards like the Navigation Timing API. It emphasizes the importance of front-end optimization and progressive enhancement to improve site speed. Examples are given of how major sites like Google, Facebook, and Wikipedia optimize script loading.
High Performance Mobile (SF/SV Web Perf)Steve Souders
1. The document discusses optimizing websites for high performance mobile experiences. It provides 14 best practices for mobile optimization, including making fewer HTTP requests, using content delivery networks, gzipping components, and optimizing images.
2. Mobile optimization is important because mobile internet usage is growing rapidly. Performance impacts metrics like user experience and revenue.
3. Tools for measuring and improving mobile performance are introduced, such as PcapPerf for analyzing network traffic and Weinre for debugging JavaScript on mobile devices. Faster mobile sites will have an advantage as mobile becomes the primary internet platform.
Which would you rather have: A rich design or a fast user experience? Users want both, but sometimes the interplay between design and performance feels like a fixed sum game: One side’s gain is the other side’s loss. Design and performance are indeed connected, but it’s more like the yin and yang. They aren’t opposing forces, but instead complement each other. Users want an experience that is rich and fast. The trick for us as designers and developers is figuring out how to do that.
The answer is to adopt an approach that considers both design and performance from the outset. With this approach, designs are conceived by teams of designers and developers working together. Developers benefit by participating in the product definition process. Designers benefit from understanding more about how designs are implemented. There’s an emphasis on early prototyping and tracking performance from the get-go.
With new metrics that focus on what a user actually sees as the page loads, we can now bridge the technical and language gaps that have hindered the seamless creation of great user experiences. In this presentation, Steve Souders, former Chief Performance Yahoo! and Google head performance engineer, explains how promoting a process that brings design and performance together at the beginning of a project helps deliver a web experience that is both fast and rich.
The document discusses techniques for prebrowsing or prefetching resources to improve page load performance. It describes how developers can use <link> tags with rel="dns-prefetch", rel="prefetch", and rel="prerender" to hint to browsers on resources that could be pre-resolved, pre-downloaded or pre-rendered before they are needed. It also explains how browsers perform internal prefetching optimizations like DNS pre-resolution, TCP pre-connection and prefetching of likely-needed resources during page transitions using predictors. The goal is to get resources the browser will need before it needs them to reduce load times.
Making users happy is a goal that unifies everyone on the team. The key then is to establish metrics that reflect user happiness. In the world of performance, we haven’t always done a great job of this. Often, performance metrics track how our pages are built which might not be correlated with a joyous user experience, and we start optimizing our stack for the sake of optimizing our stack. Luckily, momentum is building around UX-centered metrics such as start render time, time-to-interact, and first meaningful paint. Steve Souders discusses these new metrics that help us build web apps that produce the fast, joyous experiences our users want.
This document discusses strategies for improving JavaScript performance on websites. It begins by noting that JavaScript is often the number one cause of slow web pages. It then reviews the history of JavaScript loading approaches, from loading scripts in the page head in 1995 to more modern async and deferred loading. It discusses using localStorage as a cache and the Google Analytics async snippet as examples. It concludes by recommending tools and resources for measuring and improving JavaScript performance, including WebPagetest.org, ControlJS, and Steve Souders' own site and books.
Every URL visited from the Facebook iPhone app is done through a webview. Same with Twitter. Even if you don't have a mobile app, your website gets a lot of traffic from webviews. And yet, testing on webviews is challenging. There are significant performances differences between UIWebView vs WkWebView, and similarly for Android webview vs the new Chromium webview. And what about home screen apps?! In this talk, Steve Souders discusses the differences across webviews and how that affects performance of mobile web apps.
The document discusses the speed of the modern web. It summarizes key metrics around connection speeds, browser speeds, page weights, adoption of best practices, and page load times based on data from various sources. While some metrics like connection speeds and page load times are improving, pages overall are getting heavier and adoption of best practices is flat. The document advocates watching video growth, developing better performance metrics, promoting best practices more widely, utilizing multiple CPUs, and improving caching.
Presentation at WebPerfDays Amsterdam, May 18 2013.
This newish browser API can be used to gain insight in the load time of individual page resources. Does the API behave consistently and as expected? Short answer: no, not really. Long answer: view the presentation ;-)
This document discusses the importance of web performance optimization and techniques for improving page load speeds, particularly around optimizing JavaScript loading. It notes that speed is a critical user experience factor and outlines strategies like progressive rendering, loading scripts without blocking, and techniques like ControlJS for asynchronously downloading and delaying script execution. The document emphasizes the growing importance of mobile optimization and speed given rising usage on mobile devices.
All of us have a lurking failure in our websites: 3rd party scripts from ads, widgets, and analytics. How is it that one script can bring down your website?
1. Synchronous scripts block page rendering, so scripts should be loaded asynchronously.
2. Front-end dependencies like social media widgets can cause slowdowns if they fail to load. Blackholing domains in tests can show these slowdowns.
3. "Bootstrap scripts" from content delivery networks often have short cache times, increasing chances of failures. But they can be made self-updating while keeping long cache times.
The document discusses the frontend single point of failure (SPOF) problem caused by blocking JavaScript and CSS files. It provides examples of popular websites, code libraries, widgets, and content management systems that contribute to frontend SPOFs. The document recommends solutions for browsers, widget owners, CMS developers, and site owners to address this issue through asynchronous loading of resources and better monitoring of frontend performance.
This document summarizes Steve Souders' presentation on web performance optimization (WPO). It discusses how speed is the most important website feature and outlines techniques to improve performance like optimizing assets, reducing page weight, and leveraging caching. It also covers emerging trends like SPDY and improvements to third-party content. The key takeaways are that WPO matters significantly, new standards are coming, and guarding against slow third-party code.
This document summarizes Christopher Schmitt's presentation on adaptive images in responsive web design. It discusses using feature testing versus browser sniffing to determine the appropriate image to serve, including testing browser width, screen resolution, and bandwidth. It then covers various techniques for serving adaptive images, such as using .htaccess files, the <picture> element, srcset attributes, and JavaScript libraries. It emphasizes using a mobile-first approach and progressive enhancement to provide the best experience for all devices.
The document discusses techniques for improving frontend web performance, with a focus on optimizing JavaScript loading. It recommends splitting code downloads into above-the-fold and enhancements sections, loading scripts asynchronously and in parallel without blocking, and avoiding scattered inline scripts. Key techniques include loading scripts with XMLHttpRequest, in iframes, or dynamically creating script elements.
The document discusses techniques for improving frontend web performance, including splitting code into critical and non-critical sections, loading scripts asynchronously without blocking other downloads, and avoiding scattering scripts throughout a page. It provides examples of sites that could benefit from these techniques and recommends tools like YSlow for auditing performance. The overall message is that frontend optimizations like JavaScript improvements can significantly speed up sites.
Java REST API Framework Comparison - PWX 2021Matt Raible
Use Spring Boot! No, use Micronaut!! Nooooo, Quarkus is the best!!!
There's a lot of developers praising the hottest, and fastest, Java REST frameworks: Micronaut, Quarkus, and Spring Boot. In this session, you'll learn how to do the following with each framework:
✅ Build a REST API
✅ Secure your API with OAuth 2.0
✅ Optimize for production with Docker and GraalVM
I'll also share some performance numbers and pretty graphs to compare community metrics.
Related blog post: https://developer.okta.com/blog/2021/06/18/native-java-framework-comparison
"Will Git Be Around Forever? A List of Possible Successors" at UtrechtJUG🎤 Hanno Embregts 🎸
What source control software did you use in 2010? Possibly Git, if you were an early adopter or a Linux kernel committer. But chances are you were using Subversion, as this was the product of choice for the majority of the software developers. Ten years later, Git is the most popular product. Which makes me wonder: what will we use another ten years from now?
In this talk we will think about what features we want from our source control software in 2030. More speed? Better collaboration support? No merge conflicts ever?
I’ll also discuss a few products that have been published after Git emerged, including Plastic, Fossil and Pijul. I’ll talk about the extent to which they contain the features we so dearly desire and I’ll demonstrate a few typical use cases. To conclude, I’ll try to predict which one will be ‘the top dog’ in 2030 (all information is provided “as is”, no guarantees etc. etc.).
So attend this session if you’re excited about the future of version control and if you want to have a shot at beating even (!) the early adopters. Now if it turns out I was right, remember that you heard it here first.
High Performance JavaScript (CapitolJS 2011)Nicholas Zakas
High Performance JavaScript provides techniques for optimizing JavaScript performance. It discusses how JavaScript execution blocks the browser UI thread, preventing responsive user experiences. It recommends limiting individual JavaScript jobs to under 50ms to avoid unresponsiveness. The document then provides techniques to improve load time performance such as dynamically loading scripts, and runtime techniques like timers and web workers to avoid blocking the UI thread during long-running processes.
Building a PWA - For Everyone Who Is Scared ToRaymond Camden
This document provides an overview of building progressive web apps (PWAs). It discusses the key technologies needed for PWAs including manifest files, service workers, and app shells. It provides examples of how to add a manifest to enable installable web apps, how to cache assets using service workers, and how to send push notifications. While Safari and iOS do not fully support these technologies yet, the document notes they are being developed for future releases.
Dreamweaver CS6, jQuery, PhoneGap, mobile designDee Sadler
A session talk for #NAGW2012 on:
Mobile app, choices
Dreamweaver’s place
Creating Mobile Design (actual design, not code)
Other helpful Adobe tools to create HTML/CSS
jQuery Mobile in DW
PhoneGap Build in DW
This document discusses ECMAScript 2015 (ES2015), also known as ES6. It provides examples of new ES2015 features like arrow functions, template literals, classes, and modules. It also discusses how to set up a development environment to use ES2015, including transpiling code to ES5 using Babel, linting with Eslint, testing with Mocha, and generating coverage reports with Istanbul. The document emphasizes that while ES2015 is fun to explore, proper tooling like linting and testing is needed for serious development. It concludes by noting ES2015 marks a transition and thanks the audience.
Bend dynamics and perceptions with conflict resolution and emotional safety tipsJenn Turner
The document is a calendar entry repeating "Thursday, September 8, 16" multiple times without any other details. It does not provide any meaningful information in the given format.
Making users happy is a goal that unifies everyone on the team. The key then is to establish metrics that reflect user happiness. In the world of performance, we haven’t always done a great job of this. Often, performance metrics track how our pages are built which might not be correlated with a joyous user experience, and we start optimizing our stack for the sake of optimizing our stack. Luckily, momentum is building around UX-centered metrics such as start render time, time-to-interact, and first meaningful paint. Steve Souders discusses these new metrics that help us build web apps that produce the fast, joyous experiences our users want.
This document discusses strategies for improving JavaScript performance on websites. It begins by noting that JavaScript is often the number one cause of slow web pages. It then reviews the history of JavaScript loading approaches, from loading scripts in the page head in 1995 to more modern async and deferred loading. It discusses using localStorage as a cache and the Google Analytics async snippet as examples. It concludes by recommending tools and resources for measuring and improving JavaScript performance, including WebPagetest.org, ControlJS, and Steve Souders' own site and books.
Every URL visited from the Facebook iPhone app is done through a webview. Same with Twitter. Even if you don't have a mobile app, your website gets a lot of traffic from webviews. And yet, testing on webviews is challenging. There are significant performances differences between UIWebView vs WkWebView, and similarly for Android webview vs the new Chromium webview. And what about home screen apps?! In this talk, Steve Souders discusses the differences across webviews and how that affects performance of mobile web apps.
The document discusses the speed of the modern web. It summarizes key metrics around connection speeds, browser speeds, page weights, adoption of best practices, and page load times based on data from various sources. While some metrics like connection speeds and page load times are improving, pages overall are getting heavier and adoption of best practices is flat. The document advocates watching video growth, developing better performance metrics, promoting best practices more widely, utilizing multiple CPUs, and improving caching.
Presentation at WebPerfDays Amsterdam, May 18 2013.
This newish browser API can be used to gain insight in the load time of individual page resources. Does the API behave consistently and as expected? Short answer: no, not really. Long answer: view the presentation ;-)
This document discusses the importance of web performance optimization and techniques for improving page load speeds, particularly around optimizing JavaScript loading. It notes that speed is a critical user experience factor and outlines strategies like progressive rendering, loading scripts without blocking, and techniques like ControlJS for asynchronously downloading and delaying script execution. The document emphasizes the growing importance of mobile optimization and speed given rising usage on mobile devices.
All of us have a lurking failure in our websites: 3rd party scripts from ads, widgets, and analytics. How is it that one script can bring down your website?
1. Synchronous scripts block page rendering, so scripts should be loaded asynchronously.
2. Front-end dependencies like social media widgets can cause slowdowns if they fail to load. Blackholing domains in tests can show these slowdowns.
3. "Bootstrap scripts" from content delivery networks often have short cache times, increasing chances of failures. But they can be made self-updating while keeping long cache times.
The document discusses the frontend single point of failure (SPOF) problem caused by blocking JavaScript and CSS files. It provides examples of popular websites, code libraries, widgets, and content management systems that contribute to frontend SPOFs. The document recommends solutions for browsers, widget owners, CMS developers, and site owners to address this issue through asynchronous loading of resources and better monitoring of frontend performance.
This document summarizes Steve Souders' presentation on web performance optimization (WPO). It discusses how speed is the most important website feature and outlines techniques to improve performance like optimizing assets, reducing page weight, and leveraging caching. It also covers emerging trends like SPDY and improvements to third-party content. The key takeaways are that WPO matters significantly, new standards are coming, and guarding against slow third-party code.
This document summarizes Christopher Schmitt's presentation on adaptive images in responsive web design. It discusses using feature testing versus browser sniffing to determine the appropriate image to serve, including testing browser width, screen resolution, and bandwidth. It then covers various techniques for serving adaptive images, such as using .htaccess files, the <picture> element, srcset attributes, and JavaScript libraries. It emphasizes using a mobile-first approach and progressive enhancement to provide the best experience for all devices.
The document discusses techniques for improving frontend web performance, with a focus on optimizing JavaScript loading. It recommends splitting code downloads into above-the-fold and enhancements sections, loading scripts asynchronously and in parallel without blocking, and avoiding scattered inline scripts. Key techniques include loading scripts with XMLHttpRequest, in iframes, or dynamically creating script elements.
The document discusses techniques for improving frontend web performance, including splitting code into critical and non-critical sections, loading scripts asynchronously without blocking other downloads, and avoiding scattering scripts throughout a page. It provides examples of sites that could benefit from these techniques and recommends tools like YSlow for auditing performance. The overall message is that frontend optimizations like JavaScript improvements can significantly speed up sites.
Java REST API Framework Comparison - PWX 2021Matt Raible
Use Spring Boot! No, use Micronaut!! Nooooo, Quarkus is the best!!!
There's a lot of developers praising the hottest, and fastest, Java REST frameworks: Micronaut, Quarkus, and Spring Boot. In this session, you'll learn how to do the following with each framework:
✅ Build a REST API
✅ Secure your API with OAuth 2.0
✅ Optimize for production with Docker and GraalVM
I'll also share some performance numbers and pretty graphs to compare community metrics.
Related blog post: https://developer.okta.com/blog/2021/06/18/native-java-framework-comparison
"Will Git Be Around Forever? A List of Possible Successors" at UtrechtJUG🎤 Hanno Embregts 🎸
What source control software did you use in 2010? Possibly Git, if you were an early adopter or a Linux kernel committer. But chances are you were using Subversion, as this was the product of choice for the majority of the software developers. Ten years later, Git is the most popular product. Which makes me wonder: what will we use another ten years from now?
In this talk we will think about what features we want from our source control software in 2030. More speed? Better collaboration support? No merge conflicts ever?
I’ll also discuss a few products that have been published after Git emerged, including Plastic, Fossil and Pijul. I’ll talk about the extent to which they contain the features we so dearly desire and I’ll demonstrate a few typical use cases. To conclude, I’ll try to predict which one will be ‘the top dog’ in 2030 (all information is provided “as is”, no guarantees etc. etc.).
So attend this session if you’re excited about the future of version control and if you want to have a shot at beating even (!) the early adopters. Now if it turns out I was right, remember that you heard it here first.
High Performance JavaScript (CapitolJS 2011)Nicholas Zakas
High Performance JavaScript provides techniques for optimizing JavaScript performance. It discusses how JavaScript execution blocks the browser UI thread, preventing responsive user experiences. It recommends limiting individual JavaScript jobs to under 50ms to avoid unresponsiveness. The document then provides techniques to improve load time performance such as dynamically loading scripts, and runtime techniques like timers and web workers to avoid blocking the UI thread during long-running processes.
Building a PWA - For Everyone Who Is Scared ToRaymond Camden
This document provides an overview of building progressive web apps (PWAs). It discusses the key technologies needed for PWAs including manifest files, service workers, and app shells. It provides examples of how to add a manifest to enable installable web apps, how to cache assets using service workers, and how to send push notifications. While Safari and iOS do not fully support these technologies yet, the document notes they are being developed for future releases.
Dreamweaver CS6, jQuery, PhoneGap, mobile designDee Sadler
A session talk for #NAGW2012 on:
Mobile app, choices
Dreamweaver’s place
Creating Mobile Design (actual design, not code)
Other helpful Adobe tools to create HTML/CSS
jQuery Mobile in DW
PhoneGap Build in DW
This document discusses ECMAScript 2015 (ES2015), also known as ES6. It provides examples of new ES2015 features like arrow functions, template literals, classes, and modules. It also discusses how to set up a development environment to use ES2015, including transpiling code to ES5 using Babel, linting with Eslint, testing with Mocha, and generating coverage reports with Istanbul. The document emphasizes that while ES2015 is fun to explore, proper tooling like linting and testing is needed for serious development. It concludes by noting ES2015 marks a transition and thanks the audience.
Bend dynamics and perceptions with conflict resolution and emotional safety tipsJenn Turner
The document is a calendar entry repeating "Thursday, September 8, 16" multiple times without any other details. It does not provide any meaningful information in the given format.
NY Web Performance - DNS as a Web Performance ToolNS1
In this talk, NS1 CEO and co-founder, Kris Beevers, dives into:
- A DNS crash course and refresher
- What can go wrong with DNS configurations and how performance is impacted
- Optimizing DNS lookup performance
- Using DNS as an offensive tool to optimize application performance
This document provides an introduction and overview of ReactJS concepts including:
- Features of ReactJS like its component-based architecture and support for ES6
- What transpilers are and examples like Babel and Traceur
- Examples of setting up a basic "Hello World" React app with increasing complexity
- Additional concepts covered include properties, events, lists, conditional rendering, fetching external data and more
Functional Reactive Programming in JavascriptBrian Lonsdorf
Lightning is a giant discharge of electricity that can reach over five miles in length and raise air temperatures to 50,000 degrees Fahrenheit. On average, over 100 lightning bolts strike the Earth every second. Lightning is not confined to thunderstorms and has been seen in volcanic eruptions, forest fires, nuclear explosions, and heavy snowstorms.
HTTPS: What, Why and How (SmashingConf Freiburg, Sep 2015)Guy Podjarny
When users use our sites, they put their faith in us. They trust we will keep their information from reaching others, believe we provided the information they see, and allow us to run (web) code on their devices. Using HTTPS to secure our conversations is a key part of maintaining this trust.
If that’s not motivation enough, the web’s giants are actively promoting HTTPS, requiring it for features such as HTTP2 & ServiceWorker, using it for search engine ranking and more. To make the most of the web, you need to use HTTPS.
This deck reviews what HTTPS is, discusses why you should prioritize using it, and cover some of the easiest (and most cost effective) steps to get started using HTTPS
The document is a presentation about the Intel XDK, which is a tool that allows developers to build cross-platform mobile apps using HTML5, CSS, and JavaScript without needing native SDKs. It discusses how the XDK provides features like a code editor, emulator, debugging tools, and a cloud-based build system to streamline the app development process. It also provides examples of different types of apps that have been built with the XDK, such as games, city guides and educational apps.
Jam3 is a digital agency in Toronto that worked on the Vikings project to evaluate React and F1. F1 is an animation library that uses path finding to describe UI transitions like driving between locations. It works across platforms and with React. Chiefs are components that tell other components what state to be in. States and transitions are defined separately for consistency and testability. F1 is moving toward better documentation, tooling, and integration with design tools.
Design & Performance - Steve Souders at Fastly Altitude 2015Fastly
Fastly Altitude - June 25, 2015. Chief SpeedCurver Steve Souders explains how design and web performance are more interconnected than ever before. Users want a fast website with a rich design, but sometimes the interplay between design and performance feels like a fixed sum game: one side's gain is the other side's loss. Design and performance are indeed connected, but it's more like the yin and yang. They aren't opposing forces, but instead complement each other. Bringing these processes together produces experiences that are rich and fast.
Video from the talk: http://fastly.us/Altitude2015_Design-Performance
Steve's bio: Steve Souders is a co-founder at SpeedCurve, where he develops web performance services. His book, High Performance Web Sites, explains his best practices for performance; it was #1 in Amazon's Computer and Internet bestsellers. His follow-up book, Even Faster Web Sites, provides performance tips for today's Web 2.0 applications. Steve is the creator of many performance tools and services including YSlow, the HTTP Archive, Cuzillion, Jdrop, SpriteMe, ControlJS, and Browserscope. 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.
A presentation from SEO Campixx Barcamp 2011 in Berlin. Web Performance Optimization is about making websites faster. Here i discussed different measures and show the impact on competitive advantage and possibly rankings on Google. Undeniably you can say that better performance leads to more sales and better usability in terms of bouncing rates. View image slides here: http://b0i.de/wpopresentation
This document discusses various techniques for improving front-end web performance. It states that 80% of end-user response time is spent downloading page components like images, CSS, JavaScript, and that speed is important for user experience and functionality. Various methods are presented for minimizing file sizes like JavaScript minification and combining files. It also recommends techniques like using CSS sprites and lazy loading images. Browser tools for analyzing performance are listed, and references for further information are provided.
This document discusses strategies for improving SEO, including using microformats and schema to increase click-through rate, reducing page load times to decrease bounce rates, and properly handling links and redirects to maintain link juice. It provides examples of implementing microformats, measuring page speed, and types of redirects. The document recommends names, titles, and URLs to help pages rank better in search engines.
SearchLove San Diego 2018 | Mat Clayton | Site Speed for Digital MarketersDistilled
We all know that site speed matters not only for users but also for search rankings. As marketers, how can we measure and improve the impact of site speed? Mat will cover a range of topics and tools, from the basic quick wins to some of the more surprising and cutting-edge techniques used by the largest websites in the world.
This document discusses the evolution of web performance optimization (WPO). It notes that WPO drives traffic, improves user experience, increases revenue, and reduces costs. It outlines key metrics and tools for measuring and profiling performance, areas of research, best practices, and how WPO evangelism and automation have evolved. It suggests that WPO efforts will increasingly focus on mobile optimization going forward.
Dreamforce 14 : Responsive Design with Visualforce and Twitter BootstrapKeir Bowden
This document discusses responsive design using Visualforce and Twitter Bootstrap. It defines responsive design as providing an optimal viewing experience across devices by responding to screen size and orientation. It outlines the key techniques used in responsive design, including viewport meta tags, fluid grids, and CSS media queries. It then provides an overview of how Bootstrap can be used to build responsive user interfaces in Visualforce and demonstrates a sample blog application.
Core Web Vitals is a guidance from Google to delivering a great user experience on the web. There're three new metrics to define the website has a good experience or not. The metrics are Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift.
FEDSPUG November 2013: Developing Apps SharePoint 2013 by Danny JesseeWSPDC & FEDSPUG
This document contains a list of over 30 URLs linking to Microsoft webpages that provide information and documentation around developing apps and services for Microsoft products and platforms like SharePoint, Office, and Bing Maps. The URLs reference pages on topics such as setting up app domains, authentication, authorization, app packaging, hosting apps, and using the Office and SharePoint APIs.
Performance Budgets: Using APM Performance Data to Drive Decisions on Design ...AppDynamics
If a UI feature adds 500ms, can it be saved elsewhere? In a world in which personalization needs to be balanced with performance, this is a key question. The technique of performance budgets, a widely used concept in front-end development and design, can help you solve this. Hear how performance budgets using published examples from Lara Hogan at Etsy, Tim Kadlek, and other prominent developers can be exploited by the wider IT ecosystem.
Explore common, real-world application performance management examples of how performance budgets play out at customers such as Vodafone and Barclays. Learn how AppDynamics can help you balance your performance budget to keep customers and your CIO happy.
Key takeaways:
o How performance budgets provide a universal language between development, product, and the business
o Using performance budgets through the app lifecycle validate that they continue to meet users' expectations
o Help quantify the impact of poor performance and better balance performance vs. features
For more information, go to: www.appdynamics.com
This document summarizes techniques for optimizing image delivery on mobile websites. It discusses 4 key optimizations: adjusting image quality, choosing optimal file formats like WebP, sizing images responsively, and lazy loading images below the fold. The document shows that these techniques can significantly reduce image file sizes and page load times based on analyses of 500,000 mobile sites. Specific tools are recommended for automating quality adjustments, format conversion, and responsive image breakpoint generation. Lazy loading is shown to improve user experience by deferring loading of off-screen images. Overall, the techniques can help images remain fast to load while retaining high quality for modern responsive delivery.
AngularJS application on Visualforce for the Force.com platform and the Salesforce1 mobile application. Dreamforce 2014. Talk is given for experienced Salesforce developers who want to learn common features of AngularJS to build custom applications for the Salesforce1 mobile app.
This document outlines an agenda for a web performance training course. It introduces key concepts like why performance matters, how to define and measure performance metrics, and how to identify and address performance problems. It provides numerous links to tools and resources for auditing site performance, establishing performance budgets, monitoring performance over time, and optimizing code and assets to improve loading speed. The goal is to help attendees learn how to evaluate the performance of their sites and make them faster.
This document provides an agenda for an immersive workshop on styling and catching up. The agenda includes introductions, lectures on styling and image uploading, and hands-on labs for styling and image uploading. Frameworks discussed include Bootstrap, Foundation, and Semantic UI. Image uploading gems like Paperclip, Carrierwave, and Refile are also covered. The document concludes with references for further reading.
Get Started with Apps for SharePoint 2013Danny Jessee
This document contains a list of over 50 URLs linking to Microsoft developer documentation and other resources for creating apps for the SharePoint 2013 platform. The URLs provide information on setting up app domains, making SharePoint REST calls, using the SharePoint client object model, and other topics relevant to SharePoint app development.
ASPC 2015 - Building JavaScript to Stand the Test of TimeMarc D Anderson
The document provides links and recommendations for JavaScript frameworks, libraries, and tools including RequireJS, AMD, BreezeJS, image optimization, JavaScript linting tools, TypeScript, JavaScript editors, module and namespace patterns, and contact information for Marc Anderson and his projects.
This document discusses ways to make JavaScript faster in web pages. It recommends loading scripts asynchronously or with defer, preloading scripts, reducing CPU time spent evaluating scripts and function calls, budgeting third-party scripts, ensuring proper compression of scripts, and reviewing code coverage to optimize performance.
Which would you rather have: a website that’s fast or a website that’s perceived as fast? The answer is “Both!” The list of performance best practices is long and well known, but there’s been less focus on the user’s perception of speed. In this presentation Steve Souders provides examples of how the perception of speed is completely independent of actual speed, and techniques for leveraging this perception gap to create websites that feel fast.
How many photo carousels have you built? Date pickers? Dynamic tables and charts? Wouldn't it be great if there was a way to make these custom elements encapsulated and reusable? Welcome to Web Components! The building blocks are well known: HTML templates, custom elements, HTML imports, and shadow DOM. It's fairly easy to build simple examples. But what happens when performance degrades? Join this discussion of the synchronous and asynchronous nature of web components, and how they can impact the rendering of the entire page.
Cache is King discusses the importance of caching for website performance. It shows that enabling caching through techniques like setting Cache-Control headers can reduce page load times significantly. Specifically, using max-age to set expiration times for cacheable assets avoids unnecessary HTTP requests. For dynamic content, no-cache must be used to prevent caching. The document advocates being explicit with caching directives and measuring caching behavior to identify opportunities to optimize websites for cached access.
This document summarizes Steve Souders' presentation on web performance optimization (WPO). It discusses how speed is the most important website feature and outlines techniques to improve performance like optimizing assets, reducing page weight, and addressing third-party content. It also previews upcoming developments in WPO like browser tools, standards, and the growing focus on mobile and ensuring speed remains a key differentiator.
This document summarizes Steve Souders' presentation on front-end performance. It discusses the importance of front-end optimization, providing statistics on how much JavaScript impacts page load times. It also offers best practices for optimizing assets like JavaScript, CSS, images and caching. These include techniques like concatenating and minifying files, leveraging the browser cache, using CDNs and prioritizing visible content. The document emphasizes strategies like progressive enhancement and rendering to improve perceived performance.
CouchDB is a document-oriented NoSQL database that uses JSON documents with schema-free design. It features a built-in map/reduce function for querying indexes, and uses HTTP for an API and replication. CouchDB is robust, scales well, and is designed for high availability through its append-only writing and multi-version concurrency control.
Browserscope is an open-source project that profiles browsers to foster innovation and help web developers. It uses crowdsourcing to run tests on a wide variety of browsers and systems, aggregating the results to reduce biases and immediately detect changes in new and existing browsers. The current test categories examine network performance, Acid3 compliance, JavaScript and CSS capabilities, and rich text editing functions.
Presented at SXSW '09, this talk covers five best practices from my next book: Load scripts without blocking, Coupling asynchronous scripts, Don't scatter inline scripts, Use iframes sparingly, and Flush the document early.
EU Artificial Intelligence Act (High-level summary of the AI Act)prb404
Updated on 30 May in accordance with the Corrigendum version of the AI Act.
In this article we provide you with a high-level summary of the AI Act, selecting the parts which are most likely to be relevant to you regardless of who you are. We provide links to the original document where relevant so that you can always reference the Act text.
To explore the full text of the AI Act yourself, use our AI Act Explorer. Alternatively, if you want to know which parts of the text are most relevant to you, use our Compliance Checker.
View as PDF
Four-point summary
The AI Act classifies AI according to its risk:
Unacceptable risk is prohibited (e.g. social scoring systems and manipulative AI).
Most of the text addresses high-risk AI systems, which are regulated.
A smaller section handles limited risk AI systems, subject to lighter transparency obligations: developers and deployers must ensure that end-users are aware that they are interacting with AI (chatbots and deepfakes).
Minimal risk is unregulated (including the majority of AI applications currently available on the EU single market, such as AI enabled video games and spam filters – at least in 2021; this is changing with generative AI).
The majority of obligations fall on providers (developers) of high-risk AI systems.
Those that intend to place on the market or put into service high-risk AI systems in the EU, regardless of whether they are based in the EU or a third country.
And also third country providers where the high risk AI system’s output is used in the EU.
Users are natural or legal persons that deploy an AI system in a professional capacity, not affected end-users.
Users (deployers) of high-risk AI systems have some obligations, though less than providers (developers).
This applies to users located in the EU, and third country users where the AI system’s output is used in the EU.
General purpose AI (GPAI):
All GPAI model providers must provide technical documentation, instructions for use, comply with the Copyright Directive, and publish a summary about the content used for training.
Free and open licence GPAI model providers only need to comply with copyright and publish the training data summary, unless they present a systemic risk.
All providers of GPAI models that present a systemic risk – open or closed – must also conduct model evaluations, adversarial testing, track and report serious incidents and ensure cybersecurity protections.
Trust and Security, presented by Geoff HustonAPNIC
Geoff Huston, Chief Scientist at APNIC delivers a remote presentation on Internet fragmentation and its effect on the trust and security of Internet at VNNIC Internet Conference 2024 held in Hanoi, Vietnam from 4 to 7 June 2024.
Ethics guidelines for trustworthy AI (HIGH-LEVEL EXPERT GROUP ON ARTIFICIAL I...prb404
On 8 April 2019, the High-Level Expert Group on AI presented Ethics Guidelines for Trustworthy Artificial Intelligence. This followed the publication of the guidelines' first draft in December 2018 on which more than 500 comments were received through an open consultation.
According to the Guidelines, trustworthy AI should be:
(1) lawful - respecting all applicable laws and regulations
(2) ethical - respecting ethical principles and values
(3) robust - both from a technical perspective while taking into account its social environment
11. …shaved 2.2 seconds off the
average page load time and
increased download
conversions by 15.4%!
blog.mozilla.com/metrics/category/website-optimization/
12. We made the new platform 60%
faster and this resulted in a 14%
increase in donation conversions.
kylerush.net/blog/meet-the-obama-campaigns-250-million-fundraising-platform/
16. “traffic jumped from 6M to 11M uniques…
time spent on site rose from 5.9 to 7.8 minutes…
interaction rate on ads rose 108%”
17. Screen shot of blog post…we've decided to take site
speed into account in our
search rankings.
googlewebmastercentral.blogspot.com/2010/04/using-site-speed-in-web-search-ranking.html
18. “To stay in Google's good graces, websites
must be designed so they load quickly on
mobile devices.”
huffingtonpost.com/2015/04/17/google-search-update_n_7085642.html
24. Speed is more important
than design embellishment.
People are filling
small gaps in their
day with news. It
must load fast on all
touchpoints.
The design should
feel light and nimble,
always fresh and up
to date. Never
heavy, slow to load
or clogged up with
content.
Users expect sites
to render in under 2
seconds.
DAN/TBWA
33. window.onload RUM
• metrics from real users - COOL!
• reflect actual geo, hw, bw, etc.
• but, "start" time isn't right
• and timer has latency
Very excited about our next speaker and incredibly honored to have the opportunity to introduce him.
He and I are actually very much alike in many ways. We both care a lot about web performance and helping the devops community.
I think I'm a better coder.
And I will say his jokes aren't as funny as he thinks they are.
Nevertheless, I'm such a big fan I've been to every talk he's ever given.
https://www.flickr.com/photos/easyflow/3377137372/in/photolist-69qHhq-5JUiYP-55ZfsE-dYmwEQ-5Ca1VD-7zq7En-kVv8dK-mqM9Jp-5J3uv9-f4JB8M-qZznd-f4MRgN-f4xAET-bpDYeX-GroML-7qoFXr-55nSfk-rbJwH-6RFZt1-6qnVXy-jtkLG-cEGq9-4xp87D-eeUgzz-c7QHf-6qk9JT-7PjaWF-4gf1tv-7sK9B3-4VtxzW-6qvWgT-8UB4U-8t9NNr-bDvQY-972WQq-6Fkgen-4RSnyY-8T7px8-6rWXPz-6rWU3n-5fgGGe-Hq1J7-cvqi-7Hs86U-9Vo8SK-gzpzde-666Ch9-4CzyT6-3hx5nr-dReBgT
Steve
This talk is about creating better websites by bringing designers & developers closer together
Steve
Perhaps your experience with bringing designers & developers is a bit like this - but without the pillows.
Certainly, navigating between design and implementation often feels like a fixed sum game.
One side’s win is the other side’s loss.
https://www.flickr.com/photos/timdorr/4396870234/in/photolist-7Gx7ku-7GtaDx-7Gx4Ub-7Gta8t-7GtadX-7GvYZ1-3nArNu-3nArUy-3nApNY-3nvYmr-3nAq8N-3nApG1-3nAq2q-3nvYJg-3nw1xc-3nAtnq-3nvVBg-3nAtad-3nAtUo-3nw1jX-3nvZti-3nvXm6-3nAr7d-3nAqfL-3nAuPb-3nAsRf-3nAssL-3nvZHt-3nAroy-3nArvb-3nAqUE-3nAph1-3nvXf4-3nArGG-3nvVb8-3nAscS-3nAtAW-3nAueq-3nvYwD-3nArZN-3nAr27-3nAqs5-oM1oiq-bCU3k4-3sZr4-682gYi-6eDdv3-qSGcRS-aFFtxX-7QzWQc
Mark
But really, they’re both after the same thing: creating a great user experience!
Design & development ARE connected, but they’re more like the yin and the yang.
They aren't opposing forces, but instead complement each other.
Users want an experience that is rich and fast. The trick is figuring out how to deliver that.
Similar to DevOps from Velocity.
https://www.flickr.com/photos/easyflow/3377137372/in/photolist-69qHhq-5JUiYP-55ZfsE-dYmwEQ-5Ca1VD-7zq7En-kVv8dK-mqM9Jp-5J3uv9-f4JB8M-qZznd-f4MRgN-f4xAET-bpDYeX-GroML-7qoFXr-55nSfk-rbJwH-6RFZt1-6qnVXy-jtkLG-cEGq9-4xp87D-eeUgzz-c7QHf-6qk9JT-7PjaWF-4gf1tv-7sK9B3-4VtxzW-6qvWgT-8UB4U-8t9NNr-bDvQY-972WQq-6Fkgen-4RSnyY-8T7px8-6rWXPz-6rWU3n-5fgGGe-Hq1J7-cvqi-7Hs86U-9Vo8SK-gzpzde-666Ch9-4CzyT6-3hx5nr-dReBgT
A lot of the thinking behind Design+Performance came from long discussions with my business partner Mark Zeman.
He has a lengthy career as a designer and creative director, but sadly can’t be here today.
Mark
So I’m going to borrow from Yemeni Perez-Cruz to represent designers.
Mark
Mark
Mark
two minutes is slow
Steve
but we know good performance is key to great user experiences
“if we’re able to achieve a similar performance boost across our other top landing pages, we’ll drive in excess of 60 million yearly Firefox downloads.”
This was a ~5 second speed up.
Time measurements from real users.
Steve
and now Google is even demanding that your websites be quick if you don’t want to get demoted in their search results
HOW CAN WE CREATE FAST WEBAPPS?
BOTH
so where are we?
https://www.flickr.com/photos/jronaldlee/5775587577/in/photolist-9NnoYa-nYYp6g-63bGJj-KrzjB-6nYgX1-8KY39y-kz3M7y-fo68C6-5onBza-apBT72-6g9eSA-9WNvKw-4Gb2FP-2V7jsj-6G7Ynq-2tbdKU-9Kip9s-4TL5Sc-iJQYR-gi6ri6-pfx24Z-BgDwR-9NgMy1-of8g8U-49queL-atRJTH-ax64Nq-fSUV1Q-4qvBPj-4Se4NE-aegPJ4-ptxVJE-ptM5zP-ptMNBV-q95ZVa-kcfpje-mPZDqk-7FPG6G-cqvvXs-rwFCJA-bVYoNj-6McJox-CXYYb-5bMxiG-49mrhe-6q5uNW-7DpdiH-6MgWby-5n89ro-dVXS9w
Mark
It is possible to bring design and performance closer together. Here’s how…
https://www.flickr.com/photos/easyflow/3377137372/in/photolist-69qHhq-5JUiYP-55ZfsE-dYmwEQ-5Ca1VD-7zq7En-kVv8dK-mqM9Jp-5J3uv9-f4JB8M-qZznd-f4MRgN-f4xAET-bpDYeX-GroML-7qoFXr-55nSfk-rbJwH-6RFZt1-6qnVXy-jtkLG-cEGq9-4xp87D-eeUgzz-c7QHf-6qk9JT-7PjaWF-4gf1tv-7sK9B3-4VtxzW-6qvWgT-8UB4U-8t9NNr-bDvQY-972WQq-6Fkgen-4RSnyY-8T7px8-6rWXPz-6rWU3n-5fgGGe-Hq1J7-cvqi-7Hs86U-9Vo8SK-gzpzde-666Ch9-4CzyT6-3hx5nr-dReBgT
Mark
None of this works unless you have the right people in the room the whole way through the process.
It’s hard to create this relationship halfway through the process
bring designers & developers together from the get go
Mark
With everyone gathered together, discuss project goals and capture guiding principles.
Make sure performance is addressed.
https://www.flickr.com/photos/nihaogirl/4922776916/in/photolist-ndeSfc-51eh43-51a5LR-74FetH-4TeuNB-df5nYf-5Vo2Wn-5Nmjzn-51a5zV-51egkE-51a546-8v1w55-5t8PLi-9Zxguz-7wK1Le-6RAgsL
Here is an example of a principle from the design of a news website. The research showed that users consume news in small quick chunks and so it was more important that it loaded extremely fast than be visually rich with lots of brand assets. People are waiting at the bus stop and they have less than a minute to scan a few articles on their phone - it has to be fast.
There is even a specific mention for when the site should be loaded and that was used as a performance budget.
Mark
Here is an example of a principle from the design of a news website. The research showed that users consume news in small quick chunks and so it was more important that it loaded extremely fast than be visually rich with lots of brand assets. People are waiting at the bus stop and they have less than a minute to scan a few articles on their phone - it has to be fast.
There is even a specific mention for when the site should be loaded and that was used as a performance budget.
Mark
It means all the knowledge is in one room, everybody is working on the prototype from day one. Designers are not working in photoshop to create full layouts - they are creating individual assets that go into a prototype. Developers are working with existing data sources and manipulating real content. Researchers are capturing users needs and gauging reactions to each prototype. Team members have a specialisation but are expected to contribute to all aspects of the project.
Everybody is contributing to the prototype and the conversions are all embodied in one place. So every one has a shared vision and can see how well the project principles and performance principles are being met.
Here's a moment that I love - the client is in the room, the developer is experimenting with changing layout and the designer is consulting on the various options they are playing with. All the discussion revolves around the prototype on screen.
And by having a prototype from day one we can immediately assess it's performance and ensure it's delivering the user experience we need.
But one of the challenges with performance is that it is invisible. How do we monitor and make visible the performance all the way through the process - for everybody, not just this small interdisciplinary team, but also the wider organisation we need to have conversations with.
Mark
But one of the challenges with performance is that it is invisible. How do we monitor and make visible the performance all the way through the process - for everybody, not just this small interdisciplinary team, but also the wider organisation we need to have conversations with.
https://www.flickr.com/photos/josterpi/3174097491/in/photolist-5Qu5AP-h4vYQc-qDkDsE-6tDQ53-ap4pYT-6VrZjk-md5yR5-5PondA-5PVcKC-bvavRn-bxsk7Z-QudsT-6S1ivp-9hwNYa-8UjqcP-ap7amu-9zgR8a-qf1yJ9-qgz457-4JXfm4-99eAKF-6cyvEr-mFUttz-e2FfcF-37ddmA-wBwq6-63iZnr-wBwiC-9XMHpn-ph8ANF-9XQzJE-ZsAKM-iyQpBa-7jgbx4-6QJSTZ-7jk5tw-wBwgS-wBwca-bA44J-8Mdwca-qMZeNs-7P5RjE-6o8M7d-9hP5RB-4zySd-aAqBn3-NGjcd-cH8cQU-8USCg9-8KMjFj
Mark
Steve
But what exactly should we be measuring?
WHAT SHOULD WE MEASURE?
https://www.flickr.com/photos/lisanorwood/2861328403/in/photolist-5mR4fk-MjCWp-bX7FrJ-dMih5Z-8Sqpe4-qUk5B6-cMqP6L-ej4mk4-bv2Koj-gV3NF9-4LYHJC-4LYHxd-4LUxYa-4LUxKV-4LUxCH-4LYGEw-4LYGvG-4LUxdP-4LUx66-4LUwR8-4LUwCn-4LUwwz-j3LVA-6CMMSn-dcbdKE-tTwVoG-g7Ai1f-p544s2-79Kh94-aNWUrp-CsP1L-e38a5p-e38a4k-CEFSU-9xr1yb-9xqZZu-9MyzJY-3fcqzs-fpTzg2-8qAgFe-ad22ie-7xWK7u-bugShD-683bvG-8vYEtm-696zM4-bunmey-riw5sJ-rixdyo-qD6VvN
SHORT HISTORY OF HOW PERF METRICS HAVE EVOLVED
YtseJam Photography, "Going nowhere fast", http://www.flickr.com/photos/thatguyfromcchs08/2300190277/
This is just the HTML document!!! Just 1 of 50 requests!!!
http://stockcharts.com/commentary/archives/cww20021222h.html
This is just the HTML document!!! Just 1 of 50 requests!!!
As of 2011 their HTML document took 500 ms
We need metrics that focus on what the user sees!
https://www.flickr.com/photos/cataniamichele/2855661699/sizes/l
Roundtrip 2003
Episodes 2008
Boomerang 2010
FOUNDED BY GOOGLE & MICROSOFT
GAVE US .navigationStart
MORE ACCURATE WAY OF MEASURING WINDOW.ONLOAD
BUT PAGES ALSO GOT MORE COMPLEX
https://www.flickr.com/photos/zamboniandrea/170324255/
BUT PAGES ALSO GOT MORE COMPLEX
We know page load time is NOT necessarily correlate to UX.
examples of how onload does NOT correlate to UX
Amazon: http://www.webpagetest.org/result/150420_GV_E3/
Gmail: http://www.webpagetest.org/result/150420_S9_704a92a60b0b134daec3d42d649c3010/
THESE CANNED METRICS DON'T NECESSARILY CAPTURE THE UX
IF YOU'RE USING A METRIC THAT PUTS THE SAME VALUE ON ALL THE CONTENT IN THE VIEWPORT, THAT'S NOT A GOOD METRIC.
https://www.flickr.com/photos/packethunter/8606781566/in/photolist-e7y1iC-8Wjrr-6oNLSt-4KFuB3-4MUQMb-71M5Kn-6fNAWB-6fSGR1-6fSPhy-6fNCoV-6fNCN2-6fNCmz-c1ygCh-7Wp7WQ-6fSNWm-6fNCWn-6fNCRv-6fNEVF-6fSGWA-7WkQ9r-ifakh-fLN1RN-qkDua9-poHA73-qkDu1m-qkwJbZ-poHA8W-6fSSeJ-rYNC5M-rnzhum-9PXcX-6pZMty-ckNUdq-ne49L-bLpxWD-8rfW2a-7Pr24Z-6KykJG-64zPz9-6Y4MrR-4cj1Ro-6bbByr-6Y4KWP-22FRv7-6cEwfU-4MVc5m-nu1N9m-n1Beux-9wC6Kj-6Yc7kg
https://www.flickr.com/photos/mindahaas/5597392298/in/photolist-9wC6HL-BnjNV-6fNFrZ-6fSPFQ-6fNDEP-6fSMGu-6fSMDJ-8oFeHX-rAYd6m-sgpoM9-sgvPUv-sgpzGf-sxNNb3-sgwvyF-rAYxou-rBaRoK-sgpFPW-svFwuJ-sxYxwr-sxZ68n-sgpo1Q-sgvTYH-sxYwcc-sgo4cs-svFMdS-sgwty8-sxWUGc-sxYmhH-svFz5y-sxNATU-rBb16K-rBaAHx-sxWu1P-sxYuTv-rBaXM6-sxNzBW-sgnXhG-sxP2zh-rBb5kB-4ooSus-6fNEBM-6fNEmt-6fSQGQ-6fSPPC-7Wp5uE-6fSHdG-6fSH17-7WpaSj-6fNCaP-6fNBFH
Anyone surprised by that?
And yet, that’s what most websites are using them to measure their performance.
https://www.flickr.com/photos/15609463@N03/14752624612/in/photolist-otD4jL-4p9GRo-ftht9s-ft36pK-fthrfU-ft33tD-fthnJA-fthngq-ft2ZcH-fthkhh-ft2XPD-ft2XmK-fthhH9-ft2Vfv-9UMno7-8tbXHQ-JGdGp-bAnD7e-cY94qm-9Xxwuz-5umsgU-4J4FCc-meHP44-8xVrHW-ft33Wr-ft31aD-5t933c-m6NKfZ-m1fHii-a7BGxp-kXqsW-5KGU2v-y4og12-fthsLu-fthqr5-ft34mg-7zRuBJ-b1nqj4-4GFhqH-66T7qj-kdYcpH-k9fBfA-xi8kRn-a5ZQnK-bhbVMg-58vKE3-kXqqh-8JD5Lb-5MivKh-4gGAGH
INSTEAD WE NEED METRICS THAT TRACK THE CONTENT THAT'S CRITICAL FOR A GOOD UX
https://www.flickr.com/photos/kk/6863172432/in/photolist-bsty4b-3HDYJE-wiSVMX-eVWzMJ-9ftJBe-kYWQ8F-aucUmh-diNSS9-qZg4Rp-kjFung-dmuJKm-pH4iVp-bnTdAq-9LFXXN-ba67YV-dhth5h-oaaZKo-nd9Fs1-29RVSQ-pJGAjW-i29xbH-ajNXL9-o8WqV6-uqMyAg-fdPuAo-srZ5Yr-nwMJDC-jibyGv-hBcuis-vKiMxj-pu9xhj-rwJSDL-dnDq8k-swkmVC-o151uM-hBbGwi-gfwits-cHtV9-61nXN5-bAZ5za-pU4HhE-kBkvPH-pn47sx-hTFhB9-mnGW1V-o8wD5y-rRvX4y-9B1Qwy-dQuEdE-rDsEGb
not sure copyright: http://www.shareyouressays.com/117259/customs-are-an-important-source-of-hindu-law-essay
not sure copyright: http://www.shareyouressays.com/117259/customs-are-an-important-source-of-hindu-law-essay
not sure copyright: http://www.shareyouressays.com/117259/customs-are-an-important-source-of-hindu-law-essay
not sure copyright: http://www.shareyouressays.com/117259/customs-are-an-important-source-of-hindu-law-essay
15:00
ONE OF THE FIRST AND MOST POPULAR CUSTOM METRICS
Steve
Stylesheets DO block inline scripts from executing. (JS might check styling)
Stylesheets DO block inline scripts from executing. (JS might check styling)
Stylesheets DO block inline scripts from executing. (JS might check styling)
STYLESHEET WILL BLOCK IMAGE FROM RENDERING BUT IMAGE ONLOAD FIRES
SCRIPT AFTER IMG TAG WON'T EXECUTE UNTIL IMG IS RENDERED
Stylesheets DO block inline scripts from executing. (JS might check styling)
SCRIPT AFTER IMG TAG WON'T EXECUTE UNTIL IMG IS RENDERED
Stylesheets DO block inline scripts from executing. (JS might check styling)
THIS IS A PRETTY BIG DEAL
Steve
http://www.webpagetest.org/video/compare.php?tests=150422_H8_AG3-r%3A4-c%3A0&thumbSize=200&ival=100&end=visual
Steve
How do we know when the image rendered? Filmstrips!!
Steve
too early
It's not wrong, it's just answering a different question: "When did it finish downloading?"
too early
too early
too early
The only that works!
Those previous tests covered other slow (blocking) assets.
What if the image itself is slow?
NOW WE CAN CAPTURE PERFORMANCE METRICS ON WHAT USERS SEE
MANY PERFORMANCE METRICS SERVICES AUTOMATICALLY SHOW USER TIMING MARKS & MEASURES
We need metrics that focus on what the user sees!
https://www.flickr.com/photos/cataniamichele/2855661699/sizes/l
Mark
NONE OF THE CANNED METRICS DO THE JOB
GIVE A FALSE SENSE OF SECURITY
https://www.flickr.com/photos/packethunter/8606781566/in/photolist-e7y1iC-8Wjrr-6oNLSt-4KFuB3-4MUQMb-71M5Kn-6fNAWB-6fSGR1-6fSPhy-6fNCoV-6fNCN2-6fNCmz-c1ygCh-7Wp7WQ-6fSNWm-6fNCWn-6fNCRv-6fNEVF-6fSGWA-7WkQ9r-ifakh-fLN1RN-qkDua9-poHA73-qkDu1m-qkwJbZ-poHA8W-6fSSeJ-rYNC5M-rnzhum-9PXcX-6pZMty-ckNUdq-ne49L-bLpxWD-8rfW2a-7Pr24Z-6KykJG-64zPz9-6Y4MrR-4cj1Ro-6bbByr-6Y4KWP-22FRv7-6cEwfU-4MVc5m-nu1N9m-n1Beux-9wC6Kj-6Yc7kg
https://www.flickr.com/photos/mindahaas/5597392298/in/photolist-9wC6HL-BnjNV-6fNFrZ-6fSPFQ-6fNDEP-6fSMGu-6fSMDJ-8oFeHX-rAYd6m-sgpoM9-sgvPUv-sgpzGf-sxNNb3-sgwvyF-rAYxou-rBaRoK-sgpFPW-svFwuJ-sxYxwr-sxZ68n-sgpo1Q-sgvTYH-sxYwcc-sgo4cs-svFMdS-sgwty8-sxWUGc-sxYmhH-svFz5y-sxNATU-rBb16K-rBaAHx-sxWu1P-sxYuTv-rBaXM6-sxNzBW-sgnXhG-sxP2zh-rBb5kB-4ooSus-6fNEBM-6fNEmt-6fSQGQ-6fSPPC-7Wp5uE-6fSHdG-6fSH17-7WpaSj-6fNCaP-6fNBFH
not sure copyright: http://www.shareyouressays.com/117259/customs-are-an-important-source-of-hindu-law-essay
15:00
INSTEAD WE NEED METRICS THAT TRACK THE CONTENT THAT'S CRITICAL FOR A GOOD UX
https://www.flickr.com/photos/kk/6863172432/in/photolist-bsty4b-3HDYJE-wiSVMX-eVWzMJ-9ftJBe-kYWQ8F-aucUmh-diNSS9-qZg4Rp-kjFung-dmuJKm-pH4iVp-bnTdAq-9LFXXN-ba67YV-dhth5h-oaaZKo-nd9Fs1-29RVSQ-pJGAjW-i29xbH-ajNXL9-o8WqV6-uqMyAg-fdPuAo-srZ5Yr-nwMJDC-jibyGv-hBcuis-vKiMxj-pu9xhj-rwJSDL-dnDq8k-swkmVC-o151uM-hBbGwi-gfwits-cHtV9-61nXN5-bAZ5za-pU4HhE-kBkvPH-pn47sx-hTFhB9-mnGW1V-o8wD5y-rRvX4y-9B1Qwy-dQuEdE-rDsEGb
"thank you" by nj dodge: http://flickr.com/photos/nj_dodge/187190601/
Verrazano-Narrows Bridge