Website review, no card needed

krucialrr.org logo

krucialrr.org website review

Visit site (opens in a new tab)Reviewed 6 November 202652 issues · 97 checks

This review found 52 issues worth fixing on krucialrr.org, 17 of them high impact, across 97 checks. The most urgent: reduce unused JavaScript. 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.7 s3.7 sMay 16Oct 314.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.0 s
May 23, 20264.0 s
May 30, 20264.0 s
Jun 6, 20264.0 s
Jun 13, 20263.9 s
Jun 20, 20263.9 s
Jun 27, 20263.9 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.2 s
Jul 25, 20264.3 s
Aug 1, 20264.3 s
Aug 8, 20264.4 s
Aug 15, 20264.5 s
Aug 22, 20264.6 s
Aug 29, 20264.5 s
Sep 5, 20264.2 s
Sep 12, 20264.0 s
Sep 19, 20263.9 s
Sep 26, 20263.9 s
Oct 3, 20263.9 s
Oct 10, 20264.1 s
Oct 17, 20264.1 s
Oct 24, 20264.1 s
Oct 31, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
202 ms107 msMay 16Oct 31187 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026147 ms
May 23, 2026145 ms
May 30, 2026147 ms
Jun 6, 2026152 ms
Jun 13, 2026157 ms
Jun 20, 2026167 ms
Jun 27, 2026157 ms
Jul 4, 2026160 ms
Jul 11, 2026150 ms
Jul 18, 2026138 ms
Jul 25, 2026142 ms
Aug 1, 2026133 ms
Aug 8, 2026146 ms
Aug 15, 2026140 ms
Aug 22, 2026138 ms
Aug 29, 2026146 ms
Sep 5, 2026127 ms
Sep 12, 2026118 ms
Sep 19, 2026125 ms
Sep 26, 2026134 ms
Oct 3, 2026143 ms
Oct 10, 2026187 ms
Oct 17, 2026188 ms
Oct 24, 2026191 ms
Oct 31, 2026187 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 krucialrr.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. krucialrr.org at 1.1 s1.1 s
  2. krucialrr.org at 2.3 s2.3 s
  3. krucialrr.org at 3.4 s3.4 s
  4. krucialrr.org at 4.6 s4.6 s
  5. krucialrr.org at 5.7 s5.7 s
  6. krucialrr.org at 6.8 s6.8 s
  7. krucialrr.org at 8.0 s8.0 s
  8. krucialrr.org at 9.1 s9.1 s

Speed

15 to fix20
  • Reduce unused JavaScript

    13.1 s · 2.0 MB

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

  • Use efficient cache lifetimes

    6.2 s · 1.2 MB

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

  • Mobile performance score: 20

    20/100

    Your mobile performance score is 20. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.5 s

    A phone's processor spends 7.5 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, sensehq.com and Google CDN and others), adding 14.1 MB and 2.6 s of main-thread time.

  • Vimeo adds 140 ms

    140 ms

    Vimeo costs a phone 140 ms of main-thread work and 9.7 MB 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.

  • sensehq.com adds 897 ms

    897 ms

    sensehq.com costs a phone 897 ms of main-thread work and 2.1 MB 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.

  • Google Tag Manager adds 933 ms

    933 ms

    Google Tag Manager costs a phone 933 ms of main-thread work and 1.1 MB 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.

  • Improve image delivery

    1,004 KiB

    4 images could be 1,004 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    800 ms

    48 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • Reduce unused CSS

    450 ms · 79 KiB

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

  • Legacy JavaScript

    400 ms · 71 KiB

    Polyfills for old browsers add 71 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • Google CDN adds 316 ms

    316 ms

    Google CDN costs a phone 316 ms of main-thread work and 736 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.

  • Facebook adds 282 ms

    282 ms

    Facebook costs a phone 282 ms of main-thread work and 293 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.

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 31 KiB

    31 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

11 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: 4.6 s

    4.6 s

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

  • Largest Contentful Paint: 38.5 s

    38.5 s

    Your largest element takes 38.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Krucial Rapid Response is a non-profit organization rapidly…”.

  • Speed Index: 17.6 s

    17.6 s

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

  • Time to Interactive: 41.8 s

    41.8 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • Tap response (INP) got 29% slower for real visitors

    +29%

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

  • Real-user TTFB: 901 ms

    901 ms

    Real visitors wait 901 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.193

    0.193

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

  • 17 images without width and height

    17 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    +2%

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

3 checks passed
  • Real-user INP: 167 ms

    167 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.5 s

    1.5 s

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

Images and page weight

5 to fix33
  • Page weight: 17.1 MB in 205 requests

    17.1 MB

    Your homepage downloads 17.1 MB in 205 requests on a phone: other files 9.3 MB (45), scripts 4.1 MB (63) and images 2.0 MB (23). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    610 KiB

    3 images are downloaded at several times the size a phone draws them, for example DSC_8236-scaled.jpg at 2,560 px wide, shown at 359 px. Resized copies would save about 610 KiB.

  • An image on the first screen is lazy-loaded

    KrucialRapidResponseLogo-col350w.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images in older formats

    3 images (742 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.

  • 3 images below the first screen load straight away

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

  • About 4.8 g of CO₂ per visit

    4.83 g

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

Accessibility

7 to fixGoogle 9793
  • 14 text elements with low contrast

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

  • Banner landmark should not be contained in another landmark (2 elements)

    Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Krucial Rapid Response - No. 1 Non-Profit Medical Staffing Partner”.

  • 48 internal links, 18 external

    The homepage links to 48 pages on krucialrr.org and 18 external pages.

7 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Krucial Rapid Response is a non-profit organization rapidly preparing, mobilizing and deploying medical personnel and c…”.

  • One H1 headline

    Your main headline reads: “Become a Krucial Reservist”.

  • Canonical URL set

    The canonical URL is https://krucialrr.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://krucialrr.org/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://krucialrr.org/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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • 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 (709 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    / and https://krucialrr.org/reservist all use the title “Krucial Rapid Response - No. 1 Non-Profit Medical Staffing Partner”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://krucialrr.org/leadership-staff-and-workforce and https://krucialrr.org/emergency-management-deployment have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://krucialrr.org/privacy and https://krucialrr.org/terms use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://krucialrr.org/contact, https://krucialrr.org/privacy and https://krucialrr.org/terms have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

5 to fixGoogle 4673
  • 1 broken image

    1 image failed to load on a phone, for example https://px.adentifi.com/Pixels?a_id=22657;p_url=https%3A%2F%2Fkrucialrr.org%2F;uq=5096555338492.12.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 455 words of copy

    The homepage carries about 455 words of visible text.

4 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “APPLY NOW”, “CONTACT” and “Join the Ranks: Become a Reservist!”.

  • 1 short form

    A short form (6 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

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 Meta Pixel (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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 2 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.

  • 32 other companies contacted

    Loading the homepage contacts 32 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 krucialrr.org, 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
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Employees
57

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on krucialrr.org, including 26 speed issues, 1 SEO issue and 3 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