Website review, no card needed
bmacapital.com website review
Visit site (opens in a new tab)Reviewed 4 November 202634 issues · 61 checks
This review found 34 issues worth fixing on bmacapital.com, 13 of them high impact, across 61 checks. The most urgent: main-thread work: 11.7 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 5.3 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.2 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.5 s |
| Aug 22, 2026 | 5.5 s |
| Aug 29, 2026 | 5.6 s |
| Sep 5, 2026 | 5.6 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 5.7 s |
| Sep 26, 2026 | 5.6 s |
| Oct 3, 2026 | 5.7 s |
| Oct 10, 2026 | 5.6 s |
| Oct 17, 2026 | 5.3 s |
| Oct 24, 2026 | 5.1 s |
| Oct 31, 2026 | 5.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 270 ms |
| May 23, 2026 | 279 ms |
| May 30, 2026 | 280 ms |
| Jun 6, 2026 | 271 ms |
| Jun 13, 2026 | 265 ms |
| Jun 20, 2026 | 269 ms |
| Jun 27, 2026 | 260 ms |
| Jul 4, 2026 | 277 ms |
| Jul 11, 2026 | 279 ms |
| Jul 18, 2026 | 268 ms |
| Jul 25, 2026 | 287 ms |
| Aug 1, 2026 | 288 ms |
| Aug 8, 2026 | 285 ms |
| Aug 15, 2026 | 278 ms |
| Aug 22, 2026 | 258 ms |
| Aug 29, 2026 | 256 ms |
| Sep 5, 2026 | 249 ms |
| Sep 12, 2026 | 251 ms |
| Sep 19, 2026 | 266 ms |
| Sep 26, 2026 | 248 ms |
| Oct 3, 2026 | 251 ms |
| Oct 10, 2026 | 249 ms |
| Oct 17, 2026 | 249 ms |
| Oct 24, 2026 | 245 ms |
| Oct 31, 2026 | 255 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
How it loaded on a phone
1.5 s
2.9 s
4.4 s
5.9 s
7.3 s
8.8 s
10.3 s
11.7 s
Speed
Main-thread work: 11.7 s
A phone's processor spends 11.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,546 HTML elements
The page has 4,546 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
300 ms · 3.4 MB7 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 151 KiBAbout 151 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 609 KiB15 files are served with short cache lifetimes, so returning visitors download them again (609 KiB).
Render-blocking requests
400 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 400 ms.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 130 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.
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: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user LCP: 5.5 s
5.5 sReal visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.7 s
4.7 sReal visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Alert”. Most of its time is resource load duration (9.2 s).
Real-user INP: 278 ms
278 msReal visitors wait 278 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 5.3 s
5.3 sThe page becomes fully interactive after 5.3 s. Good is under 3.8 s.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 270 ms to 255 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.8 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Total Blocking Time: 132 ms
132 msScripts block the page for only 132 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.018
0.018The layout barely moves while loading (CLS 0.018, good is under 0.1).
First Contentful Paint: 1.0 s
1.0 sThe first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 6.0 MB in 43 requests
6.0 MBYour homepage downloads 6.0 MB in 43 requests on a phone: images 5.7 MB (33), scripts 285 KiB (1) and other files 50 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 204.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
All page content should be contained by landmarks (51 elements)
All page content should be contained by landmarks: 51 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://bmacapital.com/sitemap.xml, so Google discovers your pages only by following links.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
4 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “BMA Capital - Advanced trading platform for stocks, options, and futures with powerful tools for investors of all level…”.
Title: 39 characters
Your title is a healthy 39 characters: “BMA Capital - Advanced Trading Platform”.
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.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 588 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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://bmacapital.com/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.
1 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.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
6 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 588 words of copy
The homepage carries about 588 words of visible text.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start Your Investment Journey”.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 bmacapital.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Hetzner
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on bmacapital.com, including 16 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.