Website review, no card needed

atlantico.ao logo

atlantico.ao website review

Visit site (opens in a new tab)Reviewed 1 November 202644 issues · 91 checks

This review found 44 issues worth fixing on atlantico.ao, 18 of them high impact, across 91 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
5.6 s3.4 sMay 9Oct 173.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.0 s
May 23, 20264.0 s
May 30, 20264.0 s
Jun 6, 20263.9 s
Jul 4, 20265.4 s
Jul 11, 20265.4 s
Jul 18, 20265.3 s
Jul 25, 20265.2 s
Aug 1, 20264.5 s
Aug 8, 20264.2 s
Aug 15, 20264.4 s
Aug 22, 20264.3 s
Aug 29, 20264.1 s
Sep 5, 20263.7 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Oct 10, 20264.0 s
Oct 17, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
241 ms186 msMay 16Oct 17227 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026229 ms
May 23, 2026227 ms
May 30, 2026228 ms
Jun 6, 2026228 ms
Jul 4, 2026203 ms
Jul 11, 2026202 ms
Jul 18, 2026207 ms
Jul 25, 2026206 ms
Aug 1, 2026213 ms
Aug 8, 2026214 ms
Aug 15, 2026207 ms
Aug 22, 2026205 ms
Aug 29, 2026198 ms
Sep 5, 2026192 ms
Sep 19, 2026207 ms
Sep 26, 2026235 ms
Oct 3, 2026227 ms
Oct 10, 2026230 ms
Oct 17, 2026227 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 atlantico.ao (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. atlantico.ao at 0.7 s0.7 s
  2. atlantico.ao at 1.4 s1.4 s
  3. atlantico.ao at 2.2 s2.2 s
  4. atlantico.ao at 2.9 s2.9 s
  5. atlantico.ao at 3.6 s3.6 s
  6. atlantico.ao at 4.3 s4.3 s
  7. atlantico.ao at 5.1 s5.1 s
  8. atlantico.ao at 5.8 s5.8 s

Speed

8 to fix63
  • Use efficient cache lifetimes

    11.1 s · 18.6 MB

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

  • Improve image delivery

    10.6 s · 14.2 MB

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

  • Reduce unused JavaScript

    1.2 s · 336 KiB

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

  • Render-blocking requests

    1.1 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.1 s.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

  • Font display

    850 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).

  • Google Tag Manager adds 264 ms

    264 ms

    Google Tag Manager costs a phone 264 ms of main-thread work and 465 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.

  • 1,985 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, messagebird.com and OneSignal and others), adding 843 KiB and 413 ms of main-thread time.

  • Reduce unused CSS

    190 ms · 93 KiB

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

  • 4 long tasks on the main thread

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 544 ms of it running JavaScript. That is comfortably low.

  • Server response: 236 ms

    236 ms

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

Core Web Vitals

11 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 FCP: 3.3 s

    3.3 s

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

  • Largest Contentful Paint: 18.0 s

    18.0 s

    Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 22.7 s

    22.7 s

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

  • Time to Interactive: 42.7 s

    42.7 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user INP: 202 ms

    202 ms

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

  • Real-user CLS: 0.12

    0.12

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

  • Real-user TTFB: 956 ms

    956 ms

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

  • 57 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

2 checks passed
  • Total Blocking Time: 109 ms

    109 ms

    Scripts block the page for only 109 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.007

    0.007

    The layout barely moves while loading (CLS 0.007, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 19.4 MB in 133 requests

    19.4 MB

    Your homepage downloads 19.4 MB in 133 requests on a phone: images 18.3 MB (88), scripts 844 KiB (22) and fonts 165 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (237 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.5 g of CO₂ per visit

    5.50 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 7487
  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must be contained by particular parents (2 elements)

    Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

  • 30 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 110 images without alt text

    110 images have no alt text, which hurts accessibility and image search.

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

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

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 6766
  • No meta description

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

  • 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 XML sitemap

    No XML sitemap at https://atlantico.ao/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at atlantico.ao/robots.txt, the first file search crawlers ask for.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 2 links with vague text

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 174 internal links, 11 external

    The homepage links to 174 pages on atlantico.ao and 11 external pages.

2 checks passed
  • Title: 36 characters

    Your title is a healthy 36 characters: “Banco Millennium Atlantico - Para Si”.

  • Canonical URL set

    The canonical URL is https://atlantico.ao/pt/particulares/para-si/.

AI search readiness

1 to fix88
  • 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://atlantico.ao/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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

4 to fix78
  • 2 pages share a title

    https://atlantico.ao/pt/particulares/para-si and https://atlantico.ao/pt/particulares all use the title “Banco Millennium Atlantico - Para Si”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://atlantico.ao/pt/particulares, https://atlantico.ao/pt/empresas, https://atlantico.ao/pt/seguros, https://atlantico.ao/pt/investimentos-e-poupanca, https://atlantico.ao/pt/institucional and https://atlantico.ao/pt/sustentabilidade and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://atlantico.ao/pt/particulares, whose canonical is https://atlantico.ao/pt/particulares/para-si. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    https://atlantico.ao/pt/particulares, https://atlantico.ao/pt/empresas, https://atlantico.ao/pt/seguros, https://atlantico.ao/pt/investimentos-e-poupanca, https://atlantico.ao/pt/institucional and https://atlantico.ao/pt/sustentabilidade and 2 others 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 71 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8887
  • 7 small tap targets

    7 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) p: OneSignal: This web push config can only be used on https://www.atlantico.ao. Your current ori…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 748 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Download IOS APP” and “Download Android App”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Download IOS APP” and “Download Android App”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 57 testimonial or review blocks and 47 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 atlantico.ao, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2022.

Stack

Framework
Bootstrap
Analytics
Google Tag Manager
Hosting
Azure

Company

Founded
2006
Headquarters
Luanda

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on atlantico.ao, including 19 speed issues, 7 SEO issues and 1 conversion gap. 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