Website review, no card needed

survive-a-storm.com logo

survive-a-storm.com website review

Visit site (opens in a new tab)Reviewed 20 November 202633 issues · 84 checks

This review found 33 issues worth fixing on survive-a-storm.com, 13 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.8 s3.7 sMay 30Nov 143.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.9 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20263.9 s
Jun 27, 20263.9 s
Jul 4, 20263.9 s
Jul 11, 20264.0 s
Jul 18, 20264.2 s
Jul 25, 20264.5 s
Aug 1, 20264.6 s
Aug 8, 20264.6 s
Aug 15, 20264.5 s
Aug 22, 20264.5 s
Aug 29, 20264.4 s
Sep 5, 20264.5 s
Sep 12, 20264.7 s
Sep 19, 20264.5 s
Sep 26, 20264.5 s
Oct 3, 20264.5 s
Oct 10, 20264.3 s
Oct 17, 20264.2 s
Oct 24, 20264.1 s
Oct 31, 20264.0 s
Nov 7, 20263.9 s
Nov 14, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
108 ms75 msMay 30Nov 1479 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202696 ms
Jun 6, 202697 ms
Jun 13, 2026104 ms
Jun 20, 2026104 ms
Jun 27, 2026103 ms
Jul 4, 2026102 ms
Jul 11, 2026102 ms
Jul 18, 202696 ms
Jul 25, 2026101 ms
Aug 1, 2026102 ms
Aug 8, 202696 ms
Aug 15, 202696 ms
Aug 22, 202695 ms
Aug 29, 202694 ms
Sep 5, 202696 ms
Sep 12, 202694 ms
Sep 19, 202691 ms
Sep 26, 202688 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202687 ms
Oct 24, 202687 ms
Oct 31, 202686 ms
Nov 7, 202683 ms
Nov 14, 202679 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of survive-a-storm.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. survive-a-storm.com at 0.5 s0.5 s
  2. survive-a-storm.com at 0.9 s0.9 s
  3. survive-a-storm.com at 1.4 s1.4 s
  4. survive-a-storm.com at 1.9 s1.9 s
  5. survive-a-storm.com at 2.3 s2.3 s
  6. survive-a-storm.com at 2.8 s2.8 s
  7. survive-a-storm.com at 3.3 s3.3 s
  8. survive-a-storm.com at 3.7 s3.7 s

Speed

8 to fix57
  • Use efficient cache lifetimes

    2.6 s · 3.4 MB

    88 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).

  • Reduce unused JavaScript

    3.4 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.

  • Render-blocking requests

    1.9 s

    34 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

  • Improve image delivery

    2.3 MB

    5 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, odoo.com and Affirm and others), adding 2.0 MB and 743 ms of main-thread time.

  • Google Tag Manager adds 355 ms

    355 ms

    Google Tag Manager costs a phone 355 ms of main-thread work and 835 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • odoo.com adds 170 ms

    170 ms

    odoo.com costs a phone 170 ms of main-thread work and 872 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused CSS

    160 ms · 66 KiB

    About 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 203 ms. During a long task the page ignores taps.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Legacy JavaScript

    4 KiB

    Polyfills for old browsers add 4 KiB JavaScript that modern phones do not need.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 821 ms of it running JavaScript. That is comfortably low.

  • Server response: 48 ms

    48 ms

    Your server sent the HTML in 48 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 5.7 s

    5.7 s

    Real visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 4.7 s

    4.7 s

    Real visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.

  • Largest Contentful Paint: 20.0 s

    20.0 s

    Your largest element takes 20.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 24.4 s

    24.4 s

    The page becomes fully interactive after 24.4 s. Good is under 3.8 s.

  • Speed Index: 7.0 s

    7.0 s

    Visually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.4 s

    2.4 s

    The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

  • Cumulative Layout Shift: 0.125

    0.125

    The layout shifts by 0.125 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 223 ms

    223 ms

    Scripts block taps and scrolling for 223 ms in total while the page loads. Good is under 200 ms.

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.9 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 86 ms

    86 ms

    Real visitors wait 86 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 16% faster for real visitors

    -16%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 96 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

1 to fix70
  • Page weight: 5.3 MB in 151 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 151 requests on a phone: images 2.9 MB (26), scripts 2.1 MB (60) and stylesheets 80 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (77 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 2 images below the first screen load straight away

    2 images further down the page (77 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.51 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.51 g of CO₂e: 181.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8992
  • 11 text elements with low contrast

    11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • All page content should be contained by landmarks (21 elements)

    All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h1 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 61 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8590
  • Structured data has 2 problems

    Structured data found (Organization and Product) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("https://x.com/ surviveastorm")”.

  • No robots.txt

    There is no robots.txt at survive-a-storm.com/robots.txt, the first file search crawlers ask for.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 76 internal links, 13 external

    The homepage links to 76 pages on survive-a-storm.com and 13 external pages.

6 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Industry leader in the world's safest above and below ground storm shelters. EF-5 Protection. FEMA/ICC Compliant. Torna…”.

  • One H1 headline

    Your main headline reads: “StormWarn”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Survive-A-Storm: Industry Leader in Storm Shelters”.

  • Canonical URL set

    The canonical URL is https://survive-a-storm.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://survive-a-storm.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://survive-a-storm.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (888 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://survive-a-storm.com/residential-storm-shelters and https://survive-a-storm.com/residential-storm-shelters/above-ground all use the title “Residential Storm Shelters and Tornado Shelters | Survive-A-Storm”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://survive-a-storm.com/residential-storm-shelters and https://survive-a-storm.com/residential-storm-shelters/above-ground use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://survive-a-storm.com/learning-center has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://survive-a-storm.com/learning-center/install-gallery has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://survive-a-storm.com/residential-storm-shelters/garagecube took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

2 checks passed
  • Tap targets are thumb-sized

    12 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 672 words of copy

    The homepage carries about 672 words of visible text.

5 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “CONTACT”.

  • Social proof on the page

    Social proof on the homepage: 19 testimonial or review blocks, a star rating and 36 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 3 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 30 other companies contacted

    Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at survive-a-storm.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
IONOS

Company

Headquarters
Thomasville

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on survive-a-storm.com, including 17 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25