Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

High-Performance Web Platform: Real-World Problems and Solutions

Download

Right click “Save as…”

Slides (view online)
+ My Schedule- My Schedule

See how to tackle real-world web platform performance problems in modern websites and web applications. This session starts with a foundational understanding of the web platform and then shifts to a fast-paced, demo-packed set of problem/solution pairs built from industry-standard performance guidance. Learn how modifications to your HTML, CSS, and JavaScript can significantly improve how your code takes advantage of device resources and improves your user experience.

For more information, check out these courses on Microsoft Virtual Academy:

Follow the Discussion

  • One of the best sessions tjis year!

  • Tobin TitusTobinT Stay Classy, San Diego
    Thank you, Daniel! I appreciate that you watched the talk and provided feedback. Enjoy the conference!
  • I can't download the videos.

  • Tobin TitusTobinT Stay Classy, San Diego

    @Luiz I can download them. Are you still having a problem?

  • Very, very well done.  Tobin's interest and passion came through in this session.  What elevated this presentation was not only the practical and informational slides, but Tobin's relaxed and free flowing delivery.  I felt the entire room was engaged and hanging on every word.  One the highlights of Day 2 for me.  Great job !!

  • Tobin TitusTobinT Stay Classy, San Diego

    @jmichener,

    Thank you very much. I hope to deliver more content like this in the future. Your feedback is very helpful.

  • I was disappointed with the content in this session.  I guess I was expecting to see examples of poor, slow, javascript code followed by better, faster javascript code.  I think this is a 100 level course as it was mostly conceptual.  Those of us that have been developing web apps for years know that we should right-size our images and put javascript at the bottom of the page when we can.

  • Tobin TitusTobinT Stay Classy, San Diego

    Thanks for the feedback, Rob. I'm sorry you were disappointed.

    I agree that many people do understand things like "right size images": This has been preached by Steve Souders for years so some really should understand that. However, the data shows that many developers either do not know, or do not necessarily understand the impact -- particularly in a mobile-first world where this becomes even more important. I expected for some experts to get little out of the advice itself, and more out of the importance of that advice -- seeing the impact of these decisions on memory and CPU / GPU utilization.  For instance, even looking at my own blog as well as yours, there are a lot of anti-patterns for performance that I have opted to ignore (again, as I'm sure you have) :  tons of script throughout the page  head / body, multiple registrations for document ready, antiquated if IE checks, etc. But knowing the impact makes us all more inclined to make changes.

    Your point is very valid, though, and I'll perhaps aim a little higher next year should I agree to do another session. What would you prefer to see instead? What would be useful to you, at an expert level? Thanks again for the feedback. Very useful.

  • Johan Peterssondodavinkeln Developer in LA

    Great talk Tobin! I have some questions though.

    We do often use lazy loading of images, i.e. just loading images when they are visible in the viewport, we're also loading the images in different sizes depending on the width of the viewport. All this to save the user from downloading unnecessary data. But we're also generating the images in twice the size but much more compressed, so they are much smaller in file size but have larger dimensions. By doing this, they look much better on high DPI displays.

    Now to my questions, how will this affect the performance, when it comes to memory, CPU, decoding and so on, especially on low-end devices?
    You're mentioning large images, but what about large heavily compressed images? Does the encoding take longer time and consume more memory? Is the key the dimensions here, or does compression and files size matter too?

    I have done some messuring in the F12 Tools, but can't really see any difference when switching between "right" size and double size but more compressed images.

Remove this comment

Remove this thread

close

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.