Skip to main content

Search

Welcome to the Lumar Knowledge Base

January 2025 - including Crawl Safeguard and Protect Tests on Health Scores

Andrew Levey
  • Updated

Crawl Safeguard

Release Date: January 31st 2025

To make sure crawls complete quickly and efficiently, we’ve improved visibility into what we’re crawling as we crawl, and added additional crawl safeguards to the Lumar Platform:

  • You can now see a summary of the count of URLs per status code in the last 5 minutes on the crawl progress screen.

  • You can also see a trend of the failure rate per 5 minutes for the last hour, with the overload percentage.

  • In the project settings, you can now set a threshold for the percentage of errors within a fixed timeframe, which will pause the crawl when the rate is exceeded. You’ll see a message on the crawl progress screen to explain that the crawl was paused due to errors, and receive an email so you can investigate and disable the overload protection if required.

Screenshot of the Lumar Analyze crawl progress screen with the response codes and failure rate chart, and the crawl safeguard toggle and failure rate, highlighted.

Note that these settings are not enabled by default at this stage, but can be enabled for any new or existing crawls as required. We'll then look at adding the crawl safeguard settings by default for new projects in the future. In the meantime, you can enable the safeguard settings on the crawl progress screen, or in the Crawl Safeguard option in Advanced Settings in Step 4 of the crawl setup.

Screenshot of the Advanced Settings options in step 4 of the crawl setup, with the Crawl Safeguard options highlighted.

For more details on enabling crawl safeguards, including a list of the status codes flagged as failures, see this article. 

Critical Request Chains Added to Page Details View for Site Speed Projects

Release Date: January 28th 2025

As part of our site speed metrics, URLs are checked for chained critical requests, which can impact First Contentful Paint (FCP) and Largest Contentful Paint (LCP). To help identify issues more effectively, you can now view the details of Critical Request Chains in the audit section of the Page Details view for Site Speed projects.

Once you’ve navigated to the page details view, you’ll find ‘Avoid chaining critical requests’ in the left-hand navigation, depending on whether the audit has passed, failed or given warnings. Once you’ve located the audit, scroll down to view the Critical Request Chains.

Screenshot of the Critical Request Chains detail in the Analyze Page Detail View, with the Audits and the Avoid chaining critical requests audit highlighted.

Protect Tests on Health Scores

Release Date: January 20th 2025

To help you identify issues before new code is published, you can now create tests for health scores in Protect. This means you can now run health score tests on templates, or automatically stop builds if you integrate Protect with your CI/CD pipeline, to check for any site health degradation before changes go live.

Screenshot of step 4 of the Lumar Protect test suite setup, showing the ability to add health scores as tests.