webmakerghana.com website review

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

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

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

About 325 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

A phone's processor spends 2.3 s on main-thread work while loading, 933 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

6 third-party services load with your homepage (Google Tag Manager, visitor-analytics.io and Cookiebot and others), adding 428 KiB and 366 ms of main-thread time.

24 KiB could be saved by minifying JavaScript.

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

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

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

1 image 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 5.1 MB in 82 requests on a phone: images 2.9 MB (23), media 1.3 MB (1) and scripts 647 KiB (29). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example Photo 05-06-2023pm.jpg at 2,320 px wide, shown at 68 px. Resized copies would save about 1.6 MB.

Photo 05-06-2023pm.jpg weighs 972 KiB. On a phone connection a single image that size takes seconds.

8 images (1.8 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.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Structured data found (FAQPage and ProfessionalService) but with 3 problems, for example “ProfessionalService: url is not an absolute URL ("/")”.

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

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

The homepage links to 5 pages on webmakerghana.com and 7 external pages.

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 /datenschutz, which answers with an error. Visitors hit a dead end and search engines drop it.

/termin.html is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/termin.html has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie, 1 of them by other companies (measured from a US location before any click).

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