Website review, no card needed
posta.co.tz website review
Visit site (opens in a new tab)Reviewed 4 November 202620 issues · 55 checks
This review found 20 issues worth fixing on posta.co.tz, 6 of them high impact, across 55 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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 16, 2026 | 7.3 s |
| May 23, 2026 | 7.4 s |
| May 30, 2026 | 7.5 s |
| Jun 6, 2026 | 7.4 s |
| Jun 13, 2026 | 7.6 s |
| Jun 20, 2026 | 7.8 s |
| Jun 27, 2026 | 7.8 s |
| Jul 4, 2026 | 8.0 s |
| Jul 11, 2026 | 7.9 s |
| Jul 18, 2026 | 7.9 s |
| Jul 25, 2026 | 8.0 s |
| Aug 1, 2026 | 7.7 s |
| Aug 8, 2026 | 7.6 s |
| Aug 15, 2026 | 7.4 s |
| Aug 22, 2026 | 7.3 s |
| Aug 29, 2026 | 7.4 s |
| Sep 5, 2026 | 7.9 s |
| Sep 12, 2026 | 8.8 s |
| Sep 19, 2026 | 9.2 s |
| Sep 26, 2026 | 9.5 s |
| Oct 3, 2026 | 9.9 s |
| Oct 10, 2026 | 9.6 s |
| Oct 17, 2026 | 9.0 s |
| Oct 24, 2026 | 8.8 s |
| Oct 31, 2026 | 8.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 568 ms |
| May 23, 2026 | 546 ms |
| May 30, 2026 | 539 ms |
| Jun 6, 2026 | 529 ms |
| Jun 13, 2026 | 481 ms |
| Jun 20, 2026 | 493 ms |
| Jun 27, 2026 | 496 ms |
| Jul 4, 2026 | 471 ms |
| Jul 11, 2026 | 513 ms |
| Jul 18, 2026 | 459 ms |
| Jul 25, 2026 | 448 ms |
| Aug 1, 2026 | 525 ms |
| Aug 8, 2026 | 504 ms |
| Aug 15, 2026 | 506 ms |
| Aug 22, 2026 | 531 ms |
| Aug 29, 2026 | 494 ms |
| Sep 5, 2026 | 483 ms |
| Sep 12, 2026 | 408 ms |
| Sep 19, 2026 | 315 ms |
| Sep 26, 2026 | 259 ms |
| Oct 3, 2026 | 223 ms |
| Oct 10, 2026 | 221 ms |
| Oct 17, 2026 | 219 ms |
| Oct 24, 2026 | 198 ms |
| Oct 31, 2026 | 182 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 8.2 s
8.2 sReal visitors wait 8.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.0 s
6.0 sReal visitors see the first content after 6.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.6 s
2.6 sReal visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 7.3 s to 8.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 186 ms
186 msReal visitors wait 186 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.
Tap response (INP) got 66% faster for real visitors
-66%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 568 ms to 182 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
About 0.1 g of CO₂ per visit
0.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.10 g of CO₂e: 12.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 369 KiB
369 KiBYour homepage downloads 369 KiB on a phone, 91 KiB of it images (25%). That is a lean page.
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
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.
SEO
Title is short (12 characters)
Your title is only 12 characters: “TPC | Mwanzo”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (48 characters)
Your meta description is only 48 characters: “Tanzania posts corporation & We delivers better.”. 70 to 160 characters is enough to sell the click.
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://www.posta.co.tz/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at posta.co.tz/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
69 internal links, 29 external
The homepage links to 69 pages on posta.co.tz and 29 external pages.
1 checks passed
One H1 headline
Your main headline reads: “Welcome to Tanzania Posts Corporation.Your Trusted Partner in Communication & Logistics.”.
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.posta.co.tz/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 (805 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://www.posta.co.tz/en all use the title “TPC | Mwanzo”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://www.posta.co.tz/en, https://www.posta.co.tz/en/history, https://www.posta.co.tz/en/mission-vision, https://www.posta.co.tz/en/orgainzation-structure, https://www.posta.co.tz/en/board-page and https://www.posta.co.tz/en/management-page and 9 others use the same meta description. A description written for each page earns more clicks.
2 pages slow to respond
https://www.posta.co.tz/en/history and https://www.posta.co.tz/en/mission-vision took over 3 s to send their HTML from our server.
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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
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.
Thin social proof
Social proof on the homepage: 10 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.
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 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 689 words of copy
The homepage carries about 689 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Online Shop”, “Kipepeo Shop” and “Buy Now”.
1 short form
A short form (0 fields at most) is right on the homepage.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
4 other companies contacted
Loading the homepage contacts 4 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 posta.co.tz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Ttcldata
Company
- Founded
- 1994
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on posta.co.tz, including 4 speed issues, 8 SEO issues and 3 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.