Website review, no card needed
ama.bzh website review
Visit site (opens in a new tab)Reviewed 20 October 202631 issues · 69 checks
This review found 31 issues worth fixing on ama.bzh, 12 of them high impact, across 69 checks. The most urgent: google Tag Manager 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 7.5 s |
| May 9, 2026 | 6.6 s |
| May 16, 2026 | 6.5 s |
| May 23, 2026 | 6.3 s |
| May 30, 2026 | 6.3 s |
| Jun 6, 2026 | 6.5 s |
| Jun 13, 2026 | 6.6 s |
| Jun 20, 2026 | 6.9 s |
| Jun 27, 2026 | 6.9 s |
| Jul 4, 2026 | 6.9 s |
| Jul 11, 2026 | 6.6 s |
| Jul 18, 2026 | 6.2 s |
| Jul 25, 2026 | 5.9 s |
| Aug 1, 2026 | 5.7 s |
| Aug 8, 2026 | 5.6 s |
| Aug 15, 2026 | 5.9 s |
| Aug 22, 2026 | 5.8 s |
| Aug 29, 2026 | 5.8 s |
| Sep 5, 2026 | 5.7 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 5.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 362 ms |
| May 9, 2026 | 373 ms |
| May 16, 2026 | 372 ms |
| May 23, 2026 | 362 ms |
| May 30, 2026 | 371 ms |
| Jun 6, 2026 | 367 ms |
| Jun 13, 2026 | 366 ms |
| Jun 20, 2026 | 372 ms |
| Jun 27, 2026 | 341 ms |
| Jul 4, 2026 | 344 ms |
| Jul 11, 2026 | 344 ms |
| Jul 18, 2026 | 346 ms |
| Jul 25, 2026 | 358 ms |
| Aug 1, 2026 | 365 ms |
| Aug 8, 2026 | 372 ms |
| Aug 15, 2026 | 373 ms |
| Aug 22, 2026 | 378 ms |
| Aug 29, 2026 | 385 ms |
| Sep 12, 2026 | 385 ms |
| Sep 19, 2026 | 374 ms |
| Sep 26, 2026 | 323 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.4 s
8.8 s
10.3 s
11.8 s
Speed
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 1.3 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: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 3.0 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 (Google Tag Manager, hsappstatic.net and Google CDN and others), adding 3.0 MB and 2.2 s of main-thread time.
hsappstatic.net adds 421 ms
421 mshsappstatic.net costs a phone 421 ms of main-thread work and 694 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 CDN adds 364 ms
364 msGoogle CDN costs a phone 364 ms of main-thread work and 739 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
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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: 140 ms
140 msYour server sent the HTML in 140 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.0 s
5.0 sReal visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.6 s
4.6 sReal visitors see the first content after 4.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.154
0.154The layout shifts by 0.154 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 362 ms to 323 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 31% faster for real visitors
-31%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 7.5 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.6 MB in 184 requests
5.6 MBYour homepage downloads 5.6 MB in 184 requests on a phone: scripts 3.0 MB (48), images 1.5 MB (42) and other files 390 KiB (47). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
test-video-record-768x499.png weighs 555 KiB. On a phone connection a single image that size takes seconds.
5 images in older formats
5 images (1.4 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.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
68 KiB1 image is downloaded at several times the size a phone draws it, for example WEB-RVB-AMA-TAGLINE-AI-scaled.png at 2,560 px wide, shown at 90 px. Resized copies would save about 68 KiB.
About 1.6 g of CO₂ per visit
1.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 190.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
24 links without text
24 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.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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 meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (19 characters)
Your title is only 19 characters: “Home - AMA XpertEye”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“Home” and “XpertEye”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
13 links with vague text
13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
70 internal links, 18 external
The homepage links to 70 pages on ama.bzh and 18 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.amaxperteye.com/.
Structured data in place
Structured data found: BreadcrumbList, SoftwareApplication, WebPage and WebSite.
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.amaxperteye.com/sitemap_index.xml.
AI search readiness
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://www.amaxperteye.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.
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 (753 words), so crawlers that don't run JavaScript still read it.
Other pages
13 pages without a meta description
https://www.amaxperteye.com/collaborate-with-xperteye, https://www.amaxperteye.com/live-translation, https://www.amaxperteye.com/collect-relevant-data-with-xperteye, https://www.amaxperteye.com/thermal-camera-module-within-xperteye-and-realwear, https://www.amaxperteye.com/compatible-devices and https://www.amaxperteye.com/professional-services-2 and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://www.amaxperteye.com/compatible-devices has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
6 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.
Every page has an H1
Each page we checked has a main headline.
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
3 broken images
3 images failed to load on a phone, for example https://www.swaytheme.com/wp-content/uploads/sites/3/2020/08/App_Store.png.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 29 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 710 words of copy
The homepage carries about 710 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start Free Trial”.
12 calls to action
The homepage has 12 calls to action, for example “Join us”, “Contact us” and “Request a demo”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Microsoft Ads (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
28 other companies contacted
Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 ama.bzh, 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
Hiring
- Hiring
- 3 open roles
- Teams
- Agentic Compliance (1), Engineering (1), GTM (1)
- Job board
- ashby
- Careers page
- jobs.ashbyhq.com/ama (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on ama.bzh, including 11 speed issues, 5 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.