lighthouse VS Turbolinks

Check Performance: Use tools like Google Lighthouse or PageSpeed Insights to monitor your site's speed. We’ve even built this pretty cool performance tool, Performance Insights.

[1] https://github.com/GoogleChrome/lighthouse/blob/HEAD/docs/user-flows.md

PageSpeed uses Lighthouse under the hood, so what is the deal here? Googling this tells you that PageSpeed also includes some real-world data and so on, but this does not address the problem at stake. After some lengthy deep dives into the issue, we found the reason for it here:

This doesn’t come out of the box, but still possible on GCP by combining puppeteer with lighthouse (checkout puppeteer documentation for this https://github.com/GoogleChrome/lighthouse/blob/main/docs/puppeteer.md).

Google Lighthouse

I wrote a JavaScript version of this using Intl: https://github.com/GoogleChrome/lighthouse/blob/9baac0ae9da7...

Google Lighthouse - Node CLI package that runs various checks on your application, but also includes accessibility testing as well!

Google Core Vitals now represent the most important metrics to focus on when it comes to technical SEO. Google Core Vitals are a set of standardized metrics that Google uses to evaluate the user experience offered by a web page and assign it a technical SEO grade. Several tools exist to measure and report technical SEO performance, but the most reliable is Google Lighthouse.

- referred to https://github.com/GoogleChrome/lighthouse/issues/6512 but didnt see network.disable error - added staticdistdir as per https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/configuration.md,

There has been discussion about adding a visual indicator to make the mode more obvious, but it has not made it into Chrome devtools!

First off, name calling.

Second, I actually thought the same as you but digging into the history I don't see any records of a public release of Hotwire until December of 2020, and HTMX was public in May of that year.

I'm pretty sure what I was thinking of was actually Turbolinks:

https://github.com/turbolinks/turbolinks

You can find out more about Turbolinks on the GitHub repository (https://github.com/turbolinks/turbolinks). The repo is now archived, because it’s was integrated in a framework called Turbo, but the functionality is the same.

I know it’s been replaced by Turbo but you can copy Turbolink’s progress bar: https://github.com/turbolinks/turbolinks/blob/master/src/progress_bar.ts. It uses an animation that “trickles” based on response time.

// app/javascript/src/helpers/price.js // Turbolinks are enabled by default in Rails, // we need to process our script on every page load // https://github.com/turbolinks/turbolinks#full-list-of-events document.addEventListener("turbolinks:ready", () => { // Get language from html tag const lang = document.documentElement.lang; // Find all span tags with data-localize="price" const pricesOnPage = document.querySelectorAll("[data-localize=\"price\"]"); if (pricesOnPage.length > 0) { // Iterate all price span tags [...pricesOnPage].forEach(priceOnPage => { // Modify text in span tag according to current language priceOnPage.textContent = priceOnPage.textContent.toLocaleString( lang, { style: "currency", currency: "USD" } ); }) } });

Because it feels fast, it actually is not. It is using Turbolinks. https://github.com/turbolinks/turbolinks And Laravel Wrapper for Turbolinks: https://github.com/frenzyapp/turbolinks

https://github.com/turbolinks/turbolinks

It provides a smooth UX by fetching next page's HTML in background, then replace the DOM by compareing the diff in HTML. So you won't see a blank page while navigating between pages.

If you have used Turbolinks in the past, you will feel right at home with Turbo Drive. At its core, some JS code intercepts JavaScript events on your application, loads HTML asynchronously, and replaces parts of your HTML markup.

When the Turbolinks technology first came out in Rails 4, some people did not understand what it was really about. I happened to get it right away only because I personally implemented my own version of Turbo Drive for one of my client projects before Turbolinks was released (around 2012), so I really appreciated Turbolinks when it was released. With the latest updates in Rails 7, the Turbolinks technology has been renamed to Turbo Drive (now part of Hotwire) since it not only accelerates hyperlinks anymore, but also form submissions too.

Turbolinks, a great tool to make navigating your web application faster, is no longer under active development. It has been superseded by a new framework called Turbo, which is part of the Hotwire umbrella.