lccs.org website review

43 files are served with short cache lifetimes, so returning visitors download them again (10.0 MB).

7 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.9 s faster on a phone.

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

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

8 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Tag Manager and others), adding 1.5 MB and 776 ms of main-thread time.

Google CDN costs a phone 369 ms of main-thread work and 832 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.

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

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

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

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

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

Polyfills for old browsers add 21 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.

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 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

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

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

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-17, real Chrome visitors' tap response (inp) went from 78 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.6 MB in 157 requests on a phone: images 9.6 MB (33), scripts 1.4 MB (50) and fonts 369 KiB (7). Under 2 MB keeps phones on slow connections fast.

5 images (1.5 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.

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

1 image is downloaded at several times the size a phone draws it, for example flag-pole-scaled-e1760394187293-1024x725.jpg at 1,024 px wide, shown at 312 px. Resized copies would save about 37 KiB.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

All page content should be contained by landmarks: 11 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.

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

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

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

Your title is 67 characters, so Google will cut it off around 60: “Lake Country Christian School | Fort Worth Private Christian School”.

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

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

The homepage links to 64 pages on lccs.org and 15 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://www.lccs.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://www.lccs.org/school-board, https://www.lccs.org/administration, https://www.lccs.org/employment, https://www.lccs.org/privacy-policy, https://www.lccs.org/application and https://www.lccs.org/newfamilyguide and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lccs.org/school-board, https://www.lccs.org/administration, https://www.lccs.org/location, https://www.lccs.org/privacy-policy, https://www.lccs.org/admissions and https://www.lccs.org/admissionscriteria and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lccs.org/school-board, https://www.lccs.org/location, https://www.lccs.org/employment, https://www.lccs.org/privacy-policy, https://www.lccs.org/admissions and https://www.lccs.org/admissionscriteria and 5 others took over 3 s to send their HTML from our server.

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

6 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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

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

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

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

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