And so, the first prompt I'm going to be using is to use the Chrome Developer Tools MCP to record a performance trace of my website and tell me the three biggest performance issues of that website. And then we're going to identify the issues and tell me what specific URL images are causing the issues. And then we're going to generate helpers to fix the problem. And then we're going to update our performance. And then we're going to verify to make sure everything was done correctly. I'm going to just run through one of these just due to the time. And we'll just take a look, quick look at what the image, what the website looks like right now. You can see that the images are loading very slowly.
And then when we run all our fixes, everything will be much more smooth as we load. And so, let, so, when we're doing this manually, we have to go over to our docs. We have to check out, okay, like, I need to think about how to actually do lazy loading, how to resize my images, how, what kind of quality do I want to have, what's the format I want to have it in. There's a lot of things going into making sure your images and videos are actually optimized the best way possible. Normally, you go into image kits docs and figure out how to do it. But with the Power MCPs and your favorite cursor, IDE, you don't have to do that anymore.
So, I'm going to run one prompt to show you guys how we've done. I got it started a little bit earlier. So, we're just going to run the tool just so you can see what's happening right now. So for context, it's running the first prompt and figuring out what actually is wrong with the broken React e-commerce site. Let me just run through. It opens up the site on its own. It's going to go through and identify all the problems. And so, what we're going to do is hop over to the presentation. And I'm going to highlight a few things. So, typically, as I mentioned, performance is an afterthought. We build our website and we have our images on the page and it's working perfectly. Or so we thought. And we finally refreshed our page and now we're like, oh, what's going on?
Comments