How I test site speed changes using Chrome's local overrides (2021)
1–10 of 32 posts
Re: How I test site speed changes using Chrome's local overrides (2021)
#2[flagged]
Re: How I test site speed changes using Chrome's local overrides (2021)
#3[flagged]
Love testing with chrome personally, all the extensions make it so easy to use
Re: How I test site speed changes using Chrome's local overrides (2021)
#4I have coworkers who only use 2 of chromes debugging tools: the console and the network tab. They dont know about breakpoints, mapped typescript/react files, or local overrides. Every time they come to me with some issue they're facing, I have them set up breakpoints first before we do anything. Usually that's all that we need to do, and we figure out the problem in about 5mins
Re: How I test site speed changes using Chrome's local overrides (2021)
#5[flagged]
This is good advice for everyday browsing, but please test your web apps in all browsers, including Chrome.
Re: How I test site speed changes using Chrome's local overrides (2021)
#6[flagged]
…does Firefox have this? I use it because Edge’s dev tools lock up on my work machine, if it does it would help a lot.
Re: How I test site speed changes using Chrome's local overrides (2021)
#7[flagged]
…does Firefox have this? I use it because Edge’s dev tools lock up on my work machine, if it does it would help a lot.
Afaik not directly, but you can use for example Charles to intercept request and replace network requests.
Re: How I test site speed changes using Chrome's local overrides (2021)
#8After wading through the mumbojumbo like lcp, fid, cls et al. I have learned there are anti flicker scripts.... oh man, brave new world.
Re: How I test site speed changes using Chrome's local overrides (2021)
#9>It works by saving a copy of the page you're working on (or any other resource, like a JavaScript or CSS file), letting you edit that, and then serving that file instead of the live version.
1. You can already set up a local host on your machine to run tests. I thought that was standard practice.
2. I'm glad browsers are offering a similar solution which is easier to set up and useful for front end work. I just checked to see if Firefox has similar functionality, and it seems they support diffs for CSS only, but there is an add-on called Resource Override that appears to have similar functionality.
Re: How I test site speed changes using Chrome's local overrides (2021)
#10I have coworkers who only use 2 of chromes debugging tools: the console and the network tab. They dont know about breakpoints, mapped typescript/react files, or local overrides. Every time they come to me with some issue they're facing, I have them set up breakpoints first before we do anything. Usually that's all that we need to do, and we figure out the problem in about 5mins
On a tangent, it is weird sometimes that people not always pick the right tool for the job, even if the effort is small and the results pay off immediately. Like slicing carrots using a potato knife or even a table knife.