Website review, no card needed
mahanaim.com website review
Visit site (opens in a new tab)Reviewed 1 November 202639 issues · 76 checks
This review found 39 issues worth fixing on mahanaim.com, 9 of them high impact, across 76 checks. The most urgent: wix adds 1.2 s. 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
70CClosest competitors among Wix websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.5 s
1.9 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Wix adds 1.2 s
1.2 sWix costs a phone 1.2 s of main-thread work and 8.6 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.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Wix, powrcdn.com and Google Maps and others), adding 10.0 MB and 1.8 s of main-thread time.
Reduce unused JavaScript
300 ms · 907 KiBAbout 907 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
656 KiB10 files are served with short cache lifetimes, so returning visitors download them again (656 KiB).
Reduce unused CSS
430 KiBAbout 430 KiB of CSS is downloaded but never applied on this page.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 297 ms. During a long task the page ignores taps.
powrcdn.com adds 215 ms
215 mspowrcdn.com costs a phone 215 ms of main-thread work and 566 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 Maps adds 150 ms
150 msGoogle Maps costs a phone 150 ms of main-thread work and 440 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.
Duplicated JavaScript
32 KiB32 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 57 ms
57 msYour server sent the HTML in 57 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 26.5 s
26.5 sThe page becomes fully interactive after 26.5 s. Good is under 3.8 s.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Speed Index: 4.7 s
4.7 sVisually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 11.3 MB in 329 requests
11.3 MBYour homepage downloads 11.3 MB in 329 requests on a phone: images 4.7 MB (43), scripts 2.8 MB (146) and media 1.9 MB (1). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Library Books.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 3.2 g of CO₂ per visit
3.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.21 g of CO₂e: 384.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate 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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 21 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
14 H1 headlines
There are 14 <h1> headlines (“Higher-Powered Music Education”, “Higher-Powered Music Education” and “Higher-Powered Music Education”). One clear main headline is easier for people and search engines.
Meta description is long (294 characters)
Your meta description is 294 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (LocalBusiness and WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
112 internal links, 7 external
The homepage links to 112 pages on mahanaim.com and 7 external pages.
4 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “Mahanaim l Music Institute in New York”.
Canonical URL set
The canonical URL is https://www.mahanaim.com/.
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://www.mahanaim.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
llms.txt published
The site publishes https://www.mahanaim.com/llms.txt (3 KiB, 3 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.mahanaim.com/ourfaculty has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.mahanaim.com/bursar 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 31 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
9 third-party cookies
9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
8 small tap targets
8 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.
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
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 41 words
The homepage has only about 41 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
28 calls to action
The homepage has 28 calls to action, for example “How to Apply”, “Contact Us” and “Learn More”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
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.
9 other companies contacted
Loading the homepage contacts 9 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 mahanaim.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
- Wix
- Framework
- React
- Hosting
- Wix
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on mahanaim.com, including 15 speed issues, 5 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.