Bummer! This is just a preview. You need to be signed in with a Basic account to view the entire video.
How the Web Works7:02 with Dale Sande
Getting a web app from it's host to a user is a series of lightning fast transactions, initiated from the user and executed by the code in our web app. Server and data-center performance is part of the solution, which is out of scope of this course, but once the server replies to the request of the user, let's just say, the less we can send, the better.
SPDY -- The now deprecated project, Google’s next generation Transfer Protocol for web traffic
HTTP/2 -- Official next generation Transfer Protocol, based on SPDY created by Google
HTTP Header Request -- Information passed between the client and server during a web request
Head of Line Blocking -- a web performance limiting issue where a request may be stuck waiting for another request to be completed before it can begin
Load time -- the total time it takes for a web app or site to load
Latency -- An issue related to Head of Line Blocking where time is added to the total download time of a web site waiting to download additional assets
Performance Budget -- The total allowed page weight of your site or app
GZip -- A popular server side compression method
Brotli -- A newer server side compression method developed by Google
Perceived Performance -- A metric for how fast user’s think your site is
First Meaningful Paint -- A perceived performance metric where the user first sees content appear in the client post request
First Available Interaction -- A metric that closely associates with First Meaningful Paint where the user is able to begin interaction with the content of your site/app
You need to sign up for Treehouse in order to download course files.Sign up