Website review, no card needed

musical.engineering logo

musical.engineering website review

Visit site (opens in a new tab)Reviewed 21 November 202639 issues · 77 checks

This review found 39 issues worth fixing on musical.engineering, 13 of them high impact, across 77 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

Full-page screenshot of musical.engineering (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. musical.engineering at 0.4 s0.4 s
  2. musical.engineering at 0.8 s0.8 s
  3. musical.engineering at 1.1 s1.1 s
  4. musical.engineering at 1.5 s1.5 s
  5. musical.engineering at 1.9 s1.9 s
  6. musical.engineering at 2.3 s2.3 s
  7. musical.engineering at 2.6 s2.6 s
  8. musical.engineering at 3.0 s3.0 s

Speed

11 to fix48
  • Reduce unused JavaScript

    7.4 s · 902 KiB

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

  • Improve image delivery

    1.3 s · 3.5 MB

    8 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48. 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 CDN, Google Tag Manager and kajabi-cdn.com and others), adding 8.7 MB and 1.2 s of main-thread time.

  • kajabi-cdn.com adds 147 ms

    147 ms

    kajabi-cdn.com costs a phone 147 ms of main-thread work and 6.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.

  • Use efficient cache lifetimes

    600 ms · 116 KiB

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

  • Google CDN adds 591 ms

    591 ms

    Google CDN costs a phone 591 ms of main-thread work and 1.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.

  • Minify JavaScript

    300 ms · 71 KiB

    71 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 306 ms

    306 ms

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

    300 ms · 18 KiB

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

  • Main-thread work: 2.7 s

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

  • Reduce unused CSS

    150 ms · 35 KiB

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

  • Render-blocking requests

    150 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • 15 long tasks on the main thread

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 85 ms

    85 ms

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

Core Web Vitals

6 to fix58
  • First Contentful Paint: 10.9 s

    10.9 s

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

  • Largest Contentful Paint: 34.4 s

    34.4 s

    Your largest element takes 34.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Master Any Guitar Riff and Play Your Favorite Songs With Co…”.

  • Time to Interactive: 35.9 s

    35.9 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • Total Blocking Time: 343 ms

    343 ms

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

  • 7 images without width and height

    7 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
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix28
  • Page weight: 9.2 MB in 78 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 78 requests on a phone: images 6.6 MB (21), scripts 2.0 MB (34) and other files 363 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    2.1 MB

    6 images are downloaded at several times the size a phone draws them, for example a0c7571-8cce-7cc8-ebdf-211dc525e37_de287586-a58e-43e0-993a-3 at 1,920 px wide, shown at 300 px. Resized copies would save about 2.1 MB.

  • 4 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (75 KiB) is 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.

  • About 2.6 g of CO₂ per visit

    2.61 g

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

Accessibility

4 to fixGoogle 8694
  • 6 text elements with low contrast

    6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 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

2 to fixGoogle 10089
  • Title is short (14 characters)

    Your title is only 14 characters: “Avi Blum Music”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 16 internal links, 4 external

    The homepage links to 16 pages on musical.engineering and 4 external pages.

6 checks passed
  • Meta description: 93 characters

    Your meta description is 93 characters: “Learn to write music and play guitar with Avi Blum through lessons, courses, and communities.”.

  • One H1 headline

    Your main headline reads: “Melody Mastery Mini Course is now LIVE!”.

  • Canonical URL set

    The canonical URL is https://www.aviblummusic.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.aviblummusic.com/sitemap.xml.

AI search readiness

2 to fix70
  • 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.

  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • 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, which the crawlers above handle.

2 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (392 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.aviblummusic.com/llms.txt (5 KiB, 43 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix76
  • 2 linked pages hidden from search

    https://www.aviblummusic.com/resource_redirect/landing_pages/2148310772 and https://www.aviblummusic.com/resource_redirect/landing_pages/2148327124 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.aviblummusic.com/blog, https://www.aviblummusic.com/resource_redirect/landing_pages/2148310772 and https://www.aviblummusic.com/resource_redirect/landing_pages/2148327124 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.aviblummusic.com/about, https://www.aviblummusic.com/contact and https://www.aviblummusic.com/privacy use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.aviblummusic.com/resource_redirect/landing_pages/2150103986, whose canonical is https://www.aviblummusic.com/free-guitar-training. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.aviblummusic.com/about, https://www.aviblummusic.com/blog and https://www.aviblummusic.com/learn have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.aviblummusic.com/learn, https://www.aviblummusic.com/resource_redirect/landing_pages/2150341588 and https://www.aviblummusic.com/contact 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.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://kajabi-storefronts-production.kajabi-cdn.com/kajabi-storefronts-production/themes/…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 300 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Book Guitar Strategy Session”, “Book Songwriting Strategy Session” and “contact”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads 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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies, 1 of them by other companies (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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 musical.engineering, 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 Analytics | Segment
Hosting
Namecheap

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 musical.engineering, including 17 speed issues, 2 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