Website review, no card needed

ihopkc.org logo

ihopkc.org website review

Visit site (opens in a new tab)Reviewed 18 November 202641 issues · 84 checks

This review found 41 issues worth fixing on ihopkc.org, 13 of them high impact, across 84 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
3.8 s3.2 sJun 13Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
Jun 13, 20263.4 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.6 s
Jul 11, 20263.7 s
Jul 18, 20263.6 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.4 s
Sep 19, 20263.3 s
Sep 26, 20263.2 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Oct 17, 20263.6 s
Oct 24, 20263.8 s
Oct 31, 20263.6 s
Nov 7, 20263.6 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
122 ms97 msJun 13Nov 14109 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 2026100 ms
Jun 20, 2026110 ms
Jun 27, 2026110 ms
Jul 4, 2026107 ms
Jul 11, 2026110 ms
Jul 18, 2026107 ms
Jul 25, 2026111 ms
Aug 1, 2026119 ms
Aug 8, 2026115 ms
Aug 15, 2026114 ms
Aug 22, 2026115 ms
Aug 29, 2026108 ms
Sep 5, 2026110 ms
Sep 12, 2026109 ms
Sep 19, 2026103 ms
Sep 26, 2026102 ms
Oct 3, 2026102 ms
Oct 10, 2026102 ms
Oct 17, 2026105 ms
Oct 24, 2026109 ms
Oct 31, 2026103 ms
Nov 7, 2026109 ms
Nov 14, 2026109 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 ihopkc.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ihopkc.org at 0.6 s0.6 s
  2. ihopkc.org at 1.2 s1.2 s
  3. ihopkc.org at 1.8 s1.8 s
  4. ihopkc.org at 2.3 s2.3 s
  5. ihopkc.org at 2.9 s2.9 s
  6. ihopkc.org at 3.5 s3.5 s
  7. ihopkc.org at 4.1 s4.1 s
  8. ihopkc.org at 4.7 s4.7 s

Speed

10 to fix48
  • Reduce unused JavaScript

    5.9 s · 1.1 MB

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

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48. 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 (Squarespace, YouTube and sqspcdn.com and others), adding 3.0 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    910 ms · 243 KiB

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

  • Squarespace adds 654 ms

    654 ms

    Squarespace costs a phone 654 ms of main-thread work and 1.3 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.

  • Legacy JavaScript

    450 ms · 102 KiB

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

  • YouTube adds 389 ms

    389 ms

    YouTube costs a phone 389 ms of main-thread work and 1,001 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.

  • Main-thread work: 3.7 s

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

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 421 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.

  • Improve image delivery

    250 ms · 205 KiB

    6 images could be 205 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 192 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).

  • Use efficient cache lifetimes

    5 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).

  • 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: 76 ms

    76 ms

    Your server sent the HTML in 76 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: 4.2 s

    4.2 s

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Largest Contentful Paint: 19.3 s

    19.3 s

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

  • First Contentful Paint: 7.0 s

    7.0 s

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

  • Time to Interactive: 19.5 s

    19.5 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • Total Blocking Time: 361 ms

    361 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

4 checks passed
  • Real-user INP: 110 ms

    110 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 702 ms

    702 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.2 MB in 100 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 100 requests on a phone: scripts 2.1 MB (52), images 409 KiB (12) and stylesheets 231 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (36 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.90 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 10098
  • 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 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 1 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 10074
  • No H1 headline

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

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “International House of Prayer - Kansas City | 24/7 Prayer with Worship”.

  • Meta description is long (172 characters)

    Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/68e7ce7801016d545db…”.

  • 72 internal links, 15 external

    The homepage links to 72 pages on ihopkc.org and 15 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.ihopkc.org/.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.ihopkc.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.

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

  • Text is in the HTML

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

Other pages

6 to fix69
  • 3 linked pages hidden from search

    https://www.ihopkc.org/community-standards, https://www.ihopkc.org/the-global-bridegroom-fast and https://www.ihopkc.org/fasting-guidelines are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share 2 titles

    https://www.ihopkc.org/about/ihopkc and https://www.ihopkc.org/about-us all use the title “About IHOPKC | International House of Prayer Kansas City — Internatio…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.ihopkc.org/our-community, https://www.ihopkc.org/the-global-bridegroom-fast and https://www.ihopkc.org/fasting-guidelines have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.ihopkc.org/about/ihopkc and https://www.ihopkc.org/about-us use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

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

  • 2 pages without an H1

    https://www.ihopkc.org/advent and https://www.ihopkc.org/give have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 5 third-party cookies

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

  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/68e7ce7801016d545db408ed/40/5c5a…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 667 words of visible text.

2 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Current Prayer Room Schedule”, “Learn More About IHOPKC” and “Contact”.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 5 cookies set on arrival

    5

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 ihopkc.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
Squarespace
Hosting
Squarespace

Company

Founded
1999

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on ihopkc.org, including 19 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