Websites don't always work as expected. In this course, Debugging Your Website with Fiddler and Chrome DevTools, you will learn foundational knowledge necessary to debug website problems. First, you will learn diagnostic techniques. Next, you will discover how to modify requests and responses. Finally, you will explore how to decrypt HTTPS. When you’re finished with this course, you will have the skills and knowledge of Fiddler and Chrome DevTools needed to debug your website issues.
Introduction to Fiddler Hello. This is Robert Boedigheimer. Welcome to this course on Debugging Your Website with Fiddler and Chrome DevTools. In this first module, we're going to look at an introduction to Fiddler.
Diagnosing and Resolving CSS Issues In this module, we're going to look at Diagnosing and Resolving CSS Issues. So it's very common on large web pages or websites to have a lot of various CSS files, and it's often hard to understand when you look at the page exactly which rules were in play with cascading and specificity and other issues that can impact how your CSS looks. We're going to see how to troubleshoot those issues using Chrome DevTools.
Diagnosing and Resolving Performance Issues In this module, we're going to look at Diagnosing and Resolving Performance Issues. Our first step is going to be to understand basic performance rules. The first is make fewer HTTP requests. We'll talk a little later about why this might be less important if you're using HTTP/2, but in general, for a web page, we don't want to make requests that we don't need to make. Next is send as little as possible. Then, send it as infrequently as possible. And lastly, we really want to avoid latency, which is the amount of time it takes from the browser to talk to the server and get a response.
Determining Website Behavior and Potential Issues In this module, we're going to look at Determining Website Behavior and Potential Issues by using both Fiddler and Chrome DevTools to modify or slow down or otherwise change something between the browser and the server to see what kind of impact that might have on the rendering of the page or how it actually behaves.
Solving Real World Problems In this module, we're going to look at Solving Real World Problems, things like who made a given request. So when we look at a page, we see a resource that's requested. We're not sure who made that request. Things like who modified a portion of the page. We're also going to look at how you decrypt HTTPS traffic. So just a lot of different things that come up day to day working with your website. How do you use both Fiddler and Chrome DevTools to help you determine what's going on and what's wrong?