go54.com website review

About 797 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

Your mobile performance score is 43 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, b-cdn.net and Clarity and others), adding 1,018 KiB and 693 ms of main-thread time.

Google Tag Manager costs a phone 361 ms of main-thread work and 541 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.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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.

Real visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 4.0 s (75th percentile). Good is under 1.8 s.

Real visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Own Your .com.ng Domain Today for Only ₦3,000”.

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

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

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

Real visitors wait 466 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.1 MB in 80 requests on a phone: scripts 1.6 MB (28), images 266 KiB (18) and fonts 83 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

6 elements use ARIA attributes their role does not allow, which confuses screen readers.

Images must have alternative text: 6 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

4 form fields have 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. (3 elements).

Your title is only 26 characters: “GO54 - Web Hosting Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“Launch your website .css-11a2non{display:none;}@m…” and “Launch your website faster than the competition w…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 47 pages on go54.com and 47 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.

/microsoft-365-email-service has no <h1> headline, so visitors and search engines get no clear main topic.

/website-builder took over 3 s to send its HTML from our server.

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

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

6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=461232597.1792696413&gtm=45He6al0v9176600513za200zd9176600…”.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

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

1 link to other sites is dead, for example https://pagechap.com/?utm_campaign=go54_website&utm_medium=website&utm_source=website (502).

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

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

1 link go through two or more redirects, for example http://webmail.go54mail.com/.

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

go54.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.

go54.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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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 551 words of visible text.

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.

Before a visitor clicks anything, the page loads Google Analytics, 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 8 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.