Website review, no card needed

harrisburgacademy.org logo

harrisburgacademy.org website review

Visit site (opens in a new tab)Reviewed 23 October 202653 issues · 96 checks

This review found 53 issues worth fixing on harrisburgacademy.org, 19 of them high impact, across 96 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
1.8 s1.3 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.6 s
Aug 15, 20261.5 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
127 ms76 msMay 2Oct 17117 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202687 ms
May 9, 202694 ms
May 16, 202688 ms
May 23, 202691 ms
May 30, 2026100 ms
Jun 6, 202691 ms
Jun 13, 202691 ms
Jun 20, 202689 ms
Jun 27, 202682 ms
Jul 4, 202688 ms
Jul 11, 202687 ms
Jul 18, 202688 ms
Jul 25, 202692 ms
Aug 1, 202693 ms
Aug 8, 2026102 ms
Aug 15, 2026102 ms
Aug 22, 2026102 ms
Aug 29, 2026103 ms
Sep 5, 2026103 ms
Sep 12, 2026103 ms
Sep 19, 2026105 ms
Sep 26, 2026106 ms
Oct 3, 2026113 ms
Oct 10, 2026121 ms
Oct 17, 2026117 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 harrisburgacademy.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. harrisburgacademy.org at 1.0 s1.0 s
  2. harrisburgacademy.org at 1.9 s1.9 s
  3. harrisburgacademy.org at 2.9 s2.9 s
  4. harrisburgacademy.org at 3.9 s3.9 s
  5. harrisburgacademy.org at 4.9 s4.9 s
  6. harrisburgacademy.org at 5.8 s5.8 s
  7. harrisburgacademy.org at 6.8 s6.8 s
  8. harrisburgacademy.org at 7.8 s7.8 s

Speed

11 to fix30
  • Reduce unused JavaScript

    6.2 s · 1.7 MB

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

  • Render-blocking requests

    1.6 s

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

  • YouTube adds 1.2 s

    1.2 s

    YouTube costs a phone 1.2 s of main-thread work and 1.9 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. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.1 s

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

  • Improve image delivery

    250 ms · 20.4 MB

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

  • 8 third-party services on the page

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

  • Google Tag Manager adds 876 ms

    876 ms

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

  • Use efficient cache lifetimes

    300 ms · 316 KiB

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

  • myschoolapp.com adds 476 ms

    476 ms

    myschoolapp.com costs a phone 476 ms of main-thread work and 435 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 311 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    150 ms · 30 KiB

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

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • First Contentful Paint: 9.4 s

    9.4 s

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

  • Largest Contentful Paint: 30.2 s

    30.2 s

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

  • Time to Interactive: 60.4 s

    60.4 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user CLS: 0.17

    0.17

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

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

    +31%

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

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

    +23%

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

  • 20 images without width and height

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 111 ms

    111 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 737 ms

    737 ms

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

  • Cumulative Layout Shift: 0.096

    0.096

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

Images and page weight

5 to fix18
  • Page weight: 29.1 MB in 155 requests

    29.1 MB

    Your homepage downloads 29.1 MB in 155 requests on a phone: images 25.3 MB (44), scripts 3.2 MB (44) and stylesheets 250 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 15.1 MB together. On a phone connection a single image that size takes seconds.

  • 11 images far larger than shown

    7.1 MB

    11 images are downloaded at several times the size a phone draws them, for example orig_photo2117987_10922747.gif at 1,440 px wide, shown at 350 px. Resized copies would save about 7.1 MB.

  • 18 images in older formats

    18 images (16.1 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.

  • 18 images below the first screen load straight away

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

  • About 8.2 g of CO₂ per visit

    8.25 g

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

Accessibility

8 to fixGoogle 8288
  • Input buttons must have discernible text (2 elements)

    Input buttons must have discernible text: 2 elements on the page fail this check, rated critical by axe-core.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 2 tap targets too small

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail 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).

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

7 to fixGoogle 7769
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Private & Independent Schools in Harrisburg, PA | Harrisburg Academy”.

  • Meta description is long (170 characters)

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

  • 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://www.harrisburgacademy.org/sitemap.xml, so Google discovers your pages only by following links.

  • 16 links crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 156 internal links, 27 external

    The homepage links to 156 pages on harrisburgacademy.org and 27 external pages.

3 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: EducationalOrganization, ElementarySchool, HighSchool, MiddleSchool and Preschool.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.harrisburgacademy.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 (700 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix62
  • 1 page without a title

    https://www.harrisburgacademy.org/app has no <title>, so Google invents the link text in results.

  • 6 pages share 3 titles

    https://www.harrisburgacademy.org/admission and https://www.harrisburgacademy.org/admission/why-choose-harrisburg-academy all use the title “Private Elementary Middle & High School Harrisburg, PA | Harrisburg A…”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.harrisburgacademy.org/app, https://www.harrisburgacademy.org/admission/applying, https://www.harrisburgacademy.org/admission/contact-us--directions, https://www.harrisburgacademy.org/admission/admissions-events and https://www.harrisburgacademy.org/admission/re-enrollment have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://www.harrisburgacademy.org/admission and https://www.harrisburgacademy.org/admission/why-choose-harrisburg-academy 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://www.harrisburgacademy.org/admission, whose canonical is https://www.harrisburgacademy.org/admission/why-choose-harrisburg-academy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.harrisburgacademy.org/app has 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 51 found) and read each the way a search engine does.

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

Best practices

3 to fixGoogle 3188
  • 6 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.harrisburgacademy.org/' was loaded over HTTPS, but requested an insecure script…”.

  • 5 low-resolution images

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

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • 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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 440 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: “REQUEST INFORMATION”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Apply Now”, “Contact Us & Directions” and “Request Information”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 1 of them by other companies (measured from a US location before any click).

  • 36 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 harrisburgacademy.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 | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on harrisburgacademy.org, including 21 speed issues, 7 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