Static meta refresh has a positive delay
ShipReady found a static meta http-equiv=refresh element whose content begins with a positive integer delay.
Why it matters
Timed page changes can be surprising, so a positive refresh delay deserves an intentional product and accessibility review.
How ShipReady detects it
What it inspects
On a successful, untruncated HTTP 200 page, ShipReady inspects static meta elements with a quoted http-equiv=refresh attribute and reads the start of their content value.
What triggers a finding
The rule triggers when the content value begins with a positive integer. A zero-delay refresh, a missing refresh tag, or content without an initial integer does not trigger it.
What the evidence shows
The scanned static HTML declares a meta-refresh delay that ShipReady parsed as greater than zero.
Limits of this check
ShipReady does not execute the refresh, follow its destination, inspect JavaScript navigation, determine whether a browser will honor the tag, or perform a complete accessibility audit.
How to fix it
Replace unnecessary timed navigation
Use an intentional server-side redirect for permanent navigation needs, or update content without reloading the whole page when a timed refresh is not necessary.
How to verify the change
Inspect the deployed document
Check the served HTML and test the intended navigation flow in supported browsers.
Expected: No unintended positive-delay meta refresh remains in the deployed page.