Website review, no card needed
hashtech.co.tz website review
Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 78 checks
This review found 43 issues worth fixing on hashtech.co.tz, 17 of them high impact, across 78 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
Site score
67DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.7 s
4.0 s
5.3 s
6.7 s
8.0 s
9.4 s
10.7 s
Speed
Use efficient cache lifetimes
7.0 s · 5.2 MB60 files are served with short cache lifetimes, so returning visitors download them again (5.2 MB).
Render-blocking requests
4.2 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Reduce unused CSS
3.3 s · 414 KiBAbout 414 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Font display
1.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.0 s).
Improve image delivery
3.2 MB16 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
850 ms · 178 KiBAbout 178 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 850 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Minify CSS
600 ms · 35 KiB35 KiB could be saved by minifying CSS.
Document request latency
34 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 50 KiB and 0 ms of main-thread time.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 110 ms of it running JavaScript. That is comfortably low.
Server response: 207 ms
207 msYour server sent the HTML in 207 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.3 s
17.3 sYour largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Empowering Tomorrow, Connecting Today Discover limitless so…”. Most of its time is resource load delay (7.3 s).
Speed Index: 16.9 s
16.9 sVisually, the page fills in at 16.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.9 s
17.9 sThe page becomes fully interactive after 17.9 s. Good is under 3.8 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.3 MB in 65 requests
5.3 MBYour homepage downloads 5.3 MB in 65 requests on a phone: images 4.2 MB (37), stylesheets 461 KiB (8) and scripts 380 KiB (12). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
713 KiB3 images are downloaded at several times the size a phone draws them, for example choose-us1.jpg at 1,248 px wide, shown at 366 px. Resized copies would save about 713 KiB.
5 images in older formats
5 images (3.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 (3.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.51 g of CO₂e: 180.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 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), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, follow”: Google is told not to list this page at all.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (17 characters)
Your title is only 17 characters: “Hashtech Tanzania”. 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.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (417 characters)
Your meta description is 417 characters; Google truncates after about 160, so the end of your pitch is cut.
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 http://hashtech.co.tz/sitemap.xml, so Google discovers your pages only by following links.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
26 internal links, 3 external
The homepage links to 26 pages on hashtech.co.tz and 3 external pages.
1 checks passed
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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://hashtech.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
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 (628 words), so crawlers that don't run JavaScript still read it.
Other pages
8 linked pages hidden from search
https://hashtech.co.tz/about-2.html, https://hashtech.co.tz/project-list.html, https://hashtech.co.tz/contact.html, https://hashtech.co.tz/mysafari.html, https://hashtech.co.tz/staride.html and https://hashtech.co.tz/akilicorp.html and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
9 pages share a title
/, https://hashtech.co.tz/about-2.html, https://hashtech.co.tz/project-list.html, https://hashtech.co.tz/contact.html, https://hashtech.co.tz/mysafari.html and https://hashtech.co.tz/staride.html and 3 others all use the title “Hashtech Tanzania”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages share a meta description
https://hashtech.co.tz/about-2.html, https://hashtech.co.tz/project-list.html, https://hashtech.co.tz/contact.html, https://hashtech.co.tz/mysafari.html, https://hashtech.co.tz/staride.html and https://hashtech.co.tz/akilicorp.html and 2 others use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://hashtech.co.tz/about-2.html, https://hashtech.co.tz/project-list.html, https://hashtech.co.tz/contact.html, https://hashtech.co.tz/mysafari.html, https://hashtech.co.tz/staride.html and https://hashtech.co.tz/akilicorp.html and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 8 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 8 pages that loaded have a meta description.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://hashtech.co.tz/assets/images/ser-icon12.png.
2 small tap targets
2 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 654 words of copy
The homepage carries about 654 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Get in touch”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 13 testimonial or review blocks and “2 M+ Happy clients”.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
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 hashtech.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
- Framework
- jQuery
- Hosting
- Contabo GmbH
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on hashtech.co.tz, including 13 speed issues, 10 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.