creator @OptyxApp, @____lighthouse CI, third-party-web ; maintainer jpeg-js, @TestingLib, https://xitter.gq/t.co/OQCX2LPfZK ; formerly @google, @ChromeDevTools, @Yahoo
Dallas, TX
Joined April 2011
- Tweets1.2K
- Following362
- Followers1K
- Likes7.4K
Patrick Hulce retweeted
This is essentially fraud. The makers of the software cheat to achieve the impression of improvement. WP sites use the software to improve their page experience ranking. But that is based on Core Web Vitals which cannot be cheated with this mechanism.
Patrick Hulce retweeted
🤩 Great news! You can now export and measure your @ChromeDevTools Recorder user flows with the @RealWebPageTest.
Install the extension and try it out now! bit.ly/wpt-recorder
p.s: Want to create an extension? Sure, here is how goo.gle/recorder-extension
Patrick Hulce retweeted
The @RealWebPageTest has been _cranking_ on this for awhile and it's finally time to share! I could not be more excited to unveil our new Opportunities & Experiments—a way to let you test performance optimizations without touching a single line of code.
blog.webpagetest.org/posts/i…
Patrick Hulce retweeted
Yea.. well.. Dreamweaver had them...
ALT A screenshot of Dreamweaver, highlighting a “Make Nested Template” button, circa 2013.
Patrick Hulce retweeted
I ported Zelda Classic, a 20+ year old C++ Allegro program, to the web:
hoten.cc/blog/porting-zelda-…
Patrick Hulce retweeted
Love this visualization from @patrickhulce showing the average cost and total impact of script execution on Pages.
Hard to help clients understand the #webperf implications of technology decisions.
thirdpartyweb.today/
Patrick Hulce retweeted
Here's a suggestion for a way to contribute to open source projects: put together an unsolicited usability test with yourself as the subject
Make very detailed notes as you try out a tool for the first time, then send a link to your notes to the maintainers
Patrick Hulce retweeted
I made a fake @____lighthouse report for some writing, but after some edits it no longer fit, so posting it here I guess
ALT A Lighthouse report with fake suggestions for improving performance: Minimize main-thread work — 29.5 s; Wait, what? Seriously? — 78 resources found; Are you kidding? — Third-party code blocked the main thread for 2.6 s; Do you want users? — 362 requests • 9,004 KiB; Or did you make this site wrong, as a joke? — 146 long tasks found; Oh, that’s rich — 708 user timings; Is this a site for sloths? — 22 chains found; Did they get TCP to run over Fedex? — 22.9 s; New Record! — 7.81e+11 elements
Patrick Hulce retweeted
um, stolen? what do you mean? they changed hands via a legitimate transaction. it's all recorded on the blockchain, which is 100% secure and immutable and trustless. where did "stolen" come into it? hundreds of people simply decided to transfer their tokens simultaneously
This quoted post is unavailable.
Patrick Hulce retweeted
I think everybody got the memo by now, but the time for third party resources is done for the web; especially if they are close to the critical path. If you continue to need to make 3P requests redirect them through a quick edge function hosted on your favorite CDN
Patrick Hulce retweeted
Github/npm's audit tools are completely broken for build tools. Security "vulnerabilities" like prototype pollution or regex DoS in build tools aren't exploitable except in extremely rare use cases, but cause a huge amount of pointless busywork for downstream maintainers. 😡
Patrick Hulce retweeted
My first article on @ThePracticalDev!
📈 Generating user flow reports using the new @____lighthouse APIs and the ✨ @ChromeDevTools Recorder panel.
#DEVCommunity #WebPeformance
dev.to/charca/getting-starte…
Patrick Hulce retweeted
Proud to have authored this chapter on the state of Third Parties. This year we took a dive into the impact of popular third-party embeds and what they do to your page's performance.
And big thanks to @patrickhulce , @AndyDavies , @simonhearne and @csswizardry for reviewing!
Chapter 6: Third Parties written by @tunetheweb
👥 94% of sites depend on third parties
almanac.httparchive.org/en/2…
Patrick Hulce retweeted
Introducing Lighthouse for user flows: drive your page with a Puppeteer script and have Lighthouse measure and audit performance at every step: web.dev/lighthouse-user-flow…
ALT A Lighthouse user-flow report listing multiple steps of interacting with a page and Lighthouse audit results at each step
Patrick Hulce retweeted
Got some pretty crazy performance data this morning:
We decreased 3rd party scripts by 10% last week which led to 50% faster page load times.
3rd party scripts disproportionately impact overall site performance.
Thanks @SpeedCurve
#webperf
Patrick Hulce retweeted
Lying to @____lighthouse == lying to yourself. Not only are you doing nothing to improve #UX and #SEO, but you're activity preventing yourself from actually seeing what needs improvement. All around loser !
Patrick Hulce retweeted
How does Chrome render pixels on the screen?
Learn all about RenderingNG from @chrishtr:
developer.chrome.com/blog/re…
ALT Illustration to pixels on screen