acsi.org website review

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

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

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

26 images could be 5.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Freshchat, Google Tag Manager and Google/Doubleclick Ads and others), adding 2.2 MB and 1.7 s of main-thread time.

About 791 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 920 ms faster on a phone.

Freshchat costs a phone 638 ms of main-thread work and 826 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.

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

Google Tag Manager costs a phone 556 ms of main-thread work and 606 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 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.

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

14 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ASSOCIATION OF CHRISTIAN SCHOOLS INTERNATIONAL (ACSI) STRON…”.

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

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

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

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

46 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' tap response (inp) went from 126 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.6 MB in 130 requests on a phone: images 8.9 MB (51), scripts 1.9 MB (34) and fonts 486 KiB (7). Under 2 MB keeps phones on slow connections fast.

8 images weigh 5.9 MB together. On a phone connection a single image that size takes seconds.

16 images are downloaded at several times the size a phone draws them, for example blog-950-x-475ce7ae0992ba34c2c89f5e2266dbfdf3a.png at 950 px wide, shown at 220 px. Resized copies would save about 2.3 MB.

26 images (8.2 MB) 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.

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

9 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), 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.

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

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

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

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

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 153 pages on acsi.org and 25 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 /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.

/home2 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/legal/policy_resources/articles is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and /home2 all use the title “Association of Christian Schools International”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/header-utility/menu and /legal/policy_resources/articles have no meta description, so Google writes the search snippet from whatever text it finds.

/header/career-center and /careers use the same meta description. A description written for each page earns more clicks.

/home2, /header-utility/store and /legal/policy_resources/articles have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

1 link to other sites is dead, for example https://vimeo.com/user8217693 (410).

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

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

3 links go through two or more redirects, for example https://www.acsi.org/home/SignOut/.

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

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

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: “more than 1,600 students”. 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 form on the homepage, so every lead has to click through to another page first.

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

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, LinkedIn Insight 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.