Understand website pressure rankings

Learn why a website contributes more local crawl load than others.

Last checked 21 August 2026

Website Pressure ranks websites by how much local page-monitoring demand they create. It is an operational ranking, not an SEO score and not a measure of website quality.

Only websites with at least one enabled monitored page appear. A paused website remains listed and shows a Paused badge because its enabled pages and stored data still describe its configured pressure.

Read each column

Pages: enabled monitored pages. Disabled pages are excluded.
Queued: enabled pages currently waiting or active in the page-check queue.
Schedule: the shared interval if all enabled pages match, or Mixed when they differ.
Checks / day: the estimated total from every enabled page's interval.
Avg check: the whole-number average of available latest check durations. Not yet means no duration is available.
HTML: total stored gzipped HTML across enabled pages. This is not total transferred page weight.
Pressure: the computed ranking score.

Below the website name, flags identify queued, slow, large-HTML, frequent-check, and many-page contributors.

The exact pressure formula

TechDash calculates:

Pressure = enabled pages + (queued pages × 8) + (slow pages × 6) + (large pages × 4) + round(checks per day / 24)

A slow page has a latest duration of at least 15 seconds. A large page has at least 250,000 bytes of stored gzipped HTML. A site is flagged for frequent checks at 200 estimated checks per day and for many pages at 40 enabled pages.

Queued pages receive the largest per-page weight because they represent work currently occupying or waiting for crawl capacity. Slow pages come next because they hold a worker longer. Large captures add processing and storage demand. Page count and frequency account for ongoing baseline work.

The final table is sorted from highest Pressure to lowest. Equal scores are sorted by website name.

How checks per day is estimated

The estimate assumes the configured interval can run continuously:

Every 15 minutes: 96 checks per day per page
Hourly: 24
Daily: 1
Weekly: approximately one seventh per day

TechDash sums the fractional daily rates for all enabled pages, then rounds the site total once. One weekly page contributes approximately 0.14 checks per day and displays 0 when it is the site's only page. Four weekly pages contribute approximately 0.57 and display 1. Seven weekly pages contribute 1 and display 1. This is an operational approximation rather than a guaranteed run count. Battery mode, a locked screen, sleep, offline periods, queue delays, pauses, and application downtime can reduce actual checks.

Understand flags and colors

A site can carry several flags at once. Any queued page adds the queued flag. Any page over the slow or large threshold adds its corresponding flag.

Pressure color is red when the score is at least 80 or the site has at least three flags. It is amber when the score is at least 25 or any flag exists. Otherwise it is green.

Each other column has its own thresholds. For example, Pages becomes amber at 20 and red at 40, while Checks / day becomes amber at 100 and red at 200. The Schedule value is amber for Every 15 minutes or Mixed, but green for Hourly, Daily, or Weekly. Mixed is highlighted because it deserves inspection, not because mixed schedules are inherently wrong.

Use the ranking to reduce load

Start with the first row, then identify the dominant contributor:

High Queued: watch whether the page-check queue drains.
High Checks / day: move low-priority pages to a longer interval.
High Pages: disable or remove URLs that do not need continuous monitoring.
High Avg check: investigate destination speed, access challenges, redirects, and rendering.
High HTML: inspect unexpectedly large or data-heavy output.

Open the linked website to review its monitored pages. Make changes based on monitoring value, not solely to lower Pressure. A high-pressure site can be an intentional and supportable configuration when the queue drains and the computer remains responsive.