upci.org website review

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

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

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

7 third-party services load with your homepage (Google Maps, Google Tag Manager and Google Fonts and others), adding 8.0 MB and 390 ms of main-thread time.

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

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

WordPress costs a phone 0 ms of main-thread work and 6.9 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.

About 131 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.

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

Google Maps costs a phone 243 ms of main-thread work and 730 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.

The page has 2,146 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

2 KiB could be saved by minifying CSS.

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 visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

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

Your homepage downloads 10.5 MB in 251 requests on a phone: images 8.5 MB (96), scripts 1.1 MB (66) and fonts 500 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

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

1 button has no accessible name, so screen readers announce just “button”.

Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 visible links have no text or label, so screen readers cannot say where they go.

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

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

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

Structured data found ((untyped), Article, BlogPosting and BreadcrumbList) but with 1 problem, for example “block has no @type”.

3 links have no real href, so search engines can't follow them.

The homepage links to 289 pages on upci.org and 107 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

https://upci.org/our-beliefs, https://upci.org/statements-archive, https://upci.org/leadership, https://upci.org/category/superintendents-updates and https://upci.org/districts have no meta description, so Google writes the search snippet from whatever text it finds.

https://upci.org/es, https://upci.org/fr, https://upci.org/about-the-upci, https://upci.org/oneness-pentecostalism, https://upci.org/our-beliefs and https://upci.org/statements-archive and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://upci.org/general-conference-2026-election-results, https://upci.org/upci-church-statistics-2025-pastor-survey, https://upci.org/es, https://upci.org/fr, https://upci.org/oneness-pentecostalism and https://upci.org/our-beliefs and 2 others took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to set referrer policy: The value '' is not one of 'no-referrer', 'no-referrer-when-downgrade', 'origin', 'origi…”.

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

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.

Social proof on the homepage: 89 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 209 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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

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

Opening the homepage sets 2 cookies (measured from a US location before any click).

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.

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