Website review, no card needed

necchurch.org logo

necchurch.org website review

Visit site (opens in a new tab)Reviewed 18 October 202632 issues · 88 checks

This review found 32 issues worth fixing on necchurch.org, 12 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
2.9 s1.7 sApr 25Oct 101.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.1 s
May 2, 20262.2 s
May 9, 20262.3 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.6 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.2 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.4 s
Sep 5, 20262.5 s
Sep 12, 20262.4 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.6 s
Oct 10, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
120 ms84 msApr 25Oct 1097 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026113 ms
May 2, 2026116 ms
May 9, 2026112 ms
May 16, 2026110 ms
May 23, 202699 ms
May 30, 202694 ms
Jun 6, 202694 ms
Jun 13, 202698 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202694 ms
Jul 11, 202688 ms
Jul 18, 202695 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202695 ms
Aug 15, 202689 ms
Aug 22, 202694 ms
Aug 29, 202691 ms
Sep 5, 202694 ms
Sep 12, 202699 ms
Sep 19, 202697 ms
Sep 26, 202697 ms
Oct 3, 202698 ms
Oct 10, 202697 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 necchurch.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. necchurch.org at 0.4 s0.4 s
  2. necchurch.org at 0.8 s0.8 s
  3. necchurch.org at 1.1 s1.1 s
  4. necchurch.org at 1.5 s1.5 s
  5. necchurch.org at 1.9 s1.9 s
  6. necchurch.org at 2.3 s2.3 s
  7. necchurch.org at 2.6 s2.6 s
  8. necchurch.org at 3.0 s3.0 s

Speed

10 to fix49
  • Render-blocking requests

    5.4 s

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

  • Reduce unused JavaScript

    3.7 s · 756 KiB

    About 756 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.

  • Use efficient cache lifetimes

    1.2 s · 161 KiB

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

  • Mobile performance score: 49

    49/100

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

  • Improve image delivery

    750 ms · 3.1 MB

    5 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Mailchimp and Clarity and others), adding 963 KiB and 784 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 123 KiB

    About 123 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 567 ms

    567 ms

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

  • Minify CSS

    300 ms · 14 KiB

    14 KiB could be saved by minifying CSS.

  • Main-thread work: 2.4 s

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

  • Minify JavaScript

    150 ms · 44 KiB

    44 KiB could be saved by minifying JavaScript.

  • 12 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 83 but mobile only 49. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

    2 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 17.9 s

    17.9 s

    Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WE ARE THE LOVE THE ‘VILLE CHURCH”.

  • First Contentful Paint: 7.1 s

    7.1 s

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

  • Time to Interactive: 18.0 s

    18.0 s

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

  • Speed Index: 8.9 s

    8.9 s

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

  • Total Blocking Time: 321 ms

    321 ms

    Scripts block taps and scrolling for 321 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.

  • Largest content (LCP) held steady for real visitors

    +1%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 93 ms

    93 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 585 ms

    585 ms

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

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

    -15%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 113 ms to 97 ms 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

1 to fix70
  • Page weight: 6.2 MB in 116 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 116 requests on a phone: images 4.1 MB (13), scripts 1.2 MB (42) and fonts 646 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (210 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 (180 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.76 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.76 g of CO₂e: 211.4 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 8492
  • 30 text elements with low contrast

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

  • 4 tap targets too small

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

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 39 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: 39 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

2 to fixGoogle 9295
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 73 internal links, 30 external

    The homepage links to 73 pages on necchurch.org and 30 external pages.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Discover the joy of worship at Northeast Christian, a welcoming non-denominational church in Louisville, KY. Celebratin…”.

  • One H1 headline

    Your main headline reads: “We are the Love the ‘Ville Church”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Non Denominational Church Service | Northeast Christian”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Church, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.necchurch.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.necchurch.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 (456 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 4 pages share a meta description

    https://www.necchurch.org/spiritual-formation and https://www.necchurch.org/serve use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://www.necchurch.org/youth, https://www.necchurch.org/spiritual-formation, https://www.necchurch.org/outreach, https://www.necchurch.org/deaf-ministry, https://www.necchurch.org/grinstead and https://www.necchurch.org/basics and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.necchurch.org/who-we-are, https://www.necchurch.org/new, https://www.necchurch.org/basics and https://www.necchurch.org/groups took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

    8 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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.

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

    The homepage carries about 362 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join Us Online Sundays”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Merch Shop”, “Join Us Online Sundays” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 necchurch.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on necchurch.org, including 16 speed issues, 2 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