Website review, no card needed

ccpalions.org logo

ccpalions.org website review

Visit site (opens in a new tab)Reviewed 21 October 202647 issues · 89 checks

This review found 47 issues worth fixing on ccpalions.org, 12 of them high impact, across 89 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of ccpalions.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ccpalions.org at 0.5 s0.5 s
  2. ccpalions.org at 0.9 s0.9 s
  3. ccpalions.org at 1.4 s1.4 s
  4. ccpalions.org at 1.9 s1.9 s
  5. ccpalions.org at 2.4 s2.4 s
  6. ccpalions.org at 2.8 s2.8 s
  7. ccpalions.org at 3.3 s3.3 s
  8. ccpalions.org at 3.8 s3.8 s

Speed

9 to fix53
  • Improve image delivery

    4.3 s · 1.4 MB

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

  • Render-blocking requests

    4.2 s

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

  • Reduce unused JavaScript

    1.6 s · 320 KiB

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

  • Mobile performance score: 53

    53/100

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

  • Use efficient cache lifetimes

    450 ms · 232 KiB

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

  • 8 third-party services on the page

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

  • Reduce unused CSS

    450 ms · 133 KiB

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

  • Google Tag Manager adds 378 ms

    378 ms

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

  • Cloudflare CDN adds 2 ms

    2 ms

    Cloudflare CDN costs a phone 2 ms of main-thread work and 298 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.

  • Minify CSS

    150 ms · 27 KiB

    27 KiB could be saved by minifying CSS.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 8 KiB

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

  • Document request latency

    72 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    50 ms

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

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 82 but mobile only 53. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 520 ms of it running JavaScript. That is comfortably low.

  • Server response: 65 ms

    65 ms

    Your server sent the HTML in 65 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix61
  • Largest Contentful Paint: 13.9 s

    13.9 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Time to Interactive: 13.9 s

    13.9 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • Total Blocking Time: 254 ms

    254 ms

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

  • 6 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix43
  • 1 image over 500 KB

    DownloadApp.jpg weighs 627 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.3 MB in 61 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 61 requests on a phone: images 2.0 MB (17), scripts 790 KiB (28) and fonts 310 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

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

  • 3 images below the first screen load straight away

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

  • 2 images far larger than shown

    431 KiB

    2 images are downloaded at several times the size a phone draws them, for example DownloadApp.jpg at 1,235 px wide, shown at 350 px. Resized copies would save about 431 KiB.

  • About 0.9 g of CO₂ per visit

    0.94 g

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

Accessibility

8 to fixGoogle 7989
  • Required ARIA attributes must be provided (1 element)

    Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

  • Frames without titles

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (15 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 8370
  • Title is short (10 characters)

    Your title is only 10 characters: “CCPA Lions”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (38 characters)

    Your meta description is only 38 characters: “Cincinnati College Preparatory Academy”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • 5 links crawlers can't follow

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

  • 2 links with vague text

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

  • 44 internal links, 16 external

    The homepage links to 44 pages on ccpalions.org and 16 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “September 2026 Superintendent Update”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,488 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 4 pages share a title

    /, https://ccpalions.org/ElementarySchool.aspx, https://ccpalions.org/MiddleSchool.aspx and https://ccpalions.org/HighSchool.aspx all use the title “CCPA Lions”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://ccpalions.org/page/Annual-Reports/159858/Index.html, https://ccpalions.org/ElementarySchool.aspx, https://ccpalions.org/MiddleSchool.aspx and https://ccpalions.org/HighSchool.aspx use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 3 broken images

    3 images failed to load on a phone, for example https://ccpalions.org/Images/Site/Loading.gif.

  • 4 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 8-field form

    Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

  • No opening hours

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

  • No risk reducer

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

  • About 1,320 words of copy

    The homepage carries about 1,320 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join CCPA” and “Learn more”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Buy Tickets”, “Join CCPA” and “Download our school app”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    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.

  • 14 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ccpalions.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics

Company

Founded
1999

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on ccpalions.org, including 15 speed issues, 8 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25