mbacs.org website review

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

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

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

10 images could be 808 KiB 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.

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

126 KiB could be saved by minifying JavaScript.

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

4 third-party services load with your homepage (Other Google APIs/SDKs, Google CDN and Google Fonts and others), adding 309 KiB and 100 ms of main-thread time.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 5.5 MB in 96 requests on a phone: media 3.0 MB (1), images 1.5 MB (43) and scripts 780 KiB (21). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (398 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example parent_cafe_(5).jpg at 773 px wide, shown at 220 px. Resized copies would save about 79 KiB.

4 images (398 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.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Your meta description is only 39 characters: “Mariana Bracetti Academy Charter School”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 71 pages on mbacs.org and 13 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

There is no https://www.mbacs.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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Your homepage links to https://www.mbacs.org/mbaupcomingevents, which answers with an error. Visitors hit a dead end and search engines drop it.

/ and https://www.mbacs.org/apps/pages/index.jsp all use the title “Mariana Bracetti Academy Charter School”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mbacs.org/AboutUs, https://www.mbacs.org/BracettiBoardofTrustees, https://www.mbacs.org/BracettiCareers, https://www.mbacs.org/BracettiCompPlan, https://www.mbacs.org/BracettiStaff and https://www.mbacs.org/BracettiMission and 8 others use the same meta description. A description written for each page earns more clicks.

https://www.mbacs.org/apps/album and https://www.mbacs.org/apps/pages/index.jsp have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 460 words of visible text.

Opening the homepage sets 2 cookies (measured from a US location before any click).

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.

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