Website review, no card needed

hcde-texas.org logo

hcde-texas.org website review

Visit site (opens in a new tab)Reviewed 27 October 202641 issues · 93 checks

This review found 41 issues worth fixing on hcde-texas.org, 18 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
5.7 s4.3 sMay 9Oct 245.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.7 s
May 16, 20264.8 s
May 23, 20264.7 s
May 30, 20264.8 s
Jun 6, 20265.1 s
Jun 13, 20265.1 s
Jun 20, 20265.1 s
Jun 27, 20265.0 s
Jul 4, 20264.7 s
Jul 11, 20264.7 s
Jul 18, 20264.7 s
Jul 25, 20264.6 s
Aug 1, 20264.6 s
Aug 8, 20264.5 s
Aug 15, 20264.7 s
Aug 22, 20264.7 s
Aug 29, 20264.4 s
Sep 5, 20264.5 s
Sep 12, 20264.5 s
Sep 19, 20264.5 s
Sep 26, 20265.1 s
Oct 3, 20265.4 s
Oct 10, 20265.5 s
Oct 17, 20265.5 s
Oct 24, 20265.3 s
Real-visitor tap response (INP)75th percentile, phones
199 ms139 msMay 9Oct 24191 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026158 ms
May 16, 2026160 ms
May 23, 2026155 ms
May 30, 2026163 ms
Jun 6, 2026163 ms
Jun 13, 2026162 ms
Jun 20, 2026155 ms
Jun 27, 2026152 ms
Jul 4, 2026152 ms
Jul 11, 2026154 ms
Jul 18, 2026159 ms
Jul 25, 2026154 ms
Aug 1, 2026150 ms
Aug 8, 2026148 ms
Aug 15, 2026154 ms
Aug 22, 2026153 ms
Aug 29, 2026146 ms
Sep 5, 2026151 ms
Sep 12, 2026152 ms
Sep 19, 2026157 ms
Sep 26, 2026180 ms
Oct 3, 2026187 ms
Oct 10, 2026188 ms
Oct 17, 2026192 ms
Oct 24, 2026191 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. hcde-texas.org at 0.9 s0.9 s
  2. hcde-texas.org at 1.7 s1.7 s
  3. hcde-texas.org at 2.6 s2.6 s
  4. hcde-texas.org at 3.4 s3.4 s
  5. hcde-texas.org at 4.3 s4.3 s
  6. hcde-texas.org at 5.1 s5.1 s
  7. hcde-texas.org at 6.0 s6.0 s
  8. hcde-texas.org at 6.8 s6.8 s

Speed

12 to fix30
  • Reduce unused JavaScript

    26.7 s · 3.6 MB

    About 3.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 26.7 s faster on a phone.

  • Use efficient cache lifetimes

    6.5 s · 1.3 MB

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

  • Reduce unused CSS

    4.1 s · 196 KiB

    About 196 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.1 s faster on a phone.

  • Render-blocking requests

    4.0 s

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

  • YouTube adds 2.3 s

    2.3 s

    YouTube costs a phone 2.3 s of main-thread work and 4.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 9.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 6.2 MB and 3.5 s of main-thread time.

  • Google Tag Manager adds 678 ms

    678 ms

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

  • 20 long tasks on the main thread

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

  • 2,646 HTML elements

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

  • Facebook adds 233 ms

    233 ms

    Facebook costs a phone 233 ms of main-thread work and 309 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.

  • Improve image delivery

    150 ms · 107 KiB

    7 images could be 107 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 34 KiB

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

  • Font display

    50 ms

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

  • 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: 8 ms

    8 ms

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

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    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-user LCP: 6.3 s

    6.3 s

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

  • Real-user FCP: 4.8 s

    4.8 s

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

  • First Contentful Paint: 34.6 s

    34.6 s

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

  • Largest Contentful Paint: 49.6 s

    49.6 s

    Your largest element takes 49.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A young child, wearing a colorful shirt and shorts, is seen…”.

  • Speed Index: 34.6 s

    34.6 s

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

  • Time to Interactive: 50.1 s

    50.1 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Real-user INP: 213 ms

    213 ms

    Real visitors wait 213 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 20% slower for real visitors

    +20%

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

  • 6 images without width and height

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

3 checks passed
  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 565 ms

    565 ms

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

  • Cumulative Layout Shift: 0.038

    0.038

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

Images and page weight

2 to fix64
  • Page weight: 8.2 MB in 175 requests

    8.2 MB

    Your homepage downloads 8.2 MB in 175 requests on a phone: scripts 6.0 MB (40), images 626 KiB (42) and stylesheets 570 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    img1.jpg 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).

  • About 2.3 g of CO₂ per visit

    2.33 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9693
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 6 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 (2 elements)

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

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

4 to fixGoogle 9287
  • No structured data

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

  • No social preview image

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

  • No XML sitemap

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 264 internal links, 69 external

    The homepage links to 264 pages on hcde-texas.org and 69 external pages.

5 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “Home - HCDE offers quality educational resources and services to learners, teachers and districts in Harris County and …”.

  • One H1 headline

    Your main headline reads: “Home”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Home - Harris County Department of Education”.

  • Canonical URL set

    The canonical URL is https://www.hcde-texas.org/.

  • 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://www.hcde-texas.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,925 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.hcde-texas.org/scholastic-art-writing-awards, whose canonical is https://www.hcde-texas.org/scholastic-art-writing-awards/2027-scholastic-awards. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.hcde-texas.org/early-childhood-conference/overview has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.hcde-texas.org/scholastic-art-writing-awards took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 7397
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    56 of 61 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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,374 words of copy

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Apply Today!” and “Learn More About HCDE”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Head Start”, “Contact Us” and “Coolwood Head Start Project Updates”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • 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 Tag Manager, Microsoft Clarity and Cloudflare Web 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
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 1 of them by other companies (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.

  • 30 other companies contacted

    Loading the homepage contacts 30 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 hcde-texas.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on hcde-texas.org, including 23 speed issues, 4 SEO issues and 1 conversion gap. 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