Website review, no card needed

spectranet.com.ng logo

spectranet.com.ng website review

Visit site (opens in a new tab)Reviewed 26 October 202634 issues · 74 checks

This review found 34 issues worth fixing on spectranet.com.ng, 14 of them high impact, across 74 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
7.0 s3.0 sMay 9Oct 243.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20266.5 s
May 16, 20266.4 s
May 23, 20266.2 s
May 30, 20265.7 s
Jun 6, 20265.5 s
Jun 13, 20265.4 s
Jun 20, 20265.4 s
Jun 27, 20265.5 s
Jul 4, 20265.4 s
Jul 11, 20265.6 s
Jul 18, 20265.8 s
Jul 25, 20265.9 s
Aug 1, 20266.1 s
Aug 8, 20266.2 s
Aug 15, 20266.2 s
Aug 22, 20266.3 s
Aug 29, 20266.2 s
Sep 5, 20266.2 s
Sep 12, 20266.2 s
Sep 19, 20266.3 s
Sep 26, 20266.2 s
Oct 3, 20265.6 s
Oct 10, 20264.9 s
Oct 17, 20264.3 s
Oct 24, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
257 ms189 msMay 9Oct 24211 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026197 ms
May 16, 2026200 ms
May 23, 2026202 ms
May 30, 2026205 ms
Jun 6, 2026206 ms
Jun 13, 2026205 ms
Jun 20, 2026205 ms
Jun 27, 2026205 ms
Jul 4, 2026203 ms
Jul 11, 2026203 ms
Jul 18, 2026204 ms
Jul 25, 2026203 ms
Aug 1, 2026207 ms
Aug 8, 2026210 ms
Aug 15, 2026212 ms
Aug 22, 2026218 ms
Aug 29, 2026227 ms
Sep 5, 2026233 ms
Sep 12, 2026240 ms
Sep 19, 2026247 ms
Sep 26, 2026249 ms
Oct 3, 2026242 ms
Oct 10, 2026234 ms
Oct 17, 2026225 ms
Oct 24, 2026211 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

Full-page screenshot of spectranet.com.ng (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. spectranet.com.ng at 1.2 s1.2 s
  2. spectranet.com.ng at 2.4 s2.4 s
  3. spectranet.com.ng at 3.6 s3.6 s
  4. spectranet.com.ng at 4.8 s4.8 s
  5. spectranet.com.ng at 6.0 s6.0 s
  6. spectranet.com.ng at 7.2 s7.2 s
  7. spectranet.com.ng at 8.4 s8.4 s
  8. spectranet.com.ng at 9.6 s9.6 s

Speed

3 to fix56
  • Improve image delivery

    15.8 s · 4.0 MB

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

  • Render-blocking requests

    1.4 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.4 s.

  • Mobile performance score: 56

    56/100

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

  • 2 long tasks on the main thread

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

  • Document request latency

    88 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and JSDelivr CDN), adding 276 KiB and 0 ms of main-thread time.

  • Reduce unused CSS

    13 KiB

    About 13 KiB of CSS is downloaded but never applied on this page.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 33 ms of it running JavaScript. That is comfortably low.

  • Server response: 541 ms

    541 ms

    Your server sent the HTML in 541 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix0
  • 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.

  • Real-user LCP: 4.1 s

    4.1 s

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

  • Largest Contentful Paint: 23.5 s

    23.5 s

    Your largest element takes 23.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Spectranet”.

  • Time to Interactive: 23.6 s

    23.6 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Real-user INP: 253 ms

    253 ms

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

  • Real-user CLS: 0.16

    0.16

    For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • 16 images without width and height

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

3 checks passed
  • Largest content (LCP) got 40% faster for real visitors

    -40%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix14
  • Page weight: 20.0 MB in 22 requests

    20.0 MB

    Your homepage downloads 20.0 MB in 22 requests on a phone: images 19.4 MB (14), fonts 261 KiB (3) and stylesheets 206 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 18.5 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    17.1 MB

    9 images are downloaded at several times the size a phone draws them, for example homepage-enterprise-mobile.jpeg at 5,002 px wide, shown at 390 px. Resized copies would save about 17.1 MB.

  • 9 images in older formats

    9 images (19.1 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.

  • An image on the first screen is lazy-loaded

    homepage-enterprise-mobile.jpeg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 5.7 g of CO₂ per visit

    5.67 g

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

Accessibility

3 to fixGoogle 9395
  • 17 text elements with low contrast

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

  • 7 tap targets too small

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

  • All page content should be contained by landmarks (1 element)

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 10074
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No canonical URL

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

  • No social preview image

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

  • No XML sitemap

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 82 internal links, 27 external

    The homepage links to 82 pages on spectranet.com.ng and 27 external pages.

3 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “Spectranet — Nigeria's first 4G LTE network. Data plans, Home Fiber, e-Shop devices, Selfcare and award-winning broadba…”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Spectranet Nigeria – Fast Broadband & WiFi Plans”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://spectranet.com.ng/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 (1,262 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    / and https://spectranet.com.ng/unlimited-plans all use the title “Spectranet Nigeria – Fast Broadband & WiFi Plans”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without an H1

    https://spectranet.com.ng/enterprise-business has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://spectranet.com.ng/contact, https://spectranet.com.ng/shop and https://spectranet.com.ng/services/fibre-on-air took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 6 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&display=swap' violates the follo…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • No analytics detected

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

  • 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 1,059 words of copy

    The homepage carries about 1,059 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP LOCATIONS”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Call us 0800 234 5678”, “Shop Locations” and “Buy Top-Ups”.

  • 3 short forms

    3 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 64 testimonial or review blocks and 2 trust badges.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • No consent tool detected

    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.

  • 3 other companies contacted

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

1 checks passed
  • 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 spectranet.com.ng, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Hosting
Spectranet

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on spectranet.com.ng, including 14 speed issues, 6 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25