mca.org.mt website review

12 images could be 6.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.2 s faster on a phone.

47 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.7 s.

About 693 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.5 s faster on a phone.

Your mobile performance score is 52 (desktop: 76). Pages that score under 90 lose visitors before the first paint.

5 third-party services load with your homepage (Google CDN, Google Tag Manager and Clarity and others), adding 1.1 MB and 583 ms of main-thread time.

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

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

Google CDN costs a phone 360 ms of main-thread work and 734 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

178 KiB could be saved by minifying JavaScript.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

11 KiB could be saved by minifying CSS.

2 files are served with short cache lifetimes, so returning visitors download them again (10 KiB).

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

Your largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MCA 25 Years Stamp Set”.

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

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

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

Scripts block taps and scrolling for 246 ms in total while the page loads. Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 125 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.6 MB in 153 requests on a phone: images 6.5 MB (16), scripts 1.6 MB (70) and stylesheets 801 KiB (49). Under 2 MB keeps phones on slow connections fast.

3 images weigh 5.5 MB together. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example Website Banner(1).png at 5,175 px wide, shown at 390 px. Resized copies would save about 5.3 MB.

7 images (6.5 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.

1 image further down the page (243 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.73 g of CO₂e: 327.8 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”.

5 tap targets are too small or too close together to hit reliably with a finger.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your meta description is only 29 characters: “Malta Communication Authority”. 70 to 160 characters is enough to sell the click.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.mca.org.mt/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 58 pages on mca.org.mt and 4 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.

/consumer, /digital-services, /regulatory, /spectrum-technology, /publications and /consultations and 2 others use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.

6 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “$(...).once is not a function Object.attach (https://www.mca.org.mt/modules/custom/mybills_payments/js/mybills.js?v=1.x…”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

The homepage carries about 331 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Clarity (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.

Opening the homepage sets 2 cookies (measured from a US location before any click).

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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.