computersystemsmw.com website review

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

21 images could be 12.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

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

2 third-party services load with your homepage (jQuery CDN and Cloudflare CDN), adding 178 KiB and 50 ms of main-thread time.

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

About 25 KiB of JavaScript is downloaded but never used on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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.

Your homepage downloads 13.2 MB in 36 requests on a phone: images 12.9 MB (28), fonts 123 KiB (1) and scripts 67 KiB (3). Under 2 MB keeps phones on slow connections fast.

4 images weigh 10.8 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example bg nice.png at 2,895 px wide, shown at 390 px. Resized copies would save about 10.6 MB.

23 images (12.9 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.

17 images further down the page (6.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 72 characters, so Google will cut it off around 60: “Computer Systems Malawi Limited: ICT Equipment, Software Services & More”.

Your canonical URL points to yourwebsite.com, not computersystemsmw.com, so Google may credit that host instead.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“”, “We Focus On Making The Best In All Sectors” and “Our Location”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 34 pages on computersystemsmw.com and 0 external pages.

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.

There is no /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.

Your homepage links to /about.php, /services/digitisation.php, /services/web-design.php, /services/Saas.php, /services/IT-training.php and /services/IT-consultancy.php and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.

/ and /services/IT-training.html all use the title “Computer Systems Malawi Limited: ICT Equipment, Software Services & M…”. Search engines can't tell which page to show for a search, so each competes with the others.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

15 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

12 links from your homepage to your own site are broken, for example https://computersystemsmw.com/index.php (409).

http://computersystemsmw.com does not redirect to https, so some visitors land on the insecure version.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

computersystemsmw.com is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

computersystemsmw.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

computersystemsmw.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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

The homepage has only about 204 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

computersystemsmw.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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.

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