crossroads.net website review

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

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

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

osano.com costs a phone 1.2 s of main-thread work and 80 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (osano.com, Google Tag Manager and userway.org and others), adding 2.9 MB and 2.5 s of main-thread time.

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

175 KiB could be saved by minifying JavaScript.

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

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

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

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

userway.org costs a phone 236 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.

170 KiB JavaScript is shipped twice across bundles.

About 117 KiB of CSS is downloaded but never applied on this page.

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.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 14.9 MB in 263 requests on a phone: other files 9.3 MB (86), scripts 3.7 MB (97) and images 1.4 MB (35). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example crds-home-jumbotron-high-five.jpg at 1,694 px wide, shown at 390 px. Resized copies would save about 608 KiB.

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

By the Sustainable Web Design model, a visit to your homepage emits about 4.21 g of CO₂e: 505.4 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”.

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

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 50 characters: “No matter what your beliefs, you are welcome here.”. 70 to 160 characters is enough to sell the click.

No XML sitemap at https://www.crossroads.net/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at crossroads.net/robots.txt, the first file search crawlers ask for.

The homepage links to 21 pages on crossroads.net and 7 external pages.

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.

The HTML your server sends has 178 of the 457 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

/media/tags/parenting is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/media/series/raw/when-did-you-stop-dreaming-big and /media/podcasts/messages/when-did-you-stop-dreaming-big all use the title “When Did You Stop Dreaming Big? | Crossroads Church”. Search engines can't tell which page to show for a search, so each competes with the others.

/media/podcasts/crossroads-daily/jesus-doesnt-play-it-safe-or-mark-1 has no meta description, so Google writes the search snippet from whatever text it finds.

/next-step-navigator, /media/articles, /media/podcasts, /media/tags/parenting, /media/topics/culture and /media/topics/self and 3 others use the same meta description. A description written for each page earns more clicks.

/locations, /next-step-navigator, /media/podcasts/messages/when-did-you-stop-dreaming-big and /media/podcasts/audio-articles/god-wanted-me-to-tell-my-wife-about-my-porn-habit-by-donny-black have no <h1> headline, so visitors and search engines get no clear main topic.

/media/topics/humans-of-crossroads has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 images failed to load on a phone, for example https://www.crossroads.net/.

5 errors were logged to the browser console while the page loaded, for example “process is not defined”.

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 457 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

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

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