Website review, no card needed
minfin.gov.ao website review
Visit site (opens in a new tab)Reviewed 26 October 202654 issues · 75 checks
This review found 54 issues worth fixing on minfin.gov.ao, 26 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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
How it loaded on a phone
1.6 s
3.3 s
4.9 s
6.6 s
8.2 s
9.9 s
11.5 s
13.2 s
Speed
Use efficient cache lifetimes
9.3 s · 16.0 MB65 files are served with short cache lifetimes, so returning visitors download them again (16.0 MB).
Reduce unused JavaScript
3.0 s · 564 KiBAbout 564 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Mobile performance score: 20
20/100Your mobile performance score is 20. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,346 HTML elements
The page has 3,346 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
950 ms · 855 KiB14 images could be 855 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
Legacy JavaScript
500 ms · 16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.
Render-blocking requests
500 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Reduce unused CSS
310 ms · 87 KiBAbout 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 247 ms. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Cloudflare CDN and others), adding 241 KiB and 83 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: 1 ms
1 msYour server sent the HTML in 1 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: 10.4 s
10.4 sReal visitors wait 10.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.00
1.00For real visitors the layout shifts by 1.00 (75th percentile). Good is under 0.1.
Real-user FCP: 5.9 s
5.9 sReal visitors see the first content after 5.9 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 21.3 s
21.3 sYour largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (9.3 s).
Speed Index: 18.5 s
18.5 sVisually, the page fills in at 18.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 21.6 s
21.6 sThe page becomes fully interactive after 21.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.9
0.9The layout shifts by 0.9 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Real-user INP: 354 ms
354 msReal visitors wait 354 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 270 ms to 354 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 7.4 s to 10.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 461 ms
461 msScripts block taps and scrolling for 461 ms in total while the page loads. Good is under 200 ms.
35 images without width and height
35 images have no width and height attributes, so the layout jumps as each one loads.
Images and page weight
Page weight: 17.1 MB in 136 requests
17.1 MBYour homepage downloads 17.1 MB in 136 requests on a phone: images 15.3 MB (58), scripts 898 KiB (7) and other files 857 KiB (63). Under 2 MB keeps phones on slow connections fast.
About 4.9 g of CO₂ per visit
4.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.85 g of CO₂e: 582.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (3 elements)
Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 10 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.
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 canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
No XML sitemap
No XML sitemap at https://minfin.gov.ao/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at minfin.gov.ao/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1 checks passed
Title: 49 characters
Your title is a healthy 49 characters: “MINFIN - Portal Ministério das Finanças de Angola”.
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://minfin.gov.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.
Best practices
6 broken images
6 images failed to load on a phone, for example https://minfin.gov.ao/.
6 small tap targets
6 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
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
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 135 words
The homepage has only about 135 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
5 other companies contacted
Loading the homepage contacts 5 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 minfin.gov.ao, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on minfin.gov.ao, including 24 speed issues, 8 SEO issues and 6 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.