Website review, no card needed

colliervilleschools.org logo

colliervilleschools.org website review

Visit site (opens in a new tab)Reviewed 26 October 202640 issues · 82 checks

This review found 40 issues worth fixing on colliervilleschools.org, 13 of them high impact, across 82 checks. The most urgent: render-blocking requests. 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 colliervilleschools.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. colliervilleschools.org at 0.4 s0.4 s
  2. colliervilleschools.org at 0.8 s0.8 s
  3. colliervilleschools.org at 1.1 s1.1 s
  4. colliervilleschools.org at 1.5 s1.5 s
  5. colliervilleschools.org at 1.9 s1.9 s
  6. colliervilleschools.org at 2.3 s2.3 s
  7. colliervilleschools.org at 2.6 s2.6 s
  8. colliervilleschools.org at 3.0 s3.0 s

Speed

12 to fix53
  • Render-blocking requests

    7.8 s

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

  • Reduce unused JavaScript

    5.4 s · 653 KiB

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

  • Use efficient cache lifetimes

    1.5 s · 792 KiB

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

  • Improve image delivery

    900 ms · 4.4 MB

    9 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and parentsquare.com and others), adding 7.2 MB and 768 ms of main-thread time.

  • Mobile performance score: 53

    53/100

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

  • Reduce unused CSS

    600 ms · 144 KiB

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

  • parentsquare.com adds 122 ms

    122 ms

    parentsquare.com costs a phone 122 ms of main-thread work and 5.8 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.

  • Google CDN adds 347 ms

    347 ms

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

  • Main-thread work: 2.2 s

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

  • 1,914 HTML elements

    The page has 1,914 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Adobe TypeKit adds 6 ms

    6 ms

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

  • Legacy JavaScript

    200 ms · 15 KiB

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

  • Font display

    150 ms

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

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    33 KiB

    33 KiB could be saved by minifying JavaScript.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 58 ms

    58 ms

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

Core Web Vitals

5 to fix65
  • First Contentful Paint: 17.7 s

    17.7 s

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

  • Largest Contentful Paint: 25.7 s

    25.7 s

    Your largest element takes 25.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Collierville Schools”.

  • Speed Index: 17.7 s

    17.7 s

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

  • Time to Interactive: 26.1 s

    26.1 s

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

  • 12 images without width and height

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

2 checks passed
  • Total Blocking Time: 159 ms

    159 ms

    Scripts block the page for only 159 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • 3 images over 500 KB

    3 images weigh 59.2 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    43.3 MB

    5 images are downloaded at several times the size a phone draws them, for example Heart of Collierville_1769190759.gif at 1,920 px wide, shown at 330 px. Resized copies would save about 43.3 MB.

  • Page weight: 8.1 MB in 151 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 151 requests on a phone: images 4.8 MB (24), scripts 1.5 MB (68) and fonts 1.2 MB (23). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (59.9 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 (55.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.3 g of CO₂ per visit

    2.31 g

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

Accessibility

5 to fixGoogle 10094
  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • 1 form field without a label

    1 form field has 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.

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“Collierville Schools”, “Collierville Schools” and “Collierville Schools”). One clear main headline is easier for people and search engines.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 211 internal links, 29 external

    The homepage links to 211 pages on colliervilleschools.org and 29 external pages.

5 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “The official homepage of Collierville Schools, a public K-12 municipal school district located in Collierville, Tenness…”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Official homepage of Collierville Schools”.

  • Canonical URL set

    The canonical URL is https://www.colliervilleschools.org/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://colliervilleschools.org/sitemap.xml.

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://colliervilleschools.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 (833 words), so crawlers that don't run JavaScript still read it.

Other pages

7 to fix55
  • 2 pages without a title

    https://colliervilleschools.org/boardpolicies and https://colliervilleschools.org/53953_2 have no <title>, so Google invents the link text in results.

  • 3 linked pages hidden from search

    https://colliervilleschools.org/boardpolicies, https://colliervilleschools.org/aboutus and https://colliervilleschools.org/56023_2 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share 2 titles

    https://colliervilleschools.org/16304_1 and https://colliervilleschools.org/board all use the title “Collierville Schools Board of Education”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://colliervilleschools.org/boardagendas, https://colliervilleschools.org/boardpolicies and https://colliervilleschools.org/53953_2 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://colliervilleschools.org/esser and https://colliervilleschools.org/74507_1 use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://colliervilleschools.org/74507_1, whose canonical is https://colliervilleschools.org/cs2030. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://colliervilleschools.org/boardpolicies and https://colliervilleschools.org/53953_2 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    28 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 505 words of copy

    The homepage carries about 505 words of visible text.

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Public Records Request Form”, “Apply Here!” and “Teacher Salary Schedule”.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 colliervilleschools.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on colliervilleschools.org, including 17 speed issues, 2 SEO issues and 2 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