Website review, no card needed
go.com.mt website review
Visit site (opens in a new tab)Reviewed 18 November 202639 issues · 82 checks
This review found 39 issues worth fixing on go.com.mt, 13 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 206 ms |
| Jun 6, 2026 | 207 ms |
| Jun 13, 2026 | 211 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 216 ms |
| Jul 4, 2026 | 214 ms |
| Jul 11, 2026 | 214 ms |
| Jul 18, 2026 | 214 ms |
| Jul 25, 2026 | 214 ms |
| Aug 1, 2026 | 219 ms |
| Aug 8, 2026 | 222 ms |
| Aug 15, 2026 | 227 ms |
| Aug 22, 2026 | 233 ms |
| Aug 29, 2026 | 235 ms |
| Sep 5, 2026 | 234 ms |
| Sep 12, 2026 | 235 ms |
| Sep 19, 2026 | 237 ms |
| Sep 26, 2026 | 241 ms |
| Oct 3, 2026 | 246 ms |
| Oct 10, 2026 | 250 ms |
| Oct 17, 2026 | 254 ms |
| Oct 24, 2026 | 260 ms |
| Oct 31, 2026 | 262 ms |
| Nov 7, 2026 | 264 ms |
| Nov 14, 2026 | 261 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
Improve image delivery
1.1 s · 3.4 MB51 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Reduce unused JavaScript
1.4 s · 797 KiBAbout 797 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 110 KiB5 files are served with short cache lifetimes, so returning visitors download them again (110 KiB).
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google CDN, Cookiebot and Other Google APIs/SDKs and others), adding 951 KiB and 528 ms of main-thread time.
Legacy JavaScript
450 ms · 78 KiBPolyfills for old browsers add 78 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Google CDN adds 407 ms
407 msGoogle CDN costs a phone 407 ms of main-thread work and 739 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.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,966 HTML elements
The page has 1,966 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
Reduce unused CSS
61 KiBAbout 61 KiB of CSS is downloaded but never applied on this page.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 94 ms
94 msYour server sent the HTML in 94 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 9.4 s
9.4 sYour largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday with button”.
Time to Interactive: 17.3 s
17.3 sThe page becomes fully interactive after 17.3 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Real-user INP: 285 ms
285 msReal visitors wait 285 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 206 ms to 261 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 480 ms
480 msScripts block taps and scrolling for 480 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 639 ms
639 msReal visitors wait 639 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 10.4 MB in 127 requests
10.4 MBYour homepage downloads 10.4 MB in 127 requests on a phone: images 8.4 MB (66), scripts 1.5 MB (46) and other files 359 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
id-destin-movie.png weighs 556 KiB. On a phone connection a single image that size takes seconds.
38 images below the first screen load straight away
38 images further down the page (5.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
33 images in older formats
33 images (4.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.
3 images far larger than shown
439 KiB3 images are downloaded at several times the size a phone draws them, for example refer-friend-save-mobile-plan.png at 1,024 px wide, shown at 230 px. Resized copies would save about 439 KiB.
About 3.0 g of CO₂ per visit
2.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.96 g of CO₂e: 354.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6 and h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 71 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 H1 headlines
There are 6 <h1> headlines (“6 months FREE Freedom Plus”, “6 months FREE Freedom Plus” and “6 months FREE Freedom Plus”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
91 internal links, 8 external
The homepage links to 91 pages on go.com.mt and 8 external pages.
6 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “From nationwide fibre internet & mobile plans to landline, TV & a range of devices, we offer the services & products yo…”.
Title: 60 characters
Your title is a healthy 60 characters: “Welcome to GO | Mobile, internet, phone and TV services | GO”.
Canonical URL set
The canonical URL is https://www.go.com.mt/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.go.com.mt/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.go.com.mt/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 (780 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.go.com.mt/mobile-plans/unlimited-pay-monthly-freedom-plans and https://www.go.com.mt/iphone-duo-register-interest are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
1 page without a meta description
https://www.go.com.mt/careers has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.go.com.mt/easy-buy-deals, https://www.go.com.mt/offers/refer-a-friend-and-get-25-euros and https://www.go.com.mt/iphone-duo-register-interest have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://www.go.com.mt/business, https://www.go.com.mt/wholesale, https://www.go.com.mt/go-energi-pv-system, https://www.go.com.mt/go-insure, https://www.go.com.mt/offers/refer-a-friend-and-get-25-euros and https://www.go.com.mt/mobile-plans/unlimited-pay-monthly-freedom-plans and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
4 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
12 of 14 tappable elements near the top are at least 24 px.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 647 words of copy
The homepage carries about 647 words of visible text.
1 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Us”.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 go.com.mt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- Next.js
- Hosting
- DigitalOcean
Company
- Founded
- 1997
- Headquarters
- Marsa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on go.com.mt, including 18 speed issues, 2 SEO issues and 4 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.