Version 4.10: PageSpeed.ONE Domain, History, Manual Testing, Custom Times…

In recent days, we have been gradually rolling out release 4.10. It is undoubtedly the largest release we have ever prepared at PageSpeed.ONE.

Besides nearly a hundred thousand changes across almost 1,400 files, we are adding measurement history, the ability to manually initiate synthetic tests, custom measurement times, faster test initiation, and significant changes to our website to our speed monitoring.

Curious for more? Read on.

Release 4.10 is quite a hefty one. Release 4.10 is quite a hefty one.

What's New in Speed Monitoring?

The public website and internal monitoring application are now one entity for us, hence the changelog applies to both parts. But let's focus first on the monitoring application.

Notes Transform into Measurement History

Our long-term goal is to visualize everything happening with your website concerning speed. The new Measurement History (Log) serves this purpose.

Measurement History merges previous notes and newly displayed synthetic measurements into a single view.

What new elements will you see in this view?

New Measurement History table. New Measurement History table.

Let us explain the numbers in the image:

  1. The table shows a list of Measurements and Notes with the ability to switch between these types of content.
  2. Above the table on the right, you can initiate manual synthetic measurement (currently in beta) or add a note.
  3. Each row can be clicked to open a modal window with details of the measurement or note.
  4. System entries are inserted automatically, whereas those marked with the author's name can be edited.
  5. For measurements where we notice a significant change in the Lighthouse score compared to the original state, we add a color label.

In the measurement details, you can view individual Lighthouse measurement details or Lighthouse Diff, for comparison.

Measurement History applies only to PLUS tests.

Manual Testing (Beta)

On the Measurement History page, you can now start manual testing.

You can initiate your own measurement at any time outside of regular measurements. This is useful for testing changes on development versions or after deployment.

Once the measurement is complete (this may take about 15–20 minutes), we will send you an email.

Measurement detail opened from the history page. Measurement detail opened from the history page.

What can be seen in the measurement detail? (See the image above)

  1. The measurement name, which you can choose yourself.
  2. Specific Lighthouse tests and Lighthouse Diff.
  3. The ability to add a note to the graph for this measurement.

This feature is in beta. If you are interested, contact us at info@pagespeed.cz.

More Times for Measurement (Beta)

Typically, we measure only once, ideally at night. This is recommended to filter out backend fluctuations during the day.

However, in some situations, it's useful to have more regular measurement times. We now allow this in beta mode.

More measurement times in Settings. More measurement times in Settings.

You can now add more times in the Test Settings. New test runs will then be visible in all reports, and a new seven-day view will be added to the graphs.

This feature is in beta. If you are interested, contact us at info@pagespeed.cz.

Faster Start (Redirector)

Until now, we were dependent on Google's infrastructure, specifically the PageSpeed Insights API, including finding the final URL for the initiated tests.

The aim of this rather significant project was to speed up the initiation time for all tests. We now have our own tool (we call it the "redirector" – a mix of Czech and English) that looks up the final URL for the addresses you provide.

The result should be a multiple acceleration of test initiation, both free and PLUS tests. Try it yourself.

Updates on Our Public Website

Here, you will find all the updates that we have implemented on the public website with release 4.10.

New Help and All Articles + English

Our web speed help has undergone a significant revolution. This took place on two levels:

  • Technical (we have moved away from the no longer suitable Docusaurus and prepared our own system)
  • Content (all our texts are now also available in English).

PageSpeed.ONE Help after the revolution. PageSpeed.ONE Help after the revolution.

All articles for the blog, knowledge, metrics, monitoring documentation, and this changelog are now found in one place – under the Resources page in the navigation.

Translating texts into English and potentially other languages has become easier for us, and it will now be simpler for us to produce more content.

New Navigation on the Website

The mentioned change also involves a change in navigation across the entire website, which we have redesigned, including the mobile version.

Transition to PageSpeed.ONE Domain

As we have previously announced, our ambition and now everyday reality is to accelerate not only Czech but also foreign websites.

Following the brand change to PageSpeed.ONE, we are now also transitioning to the new domain – https://pagespeed.one/

Transition to PageSpeed.ONE Domain Transition to PageSpeed.ONE Domain.

Henceforth, we no longer use the older domains pagespeed.cz and speedjar.com.

Redirection should cover all possible states, but you may need to update domains in your password managers.

And So On

Since the last release 4.9, we've achieved:

  • Clicking a header anchor automatically copies the URL to your clipboard.
  • We now measure using the new SPS score.
  • We've shortened the time needed to calculate the Watchdog limit, so you now get data faster.
  • A secret tip: if you change the range parameter in the URL of the test suite, you'll get a longer time period.
  • We have moved the database to a more powerful machine and thus sped up the entire app.
  • We've launched the PageSpeed.ONE Awards and added comparisons with winners to the monitoring interface.
  • In Test Suite Settings, we provide better feedback in case of invalid URLs.
  • For PLUS test suites, we now automatically add website categories.
  • Internally, we've switched to Tailwind for CSS.

The team at PageSpeed.ONE is thoroughly enjoying these new features, and we hope they help you speed up your websites too.

Found a bug? Have an idea? Feel free to write to us at info@pagespeed.cz.

Authors: Martin Michálek

Tags:MonitoringChangelog

NextMonitoring v4.9.1