Website review, no card needed
olmca.org website review
Visit site (opens in a new tab)Reviewed 24 October 202642 issues · 84 checks
This review found 42 issues worth fixing on olmca.org, 18 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
7.5 s · 9.8 MB134 files are served with short cache lifetimes, so returning visitors download them again (9.8 MB).
Improve image delivery
3.1 s · 5.0 MB22 images could be 5.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.
Reduce unused JavaScript
7.0 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.
Render-blocking requests
2.7 s24 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.7 s.
Minify JavaScript
1.5 s · 235 KiB235 KiB could be saved by minifying JavaScript.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 73). 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 (Google Tag Manager, Facebook and Cloudflare CDN and others), adding 5.5 MB and 507 ms of main-thread time.
Instagram adds 0 ms
0 msInstagram costs a phone 0 ms of main-thread work and 4.1 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.
Google Tag Manager adds 286 ms
286 msGoogle Tag Manager costs a phone 286 ms of main-thread work and 495 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 Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 406 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 149 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 73 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 657 ms of it running JavaScript. That is comfortably low.
Server response: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.9 s
9.9 sThe first text or image appears after 9.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 30.3 s
30.3 sYour largest element takes 30.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “null”.
Time to Interactive: 31.1 s
31.1 sThe page becomes fully interactive after 31.1 s. Good is under 3.8 s.
Speed Index: 12.0 s
12.0 sVisually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.2
0.2The layout shifts by 0.2 while loading, so content jumps under the reader's thumb. Good is under 0.1.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
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
Total Blocking Time: 120 ms
120 msScripts block the page for only 120 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 29.8 MB in 215 requests
29.8 MBYour homepage downloads 29.8 MB in 215 requests on a phone: images 24.4 MB (62), scripts 2.7 MB (77) and other files 2.0 MB (23). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 17.4 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
16.4 MB6 images are downloaded at several times the size a phone draws them, for example About Us.jpg at 5,021 px wide, shown at 230 px. Resized copies would save about 16.4 MB.
9 images in older formats
9 images (17.7 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.
5 images below the first screen load straight away
5 images further down the page (7.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 8.4 g of CO₂ per visit
8.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.45 g of CO₂e: 1013.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Links must have discernible text (1 element)
Links must have discernible text: 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.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (190 characters)
Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
64 internal links, 25 external
The homepage links to 64 pages on olmca.org and 25 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Fall Open House Registration”.
Title: 32 characters
Your title is a healthy 32 characters: “Our Lady of Mount Carmel Academy”.
Structured data in place
Structured data found: EducationalOrganization.
XML sitemap found
Your XML sitemap is reachable at https://www.olmca.org/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your 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.
Some text only appears after JavaScript runs
55%The HTML your server sends has 426 of the 768 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
Organization data is thin (2 of 6 facts)
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.
No llms.txt
There is no https://olmca.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.
Opted out of AI training for 5 crawlers
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.
Other pages
9 pages share 3 titles
/, https://olmca.org/apps/pages/index.jsp, https://olmca.org/apps/pages and https://olmca.org/apps/events/event.jsp all use the title “Our Lady of Mount Carmel Academy”, and 2 other titles repeat too. 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://olmca.org/apps/events/view_calendar.jsp has no meta description, so Google writes the search snippet from whatever text it finds.
9 pages share a meta description
https://olmca.org/apps/pages/index.jsp, https://olmca.org/apps/staff, https://olmca.org/apps/pages, https://olmca.org/apps/events, https://olmca.org/apps/events/event.jsp and https://olmca.org/apps/events/index.jsp and 3 others use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://olmca.org/apps/pages/index.jsp, https://olmca.org/apps/pages and https://olmca.org/apps/maps have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://olmca.org/apps/pages/index.jsp, https://olmca.org/apps/pages, https://olmca.org/apps/events/event.jsp and https://olmca.org/apps/news/show_news.jsp have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 11 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
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 429 (Too Many Requests)”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
58 of 66 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 768 words of copy
The homepage carries about 768 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: “APPLY” and “SCHEDULE A VISIT”.
3 calls to action
The homepage has 3 calls to action, for example “Apply”, “Schedule a Visit” and “contact us”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
18 other companies contacted
Loading the homepage contacts 18 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 olmca.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on olmca.org, including 16 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.