Website review, no card needed

nta.ng logo

nta.ng website review

Visit site (opens in a new tab)Reviewed 19 November 202640 issues · 85 checks

This review found 40 issues worth fixing on nta.ng, 18 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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
5.7 s3.8 sMay 30Nov 144.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.4 s
Jun 6, 20265.5 s
Jun 13, 20265.3 s
Jun 20, 20265.3 s
Jun 27, 20264.9 s
Jul 4, 20264.8 s
Jul 11, 20264.7 s
Jul 18, 20264.7 s
Jul 25, 20265.0 s
Aug 1, 20265.2 s
Aug 8, 20265.1 s
Aug 15, 20265.1 s
Aug 22, 20264.2 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.4 s
Sep 26, 20264.5 s
Oct 3, 20265.4 s
Oct 10, 20265.1 s
Oct 17, 20265.2 s
Oct 24, 20265.1 s
Oct 31, 20264.9 s
Nov 7, 20264.8 s
Nov 14, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
239 ms148 msMay 30Nov 14205 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026197 ms
Jun 6, 2026211 ms
Jun 13, 2026218 ms
Jun 20, 2026228 ms
Jun 27, 2026181 ms
Jul 4, 2026179 ms
Jul 11, 2026163 ms
Jul 18, 2026158 ms
Jul 25, 2026209 ms
Aug 1, 2026210 ms
Aug 8, 2026218 ms
Aug 15, 2026220 ms
Aug 22, 2026195 ms
Aug 29, 2026194 ms
Sep 5, 2026167 ms
Sep 12, 2026161 ms
Sep 19, 2026167 ms
Sep 26, 2026176 ms
Oct 3, 2026226 ms
Oct 10, 2026214 ms
Oct 17, 2026218 ms
Oct 24, 2026215 ms
Oct 31, 2026191 ms
Nov 7, 2026204 ms
Nov 14, 2026205 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 nta.ng (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nta.ng at 1.4 s1.4 s
  2. nta.ng at 2.9 s2.9 s
  3. nta.ng at 4.3 s4.3 s
  4. nta.ng at 5.7 s5.7 s
  5. nta.ng at 7.2 s7.2 s
  6. nta.ng at 8.6 s8.6 s
  7. nta.ng at 10.0 s10.0 s
  8. nta.ng at 11.5 s11.5 s

Speed

7 to fix65
  • Reduce unused JavaScript

    1.4 s · 245 KiB

    About 245 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.

  • Render-blocking requests

    1.1 s

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

  • Use efficient cache lifetimes

    450 ms · 5.8 MB

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

  • Improve image delivery

    300 ms · 5.7 MB

    25 images could be 5.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65. 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 Tag Manager, acan.group and YouTube and others), adding 1.2 MB and 139 ms of main-thread time.

  • acan.group adds 0 ms

    0 ms

    acan.group costs a phone 0 ms of main-thread work and 799 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.

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    11 KiB

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

  • Reduce unused CSS

    11 KiB

    About 11 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.

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 103 ms

    103 ms

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

Core Web Vitals

10 to fix33
  • 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.8 s

    4.8 s

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your 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. Most of its time is resource load duration (4.5 s).

  • Speed Index: 10.0 s

    10.0 s

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

  • Time to Interactive: 9.5 s

    9.5 s

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

  • Real-user INP: 223 ms

    223 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

4 checks passed
  • Real-user CLS: 0.06

    0.06

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.4 s to 4.7 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: 41 ms

    41 ms

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

Images and page weight

5 to fix18
  • Page weight: 7.6 MB in 81 requests

    7.6 MB

    Your homepage downloads 7.6 MB in 81 requests on a phone: images 6.6 MB (36), scripts 510 KiB (22) and other files 250 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 16 images far larger than shown

    4.7 MB

    16 images are downloaded at several times the size a phone draws them, for example AFP__20261102__D4TY7KE__v3__MP41920x1080__GhanaMustGoTheHumb at 1,920 px wide, shown at 348 px. Resized copies would save about 4.7 MB.

  • 5 images over 500 KB

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

  • 17 images in older formats

    17 images (6.2 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.

  • 10 images below the first screen load straight away

    10 images further down the page (4.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.15 g

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

Accessibility

4 to fixGoogle 9193
  • 23 text elements with low contrast

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

  • 15 tap targets too small

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 58 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 10078
  • No H1 headline

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

  • Canonical points to another host

    Your canonical URL points to localhost, not nta.ng, so Google may credit that host instead.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (http://localhost)”.

  • No XML sitemap

    No XML sitemap at http://localhost:3000/sitemap.xml, so Google discovers your pages only by following links.

  • 70 internal links, 7 external

    The homepage links to 70 pages on nta.ng and 7 external pages.

4 checks passed
  • Meta description: 101 characters

    Your meta description is 101 characters: “Stay updated with Nigeria's latest news, watch live TV channels, and access premium content from NTA.”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Nigerian Television Authority - News, Live TV and Replay”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

    There is no https://www.nta.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.

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,371 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.nta.ng/watch/live/ntaintl and https://www.nta.ng/watch/live all use the title “NTA INT'L - NTA”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.nta.ng/watch/live/ntaintl and https://www.nta.ng/watch/live use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://www.nta.ng/watch/live/ntanews24, https://www.nta.ng/watch/live/ntaparliement, https://www.nta.ng/watch/live/nta2lagos and https://www.nta.ng/watch/live/ntaentertainment have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://www.nta.ng/watch/live/ntaintl, https://www.nta.ng/watch/live/ntanews24, https://www.nta.ng/watch/live/ntaparliement, https://www.nta.ng/watch/live/nta2lagos, https://www.nta.ng/watch/live/ntaentertainment and https://www.nta.ng/watch/live have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 4 pages slow to respond

    https://www.nta.ng/news/business-and-economy/nigerias-inflation-drops-to-14-06-why-does-the-cost-of-living-still-feel-high, https://www.nta.ng/news/politics/obasanjo-faults-tinubus-subsidy-approach-raises-questions-about-economic-planning, https://www.nta.ng/news/business-and-economy/tinubu-approves-kebbi-dry-port-possible-northern-trade-boost and https://www.nta.ng/watch/live took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 46 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    30 of 37 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

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

  • 4 other companies contacted

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

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 nta.ng, 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
Analytics
Google Analytics
Hosting
OVHcloud

Company

Founded
1976
Headquarters
Federal Capital Territory

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on nta.ng, including 17 speed issues, 4 SEO issues and 6 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

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