Website review, no card needed
bera.ai website review
Visit site (opens in a new tab)Reviewed 22 October 202643 issues · 93 checks
This review found 43 issues worth fixing on bera.ai, 14 of them high impact, across 93 checks. The most urgent: page weight: 76.0 MB in 234 requests. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.5 s |
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 107 ms |
| May 9, 2026 | 107 ms |
| May 16, 2026 | 102 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 108 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 132 ms |
| Jul 18, 2026 | 132 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 130 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 118 ms |
| Sep 19, 2026 | 118 ms |
| Sep 26, 2026 | 100 ms |
| Oct 3, 2026 | 111 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 136 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
Reduce unused JavaScript
3.3 s · 834 KiBAbout 834 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
2.1 s33 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 86). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
4.2 MB7 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Drift and navattic.com and others), adding 2.0 MB and 969 ms of main-thread time.
Google Tag Manager adds 441 ms
441 msGoogle Tag Manager costs a phone 441 ms of main-thread work and 638 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.
Drift adds 343 ms
343 msDrift costs a phone 343 ms of main-thread work and 813 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.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 275 ms. During a long task the page ignores taps.
navattic.com adds 117 ms
117 msnavattic.com costs a phone 117 ms of main-thread work and 493 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Use efficient cache lifetimes
150 ms · 49 KiB8 files are served with short cache lifetimes, so returning visitors download them again (49 KiB).
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 86 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.
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: 5 ms
5 msYour server sent the HTML in 5 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.
Largest Contentful Paint: 28.5 s
28.5 sYour largest element takes 28.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Brand Intelligence Built for Business Growth. Every brand c…”.
Time to Interactive: 31.9 s
31.9 sThe page becomes fully interactive after 31.9 s. Good is under 3.8 s.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.5 s
5.5 sThe first text or image appears after 5.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 457 ms
457 msScripts block taps and scrolling for 457 ms in total while the page loads. Good is under 200 ms.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 107 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 139 ms
139 msReal visitors wait 139 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 76.0 MB in 234 requests
76.0 MBYour homepage downloads 76.0 MB in 234 requests on a phone: media 68.9 MB (13), images 4.4 MB (42) and scripts 2.2 MB (100). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
4.1 MB5 images are downloaded at several times the size a phone draws them, for example BERA_Testimonials_Chime.webp at 13,022 px wide, shown at 355 px. Resized copies would save about 4.1 MB.
6 images below the first screen load straight away
6 images further down the page (4.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 21.5 g of CO₂ per visit
21.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 21.53 g of CO₂e: 2583.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo 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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h4 → h6, h1 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 39 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 4 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 long (81 characters)
Your title is 81 characters, so Google will cut it off around 60: “Brand Management Tracking Software | Advanced Brand Tracking Solutions by BERA.ai”.
12 links with vague text
12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
102 internal links, 21 external
The homepage links to 102 pages on bera.ai and 21 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Know Your Brand Impact–Everywhere That Matters to You.”.
Canonical URL set
The canonical URL is https://bera.ai/.
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://bera.ai/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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://bera.ai/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,164 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://bera.ai/competitive-intelligence and https://bera.ai/brand-resources have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://bera.ai/brand-resources and https://bera.ai/about have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://bera.ai/conversion-funnel took over 3 s to send its HTML from our server.
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
1 JavaScript error while loading
1 error was 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
27 of 33 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 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 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 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 910 words of copy
The homepage carries about 910 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Subscribe”.
22 calls to action
The homepage has 22 calls to action, for example “Contact”, “Subscribe” and “Request Demo”.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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 LinkedIn Insight (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
27 other companies contacted
Loading the homepage contacts 27 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 bera.ai, 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 Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on bera.ai, including 20 speed issues, 4 SEO issues and 2 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.