Website review, no card needed

icisf.org logo

icisf.org website review

Visit site (opens in a new tab)Reviewed 24 October 202647 issues · 95 checks

This review found 47 issues worth fixing on icisf.org, 22 of them high impact, across 95 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.4 s2.7 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.8 s
May 9, 20264.0 s
May 16, 20264.1 s
May 23, 20264.2 s
May 30, 20264.1 s
Jun 6, 20263.9 s
Jun 13, 20263.8 s
Jun 20, 20263.7 s
Jun 27, 20263.7 s
Jul 4, 20263.5 s
Jul 11, 20263.3 s
Jul 18, 20263.2 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
116 ms84 msMay 2Oct 17102 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202688 ms
May 9, 202688 ms
May 16, 202691 ms
May 23, 202689 ms
May 30, 202693 ms
Jun 6, 202696 ms
Jun 13, 202695 ms
Jun 20, 2026104 ms
Jun 27, 2026103 ms
Jul 4, 2026102 ms
Jul 11, 2026103 ms
Jul 18, 2026104 ms
Jul 25, 2026104 ms
Aug 1, 2026111 ms
Aug 8, 2026105 ms
Aug 15, 2026102 ms
Aug 22, 202699 ms
Aug 29, 2026101 ms
Sep 5, 2026104 ms
Sep 12, 2026105 ms
Sep 19, 2026112 ms
Sep 26, 2026103 ms
Oct 3, 2026103 ms
Oct 10, 2026104 ms
Oct 17, 2026102 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 icisf.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. icisf.org at 1.6 s1.6 s
  2. icisf.org at 3.1 s3.1 s
  3. icisf.org at 4.7 s4.7 s
  4. icisf.org at 6.3 s6.3 s
  5. icisf.org at 7.9 s7.9 s
  6. icisf.org at 9.4 s9.4 s
  7. icisf.org at 11.0 s11.0 s
  8. icisf.org at 12.6 s12.6 s

Speed

10 to fix43
  • Use efficient cache lifetimes

    7.2 s · 3.2 MB

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

  • Improve image delivery

    6.5 s · 3.6 MB

    21 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.5 s faster on a phone.

  • Render-blocking requests

    3.9 s

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

  • Mobile performance score: 43

    43/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Vimeo and Google Analytics and others), adding 1.1 MB and 640 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 114 KiB

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

  • Google Tag Manager adds 545 ms

    545 ms

    Google Tag Manager costs a phone 545 ms of main-thread work and 506 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 JavaScript

    565 KiB

    About 565 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 3.0 s

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

  • Vimeo adds 43 ms

    43 ms

    Vimeo costs a phone 43 ms of main-thread work and 521 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.

  • 10 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    10 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 132 ms

    132 ms

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

Core Web Vitals

10 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 FCP: 3.2 s

    3.2 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 23.8 s

    23.8 s

    Your largest element takes 23.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Smartphone displaying CISM news logo on laptop”.

  • Speed Index: 18.5 s

    18.5 s

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

  • Time to Interactive: 24.1 s

    24.1 s

    The page becomes fully interactive after 24.1 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.

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Total Blocking Time: 500 ms

    500 ms

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

  • 18 images without width and height

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

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

    +17%

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

4 checks passed
  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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.

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 8.0 MB in 171 requests

    8.0 MB

    Your homepage downloads 8.0 MB in 171 requests on a phone: images 6.1 MB (30), scripts 1.3 MB (53) and fonts 334 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    1.3 MB

    9 images are downloaded at several times the size a phone draws them, for example UMBC-vertical-logo-Star.jpg at 596 px wide, shown at 129 px. Resized copies would save about 1.3 MB.

  • 13 images in older formats

    13 images (2.4 MB) 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.

  • 12 images below the first screen load straight away

    12 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.3 g of CO₂ per visit

    2.28 g

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

Accessibility

9 to fixGoogle 7687
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 16 text elements with low contrast

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

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 5 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 9276
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (5 characters)

    Your title is only 5 characters: “ICISF”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (55 characters)

    Your meta description is only 55 characters: “International Critical Incident Stress Foundation, Inc.”. 70 to 160 characters is enough to sell the click.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 61 internal links, 16 external

    The homepage links to 61 pages on icisf.org and 16 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness, Organization 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://icisf.org/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://icisf.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 (833 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://icisf.org/faculty, whose canonical is https://icisf.org/about-us/faculty. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://icisf.org/teach-a-course/approved-instructor-forms and https://icisf.org/approved-instructor-program have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages slow to respond

    https://icisf.org/education-training, https://icisf.org/speakers-bureau, https://icisf.org/self-paced-online, https://icisf.org/conference-and-events, https://icisf.org/map-of-upcoming-icisf-courses and https://icisf.org/education-training/ceu-information and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 5494
  • 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.”).

  • Browser-reported issues

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 508 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”, “Sign up for emails” and “Certificate Replacement Request”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 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.

  • 20 other companies contacted

    Loading the homepage contacts 20 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 icisf.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
Vue.js
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on icisf.org, including 20 speed issues, 4 SEO issues and 4 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