horizon.org website review

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

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

9 images could be 693 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

Your mobile performance score is 53 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Squarespace, Google Tag Manager and Facebook and others), adding 2.6 MB and 654 ms of main-thread time.

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

Squarespace costs a phone 351 ms of main-thread work and 836 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 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

Adobe TypeKit costs a phone 7 ms of main-thread work and 360 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.

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

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.

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

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Weekend Oct 11, 2026-101.jpg”.

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

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

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

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

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

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

Your homepage downloads 2.6 MB in 72 requests on a phone: scripts 1.1 MB (27), images 1.0 MB (14) and fonts 353 KiB (17). Under 2 MB keeps phones on slow connections fast.

paradise+found+thumbnail+1920x+1080.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images further down the page (152 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 0.74 g of CO₂e: 88.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 image has no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 26 characters: “Horizon Church | San Diego”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“Choose Wisely”, “Stay up to date” and “Our Lead Pastor”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5a9c2c610dbda34f5e6…”.

The homepage links to 57 pages on horizon.org and 18 external pages.

Your Organization JSON-LD is missing name, url, logo and description. 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 /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.

/about-jesus is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/give, /live, /sermons, /about-jesus, /our-faith and /pastorbob and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/sermons has no <h1> headline, so visitors and search engines get no clear main topic.

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

5 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 ()”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

horizon.org is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

horizon.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

horizon.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 263 words of visible text.

DMARC is set to p=none, so mail pretending to be horizon.org is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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