Website review, no card needed

ahkbrasil.com logo

ahkbrasil.com website review

Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 81 checks

This review found 41 issues worth fixing on ahkbrasil.com, 19 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
2.9 s2.6 sApr 25Oct 102.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.8 s
May 2, 20262.8 s
May 9, 20262.7 s
May 16, 20262.7 s
May 23, 20262.8 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.6 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.8 s
Sep 19, 20262.9 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
145 ms120 msApr 25Oct 10132 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026128 ms
May 2, 2026132 ms
May 9, 2026135 ms
May 16, 2026130 ms
May 23, 2026140 ms
May 30, 2026133 ms
Jun 6, 2026139 ms
Jun 13, 2026142 ms
Jun 20, 2026123 ms
Jun 27, 2026129 ms
Jul 4, 2026126 ms
Jul 11, 2026130 ms
Jul 18, 2026137 ms
Jul 25, 2026126 ms
Aug 1, 2026128 ms
Aug 8, 2026127 ms
Aug 15, 2026128 ms
Aug 22, 2026130 ms
Aug 29, 2026129 ms
Sep 5, 2026130 ms
Sep 12, 2026130 ms
Sep 19, 2026135 ms
Sep 26, 2026135 ms
Oct 3, 2026129 ms
Oct 10, 2026132 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

Full-page screenshot of ahkbrasil.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ahkbrasil.com at 0.5 s0.5 s
  2. ahkbrasil.com at 1.1 s1.1 s
  3. ahkbrasil.com at 1.6 s1.6 s
  4. ahkbrasil.com at 2.1 s2.1 s
  5. ahkbrasil.com at 2.6 s2.6 s
  6. ahkbrasil.com at 3.2 s3.2 s
  7. ahkbrasil.com at 3.7 s3.7 s
  8. ahkbrasil.com at 4.2 s4.2 s

Speed

9 to fix14
  • Use efficient cache lifetimes

    24.9 s · 14.7 MB

    60 files are served with short cache lifetimes, so returning visitors download them again (14.7 MB).

  • Improve image delivery

    20.1 s · 11.8 MB

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

  • Reduce unused JavaScript

    2.4 s · 445 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 14

    14/100

    Your mobile performance score is 14 (desktop: 23). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.6 s

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

  • Reduce unused CSS

    900 ms · 178 KiB

    About 178 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 10 long tasks on the main thread

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

  • 1,722 HTML elements

    The page has 1,722 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 1 third-party service on the page

    1 third-party service load with your homepage (piwik.pro), adding 161 KiB and 96 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.

1 checks passed
  • Server response: 206 ms

    206 ms

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

Core Web Vitals

13 to fix0
  • 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 CLS: 0.98

    0.98

    For real visitors the layout shifts by 0.98 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 36.2 s

    36.2 s

    Your largest element takes 36.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cidade de São Paulo - Ponte Estaiada”.

  • Time to Interactive: 37.2 s

    37.2 s

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

  • Cumulative Layout Shift: 0.99

    0.99

    The layout shifts by 0.99 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 11.5 s

    11.5 s

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

  • Total Blocking Time: 1.0 s

    1.0 s

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

  • Real-user LCP: 2.9 s

    2.9 s

    Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 259 ms

    259 ms

    Real visitors wait 259 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.3 s

    1.3 s

    Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 17 images without width and height

    17 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 128 ms to 132 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

3 to fix53
  • Page weight: 16.3 MB in 66 requests

    16.3 MB

    Your homepage downloads 16.3 MB in 66 requests on a phone: images 15.0 MB (32), scripts 883 KiB (20) and stylesheets 203 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (1.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.

  • 7 images below the first screen load straight away

    7 images further down the page (656 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.6 g of CO₂ per visit

    4.62 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9193
  • 4 text elements with low contrast

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

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7576
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 2 problems

    Structured data found (Organization) but with 2 problems, for example “Organization: url is not an absolute URL ("www.ahkbrasilien.com.br")”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 71 internal links, 11 external

    The homepage links to 71 pages on ahkbrasil.com and 11 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Câmara Brasil-Alemanha de São Paulo”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Câmara Brasil-Alemanha de São Paulo”.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.ahkbrasilien.com.br/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.

3 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 contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 13 pages without a meta description

    https://www.ahkbrasilien.com.br/br/sobre-nos, https://www.ahkbrasilien.com.br/br/imprensa, https://www.ahkbrasilien.com.br/br/eventos-e-delegacoes, https://www.ahkbrasilien.com.br/br/Areas-de-atuacao, https://www.ahkbrasilien.com.br/br/Areas-de-atuacao/diversidade-e-inclusao2 and https://www.ahkbrasilien.com.br/br/Areas-de-atuacao/inovacao2 and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 14 pages that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 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.

  • Thin social proof

    Social proof on the homepage: 5 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 738 words of visible text.

1 checks passed
  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 ahkbrasil.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
Ibexa DXP

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on ahkbrasil.com, including 22 speed issues, 6 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

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