setup SpeedTracker on LNUG website

[simonmcmanus]

Speed tracker will let us keep an eye on the time it takes to load the LNUG website and check things like Lighthouse score over time:

https://speedtracker.org/

Once in place we should establish some baselines to ensure we don't slow the site down as we make changes.

[domfarnham]

Hi Simon,

Mind if I work on this one?

Dom

[simonmcmanus]

That would be great, thanks Dom.

On 14 January 2018 at 21:43, Dom Farnham notifications@github.com wrote:

Hi Simon,

Mind if I work on this one?

Dom

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lnug/website/issues/146#issuecomment-357544988, or mute the thread https://github.com/notifications/unsubscribe-auth/AADaLW8OeUzSDUF9lkxtxwfRt5_y1TpUks5tKnUKgaJpZM4QgJom .

-- Simon McManus

DotJS Ltd - Node Consultancy

[domfarnham]

Hi Simon,

I have setup a proof of concept by forking speedtracker to my Github profile and configuring it to test lnug.org.

I have setup 4 profiles: 1) lnug.org(Dulles:Chrome:Cable:Lighthouse) The test is performed from a Chrome browser, on a device located in Dulles, Virgina, over a Cable (5/1Mbps, 28ms RTT) connection.

2) lnug.org(London:Chrome:Cable) The test is performed from a Chrome browser, on a device located in London, over a Cable (5/1Mbps, 28ms RTT) connection.

3) lnug.org(London:Chrome:4G) The test is performed from a Chrome browser, on a device located in London, over a 4G (9Mbps, 170ms RTT) connection.

4) lnug.org(London:Chrome:3G) The test is performed from a Chrome browser, on a device located in London, over a 3G (1.6Mbps/768Kbps, 300ms RTT) connection.

Please note that Lighthouse PWA scores are only scored when the location is set as Dulles, Virginia, and the browser as Chrome. This is a current limitiation with Speedtracker.

All profiles are configured with the same budget parameters but can be tweaked to your liking. Time to First Byte: 600ms First Paint: 3 seconds Fully Loaded: 5 seconds

Please take a look at my speedtracker POC dashboard. https://domfarnham.github.io/speedtracker

To implement this from the LNUG GitHub profile I would need to fork the speedtracker/speedtracker repo to the LNUG profile, add speedtracker-bot as a collaborator on the forked repo and configure the speedtracker profiles. I would also need a suitable email address to use to register for a WebPageTest API key. And a suitable email address you would like Speedtracker alerts sent to whenever performance exceeds any of the above budget thresholds.

Note that currently the 3G tests results are not within the budget thresholds.

Are you happy for me to fork speedtracker to the LNUG profile and proceed with setting up these 4 profiles? Should I use contact@lnug.org as the email address?

Dom

[lnugbot]

Hi Dom,

Good work! Please go ahead and setup on the LNUG github repo. Let me know if you need any assistance/access.

To avoid spamming lots of people its probably best to just add individual emails for the time being. So feel free to add me (mcmanus.simon@gmail.com) and yourself (if you want the notifications). Others can always add themselves later.

Thanks

SImon

On 15 January 2018 at 21:45, Dom Farnham notifications@github.com wrote:

Hi Simon,

I have setup a proof of concept by forking speedtracker to my Github profile and configuring it to test lnug.org.

I have setup 4 profiles:

1.

lnug.org(Dulles:Chrome:Cable:Lighthouse) The test is performed from a Chrome browser, on a device located in Dulles, Virgina, over a Cable (5/1Mbps, 28ms RTT) connection. 2.

lnug.org(London:Chrome:Cable) The test is performed from a Chrome browser, on a device located in London, over a Cable (5/1Mbps, 28ms RTT) connection. 3.

lnug.org(London:Chrome:4G) The test is performed from a Chrome browser, on a device located in London, over a 4G (9Mbps, 170ms RTT) connection. 4.

lnug.org(London:Chrome:3G) The test is performed from a Chrome browser, on a device located in London, over a 3G (1.6Mbps/768Kbps, 300ms RTT) connection.

Please note that Lighthouse PWA scores are only scored when the location is set as Dulles, Virginia, and the browser as Chrome. This is a current limitiation with Speedtracker.

All profiles are configured with the same budget parameters but can be tweaked to your liking. Time to First Byte: 600ms First Paint: 3 seconds Fully Loaded: 5 seconds

Please take a look at my speedtracker POC dashboard. https://domfarnham.github.io/speedtracker

To implement this from the LNUG GitHub profile I would need to fork the speedtracker/speedtracker repo to the LNUG profile, add speedtracker-bot as a collaborator on the forked repo and configure the speedtracker profiles. I would also need a suitable email address to use to register for a WebPageTest API key. And a suitable email address you would like Speedtracker alerts sent to whenever performance exceeds any of the above budget thresholds.

Note that currently the 3G tests results are not within the budget thresholds.

Are you happy for me to fork speedtracker to the LNUG profile and proceed with setting up these 4 profiles? Should I use contact@lnug.org as the email address?

Dom

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lnug/website/issues/146#issuecomment-357796010, or mute the thread https://github.com/notifications/unsubscribe-auth/AKr8E5DEq_WLJiCRouZWmISuyydX27cSks5tK8blgaJpZM4QgJom .

-- Simon McManus

DotJS Ltd - Node Consultancy

[domfarnham]

Hi Simon,

SpeedTacker is now setup on the LNUG github. You can access the dashboard here https://lnug.github.io/speedtracker.

A scheduled test will be performed every 12 hours for each of the 4 profiles.

Currently, you and I will receive notifications whenever a performance metric exceeds one of the configured limits. The recipients list can be modified within the speedtracker.yml file, when needed.

Dom

[simonmcmanus]

thanks @domfarnham