Website review, no card needed

moesc.org logo

moesc.org website review

Visit site (opens in a new tab)Reviewed 20 October 202644 issues · 90 checks

This review found 44 issues worth fixing on moesc.org, 19 of them high impact, across 90 checks. The most urgent: page weight: 364.4 MB in 168 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

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.1 sMay 2Oct 32.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.6 s
Jun 13, 20262.5 s
Jun 27, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.3 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
96 ms87 msSep 5Sep 2689 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 202695 ms
Sep 12, 202688 ms
Sep 19, 202689 ms
Sep 26, 202689 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 moesc.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. moesc.org at 1.4 s1.4 s
  2. moesc.org at 2.9 s2.9 s
  3. moesc.org at 4.3 s4.3 s
  4. moesc.org at 5.8 s5.8 s
  5. moesc.org at 7.2 s7.2 s
  6. moesc.org at 8.6 s8.6 s
  7. moesc.org at 10.1 s10.1 s
  8. moesc.org at 11.5 s11.5 s

Speed

15 to fix10
  • Use efficient cache lifetimes

    6.9 s · 1.2 MB

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

  • Reduce unused JavaScript

    4.4 s · 971 KiB

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

  • Render-blocking requests

    3.1 s

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

  • audioeye.com adds 2.2 s

    2.2 s

    audioeye.com costs a phone 2.2 s of main-thread work and 351 KiB 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.

  • Main-thread work: 10.5 s

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

  • Mobile performance score: 10

    10/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye.com, finalsite.com and Google Tag Manager and others), adding 363.6 MB and 3.2 s of main-thread time.

  • finalsite.net adds 0 ms

    0 ms

    finalsite.net costs a phone 0 ms of main-thread work and 361.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.

  • 17 long tasks on the main thread

    17 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

  • Improve image delivery

    650 ms · 292 KiB

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

  • Reduce unused CSS

    600 ms · 115 KiB

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

  • finalsite.com adds 414 ms

    414 ms

    finalsite.com costs a phone 414 ms of main-thread work and 321 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.

  • Google Tag Manager adds 305 ms

    305 ms

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

  • Font display

    300 ms

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

  • juicer.io adds 52 ms

    52 ms

    juicer.io costs a phone 52 ms of main-thread work and 347 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 · 44 KiB

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

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

    9 ms

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

Core Web Vitals

7 to fix13
  • First Contentful Paint: 8.7 s

    8.7 s

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

  • Largest Contentful Paint: 1016.8 s

    1016.8 s

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

  • Speed Index: 18.1 s

    18.1 s

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

  • Time to Interactive: 1112.2 s

    1112.2 s

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

  • Total Blocking Time: 2.6 s

    2.6 s

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

  • Cumulative Layout Shift: 0.325

    0.325

    The layout shifts by 0.325 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

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

Images and page weight

2 to fix60
  • Page weight: 364.4 MB in 168 requests

    364.4 MB

    Your homepage downloads 364.4 MB in 168 requests on a phone: images 349.4 MB (96), media 12.6 MB (1) and scripts 1.7 MB (25). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    59 KiB

    1 image is downloaded at several times the size a phone draws it, for example 36130935 at 1,200 px wide, shown at 328 px. Resized copies would save about 59 KiB.

  • 2 images in older formats

    2 images (220 KiB) 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.

  • 1 image below the first screen load straight away

    1 image further down the page (180 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 103.3 g of CO₂ per visit

    103.27 g

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

Accessibility

9 to fixGoogle 8989
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 33 images without alt text

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

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

    All page content should be contained by landmarks: 4 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 marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

  • 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
  • 49 automated accessibility rules passed

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

SEO

5 to fixGoogle 9282
  • 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 (53 characters)

    Your meta description is only 53 characters: “Home - Monmouth-Ocean Educational Services Commission”. 70 to 160 characters is enough to sell the click.

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

  • 6 links with vague text

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

  • No X (Twitter) card tag

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

  • 130 internal links, 44 external

    The homepage links to 130 pages on moesc.org and 44 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Home”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Home - Monmouth-Ocean Educational Services Commission”.

  • Canonical URL set

    The canonical URL is https://www.moesc.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.moesc.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 (768 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 3 pages slow to respond

    https://www.moesc.org/moesc/mission-vision/2026-27-district-goals, https://www.moesc.org/moesc/meet-the-moesc-team and https://www.moesc.org/transportation-services/contact-us took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 14 pages that loaded have a <title>.

Best practices

1 to fix93
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://wsv3cdn.audioeye.com/static-scripts/v2/2026-10-19b/compliance.css' from origin 'ht…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    12 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

    The homepage carries about 402 words of visible text.

5 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “Contact Us”, “Fee Schedule(opens in new window/tab)” and “LEARN MORE”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager 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
  • 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.

  • 8 cookies set on arrival

    8

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on moesc.org, including 22 speed issues, 5 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