Website review, no card needed
bttcorp.com website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 76 checks
This review found 38 issues worth fixing on bttcorp.com, 13 of them high impact, across 76 checks. The most urgent: improve image delivery. 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 sideShow as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 150 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 144 ms |
| Oct 31, 2026 | 127 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
Speed
Improve image delivery
23.1 s · 5.0 MB6 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 23.1 s faster on a phone.
Render-blocking requests
1.5 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Reduce unused JavaScript
840 ms · 173 KiBAbout 173 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 840 ms faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 320 ms
320 msGoogle Tag Manager costs a phone 320 ms of main-thread work and 198 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 281 ms. During a long task the page ignores taps.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 856 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, AddToAny and Google Fonts and others), adding 374 KiB and 340 ms of main-thread time.
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.
Use efficient cache lifetimes
1 KiB1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).
1 checks passed
Server response: 31 ms
31 msYour server sent the HTML in 31 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 34.0 s
34.0 sYour largest element takes 34.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Smiling man with a transparent visualization of brain therm…”.
Time to Interactive: 34.4 s
34.4 sThe page becomes fully interactive after 34.4 s. Good is under 3.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 284 ms
284 msScripts block taps and scrolling for 284 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.076
0.076The layout barely moves while loading (CLS 0.076, good is under 0.1).
Images and page weight
Page weight: 8.6 MB in 67 requests
8.6 MBYour homepage downloads 8.6 MB in 67 requests on a phone: images 6.1 MB (9), media 1.9 MB (1) and scripts 456 KiB (23). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
2.0 MB2 images are downloaded at several times the size a phone draws them, for example hero-woman-brain-v2.png at 1,672 px wide, shown at 390 px. Resized copies would save about 2.0 MB.
5 images in older formats
5 images (5.3 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.
3 images below the first screen load straight away
3 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.45 g of CO₂e: 294.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (29 elements)
All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (15 characters)
Your title is only 15 characters: “Home - btt Corp”. Between 30 and 65 characters leaves room to say what you do and for whom.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
41 internal links, 0 external
The homepage links to 41 pages on bttcorp.com and 0 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Advancing thefuture of healththrough brain thermodynamics”.
Canonical URL set
The canonical URL is https://bttcorp.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://bttcorp.com/sitemap_index.xml.
AI search readiness
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.
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (743 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bttcorp.com/llms.txt (2 KiB, 13 links), a plain-text guide to the site for AI tools.
Other pages
12 pages share 6 titles
/ and https://bttcorp.com/br all use the title “Home - btt Corp”, and 5 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://bttcorp.com/about, https://bttcorp.com/marc-abreu, https://bttcorp.com/medical-institute, https://bttcorp.com/wellness, https://bttcorp.com/research and https://bttcorp.com/media and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://bttcorp.com/terms and https://bttcorp.com/privacy use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example //contact, whose canonical is https://bttcorp.com/contact. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
//contact and https://bttcorp.com/contact have 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 17 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
10 of 12 tappable elements near the top are at least 24 px.
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.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 544 words of copy
The homepage carries about 544 words of visible text.
2 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Learn More” and “Contact btt”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
8 other companies contacted
Loading the homepage contacts 8 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 bttcorp.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Akamai Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on bttcorp.com, including 12 speed issues, 4 SEO issues and 5 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.