Website review, no card needed

academytexas.com logo

academytexas.com website review

Visit site (opens in a new tab)Reviewed 17 November 202627 issues · 78 checks

This review found 27 issues worth fixing on academytexas.com, 6 of them high impact, across 78 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

Full-page screenshot of academytexas.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix57
  • Reduce unused JavaScript

    1.9 s · 315 KiB

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

  • Use efficient cache lifetimes

    850 ms · 229 KiB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    850 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 827 KiB and 665 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 30 KiB

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

  • Google Tag Manager adds 256 ms

    256 ms

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 20 KiB

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

  • Improve image delivery

    10 KiB

    1 image could be 10 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix58
  • Largest Contentful Paint: 9.7 s

    9.7 s

    Your largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TEXAS REAL ESTATE CE YOU CAN FINISH TONIGHT Texas Real Esta…”.

  • Time to Interactive: 9.7 s

    9.7 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Total Blocking Time: 349 ms

    349 ms

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

  • 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

100
  • About 0.3 g of CO₂ per visit

    0.32 g

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

4 checks passed
  • Page weight: 1.1 MB in 63 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 63 requests on a phone: scripts 904 KiB (30), stylesheets 99 KiB (21) and images 67 KiB (6). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9395
  • 29 text elements with low contrast

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

  • Links must have discernible text (3 elements)

    Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 44 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: 44 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (BreadcrumbList, EducationalOrganization, FAQPage and ImageObject) but with 1 problem, for example “Service: no offers (price) block”.

  • 1 link crawlers can't follow

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

  • 39 internal links, 5 external

    The homepage links to 39 pages on academytexas.com and 5 external pages.

7 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Texas real estate CE that posts to TREC in 3 seconds. Finish at 11pm, renew at 11:01. 18-hour renewal from $75. No-ques…”.

  • One H1 headline

    Your main headline reads: “Texas Real Estate Continuing Education Online”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Texas Real Estate CE Online | Instant TREC Posting | TREA”.

  • Canonical URL set

    The canonical URL is https://academytexas.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://academytexas.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

5 to fix76
  • 2 pages share a title

    https://academytexas.com/real-estate-courses and https://academytexas.com/courses-2 all use the title “Texas Real Estate CE Courses: All 18 Hours for $75”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://academytexas.com/instructors has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://academytexas.com/real-estate-courses and https://academytexas.com/courses-2 use the same meta description. A description written for each page earns more clicks.

  • 8 links to non-canonical URLs

    Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://academytexas.com/faq, whose canonical is https://academytexas.com/trea-faq. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://academytexas.com/trea-contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://academytexas.com/course-renewal and https://academytexas.com/dmca took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    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 ()”.

  • 1 low-resolution image

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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 direct contact details

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

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 932 words of copy

    The homepage carries about 932 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start My CE Tonight”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Start My CE Tonight” and “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

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

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on academytexas.com, including 12 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