#webpagetest — Public Fediverse posts

“The Decline of WebPageTest After the Catchpoint Era” by @innoweb

🔗 https://www.innoweb.com.au/blog/the-slow-demise-of-webpagetest

> The spirit of openness, clarity, and technical depth that defined it has been overshadowed by commercialisation and integration. I understand how this happens - it’s a familiar story for beloved tools after acquisition - but that doesn’t make it any less disappointing.

#WebPageTest #WebPerf

⚓️ https://nicolas-hoizey.com/links/2026/04/22/the-decline-of-webpagetest-after-the-catchpoint-era/

#Development #Analyses
The slow demise of WebPageTest · How the iconic web performance tool lost its edge https://ilo.im/16cdfy

_____
#Testing #Monitoring #Metrics #WebPerf #WebPageTest #Catchpoint #WebDev #Frontend

“WebPageTest.org is moving to the new UI within the Catchpoint Portal to provide users with enhanced features” in https://docs.catchpoint.com/wptpro/docs/webpagetest-faq

🤣🤦‍♂️🤡

#WebPageTest #Catchpoint #webperf #enshittification

Ok, the roadmap in #WebPageTest #Catchpoint docs says “Add scripting capabilities to scheduled tests for full control” in the “Later (Future Enhancements)” section…

https://docs.catchpoint.com/wptpro/docs/webpagetest-roadmap

As some features like authentication are now only available in scheduled tests, we can't have both authentification and scripts in the same tests… 😭

Basic authentication is in the “Next (Planned for Upcoming Releases)” section of the roadmap, while it was available before…

#webperf #enshittification

I would use @speedcurve if I could.

My client allowed #WebPageTest IPs, much easier for them is seems, than checking HTTP headers from SpeedCurve.

#SpeedCurve

With #WebPageTest before #Catchpoint, we could set the URL for the test, and a script that had access to variables like %ORIGIN% or %URL%

Now, when we activate the script feature in an “Instant Test”, the URL field is disabled, so we can't have reusable scripts… 😭

Oh, and it looks like using scripts is not possible in scheduled tests, I couldn't find it. 😡

#webperf #enshittification

Almost every time I try to connect to #Catchpoint 's #WebPageTest with our paid account, I get a 400 error. 😭

I have to try 5 to 10 times before being able to access the tool and use it…

@grigs do you have similar issues?

This morning I spent some time speeding up my WebPageTest Uncompressed JavaScript bytes per character web performance metric tool and migrated it away from Glitch to https://javascript-bytes-per-character.astray.com/
It calculates something like: "According to this WebPageTest run, https://www.javascript.com/ requires 2,190,868 bytes of JavaScript to show 2,003 characters of text on the page. That's 1,093.8 JavaScript bytes per character."
#webPerf #webPageTest

I’ve been afraid to enable the new UI for #WebPageTest because I wasn't certain I would be able to get back to the old UI.

But I took the leap today hoping I would find an easier way to run experiments blocking domains.

Has anyone else switched to the new UI yet? What are your impressions?

“Discovering Third Party Performance Risks” by @paulcalvano

🔗 https://paulcalvano.com/2024-09-03-discovering-third-party-performance-risks/

> […] a tool called Third Party Explorer, which leverages WebpageTest data to help analyze a third party’s impact on a page load. The idea behind this tool is that some of the insights already collected during a WebPageTest measurement may enable you to prioritize a list of domains to evaluate proactively.

#WebPerf #WebPageTest

⚓️ https://nicolas-hoizey.com/links/2024/09/05/discovering-third-party-performance-risks/

#Development #Techniques
Discovering third party performance risks · How to assess if a third-party script needs further review https://ilo.im/15zzqp

_____
#ThirdParty #ThirdPartyExplorer #WebPageTest #Browser #WebPerf #WebDev #Frontend #JavaScript

In case anyone working on private #webpagetest installs is wondering, it was this func that fails silently (until you add some "curl_error" logging to see that it's timing out...):

https://github.com/catchpoint/WebPageTest/blob/apache/www/common_lib.inc#L2617

(as in, I've locked it down so the WPT server is essentially private)

Options were:
a) add a `local_server` entry to settings.ini ("application" change)
b) add the wpt server's security group to itself as allowed ingress? I guess? (infra change)

I went with a) so the async requests went via 127.0.0.1 instead.

Seems to have worked!

I had to add "fwrite()" calls to soooo many files in the #webpagetest source code to understand what was calling what and why it worked when I hit a URL directly..

1) managed to migrate my stuff to ARM / t4g EC2 instances, so I'll keep an eye on AWS spend to see if it actually helped 🎉
2) finally debugged why videos weren't being created on my private #webpagetest instance - took me an insanely long time to realise that an async php function, calling itself via php curl, was silently timing out, due to using the public dns, which is mega locked down 🤦🏻

Ouch. The PHPStan output for #webpagetest on php8 is scary. Nothing seems to be functioning as expected.. Think I better just back away for the time being, and lock my versions until I want to dive head first into #PHP development

Ah of course. A new month rolls around, ubuntu change their most recent LTS AMI from Focal to Jammy, and my #webpagetest deployments fail 🤦🏻

That'll teach me to use wildcards in the AMI search...

https://cloud-images.ubuntu.com/locator/ec2/

Hiccups in our Web Performance Reports' 'Lighthouse Scores' section resolved! Big thanks to the #WebPageTest engineering team. 😊 #webperf

Fellow #WebPageTest users, any idea why a request would have `dns_start: -1` and `dns_end: -1`?

Could it be because there’s a `preconnect` (in HTTP headers) for this subdomain, so the connection happens before the timing measures start?

#WebPerf

I don't like GitHub bots closing issues that are not resolved… 😞

https://github.com/catchpoint/WebPageTest/issues/1579#issuecomment-1763234442

#WebPageTest

#Development #Reviews
Is Lighthouse a misleading performance tool? · What to expect from Google’s tool for improving web page quality https://ilo.im/147naa

_____
#Metrics #Tools #Google #Lighthouse #WebPageTest #SEO #Accessibility #WebPerformance #WebPerf #WebDevelopment #WebDev #Frontend #PageSpeedInsights #CoreWebVitals #CrUX

I'm really worried about #WebPageTest, right now… 🤨

#WebPerf

⚓️ https://nicolas-hoizey.com/notes/2023/06/14/1/

I no longer see the option to emulate mobile browsers in #webpagetest advanced settings. It used to be under the Chromium tab.

Are other people experiencing the same thing? Or is it just me?

#webperf

https://www.webpagetest.org/

#Development #Reviews
Lighthouse diff + WebPageTest · Google’s web performance auditing tool now has a diff tool https://ilo.im/12u80m

_____
#WebPerformance #WebPerf #DiffTool #Lighthouse #WebPageTest #WebDevelopment #WebDev #Website

@Dariusz_w
🤩 Great to see #WebPerfReport and #WebPageTest in action. ⚡️
Thanks for sharing 😊 and good solution 💡

Today: we finaly have a Pro account on WebPageTest so we'll be able to use all Opportunities & Experiments! 🥳

Also today, in WebPageTest header: "Notice: WebPageTest's user account services are currently experiencing issues." 😭

#WebPageTest #WebPerf

⚓️ https://nicolas-hoizey.com/notes/2023/03/07/1/

#WebPageTest
Anyone have any Info about WebPageTest having technical issues? 😢 I can't get the page to load.

📣[new improve] Now all #webperformance tests in @webperfreport also Run #Lighthouse Audit so you can view the results in the new Lighthouse section from the Full Test of #WebPageTest.⚡️
👉 https://webperformancereport.com
#webperf #seo #pwa #buildinpublic

📣[New Improve] now in ⚡@webperfreport⚡ you can jump directly to the Performance Optimization section on the Full Test in #WebPageTest.
💪 We continue working to deliver the best WebPerformance Report to your inbox. 💪
👉 https://webperformancereport.com/
#webperf #webperformance