ym360.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, shgcdn2.com and Shopify and others), adding 2.0 MB and 2.0 s of main-thread time.

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

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

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

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

Shopify costs a phone 373 ms of main-thread work and 630 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.

shgcdn2.com costs a phone 385 ms of main-thread work and 270 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.

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

rebuyengine.com costs a phone 265 ms of main-thread work and 329 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 14.4 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 22.6 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 3.8 MB in 325 requests on a phone: scripts 2.4 MB (152), other files 771 KiB (118) and images 205 KiB (19). 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 1.08 g of CO₂e: 129.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Your title is 69 characters, so Google will cut it off around 60: “YM360 | Youth Ministry 360 | Curriculum, Camps, Conferences, Training”.

There are 10 <h1> headlines (“YM360”, “YM360” and “TRUSTED BY THOUSANDS OF YOUTH PASTORS”). One clear main headline is easier for people and search engines.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 60 pages on ym360.com and 20 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.

There is no https://youthministry360.com/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://youthministry360.com/collections/youth-camp-resources-by-ym360 and https://youthministry360.com/collections/store have no meta description, so Google writes the search snippet from whatever text it finds.

https://youthministry360.com/collections/midweek took over 3 s to send its HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

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.

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: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

The homepage carries about 599 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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 9 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 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.