Website review, no card needed

nairametrics.com logo

nairametrics.com website review

Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 84 checks

This review found 35 issues worth fixing on nairametrics.com, 10 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
3.8 s2.3 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.6 s
May 9, 20263.5 s
May 16, 20263.4 s
May 23, 20263.2 s
May 30, 20263.3 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.0 s
Jun 27, 20262.8 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20262.9 s
Sep 26, 20262.8 s
Oct 3, 20262.6 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
252 ms135 msMay 2Oct 17173 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026238 ms
May 9, 2026236 ms
May 16, 2026227 ms
May 23, 2026224 ms
May 30, 2026227 ms
Jun 6, 2026223 ms
Jun 13, 2026222 ms
Jun 20, 2026210 ms
Jun 27, 2026180 ms
Jul 4, 2026152 ms
Jul 11, 2026150 ms
Jul 18, 2026148 ms
Jul 25, 2026151 ms
Aug 1, 2026156 ms
Aug 8, 2026153 ms
Aug 15, 2026157 ms
Aug 22, 2026162 ms
Aug 29, 2026169 ms
Sep 5, 2026175 ms
Sep 12, 2026177 ms
Sep 19, 2026177 ms
Sep 26, 2026175 ms
Oct 3, 2026173 ms
Oct 10, 2026173 ms
Oct 17, 2026173 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 nairametrics.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nairametrics.com at 0.6 s0.6 s
  2. nairametrics.com at 1.2 s1.2 s
  3. nairametrics.com at 1.7 s1.7 s
  4. nairametrics.com at 2.3 s2.3 s
  5. nairametrics.com at 2.9 s2.9 s
  6. nairametrics.com at 3.5 s3.5 s
  7. nairametrics.com at 4.0 s4.0 s
  8. nairametrics.com at 4.6 s4.6 s

Speed

9 to fix48
  • Use efficient cache lifetimes

    3.8 s · 5.5 MB

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

  • Mobile performance score: 48

    48/100

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

  • Main-thread work: 5.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Taboola and others), adding 2.4 MB and 1.6 s of main-thread time.

  • Reduce unused JavaScript

    1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page.

  • Google/Doubleclick Ads adds 805 ms

    805 ms

    Google/Doubleclick Ads costs a phone 805 ms of main-thread work and 1.3 MB 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.

  • Improve image delivery

    350 ms · 181 KiB

    7 images could be 181 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Google Tag Manager adds 388 ms

    388 ms

    Google Tag Manager costs a phone 388 ms of main-thread work and 429 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.

  • Taboola adds 118 ms

    118 ms

    Taboola costs a phone 118 ms of main-thread work and 335 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.

  • Reduce unused CSS

    150 ms · 53 KiB

    About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    200 ms

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    20 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 91 ms

    91 ms

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

Core Web Vitals

6 to fix100
  • 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.

  • Time to Interactive: 42.7 s

    42.7 s

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

  • Speed Index: 13.2 s

    13.2 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NGX,Arbico Plc”.

  • Total Blocking Time: 728 ms

    728 ms

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

  • Real-user TTFB: 900 ms

    900 ms

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

8 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 154 ms

    154 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Tap response (INP) got 27% faster for real visitors

    -27%

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

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

    -32%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix43
  • Page weight: 7.7 MB in 164 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 164 requests on a phone: fonts 3.5 MB (4), scripts 2.2 MB (55) and images 1.7 MB (47). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    image-2026-10-21T144916.489-300x170.webp 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).

  • 14 images below the first screen load straight away

    14 images further down the page (923 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 8 images in older formats

    8 images (558 KiB) 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 far larger than shown

    48 KiB

    1 image is downloaded at several times the size a phone draws it, for example nairametrics-awards-scaled.webp at 2,000 px wide, shown at 390 px. Resized copies would save about 48 KiB.

  • About 2.2 g of CO₂ per visit

    2.18 g

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

Accessibility

5 to fixGoogle 10095
  • All page content should be contained by landmarks (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate 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.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

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

  • 292 internal links, 15 external

    The homepage links to 292 pages on nairametrics.com and 15 external pages.

6 checks passed
  • Meta description: 120 characters

    Your meta description is 120 characters: “Destination for Business news, financial literacy, economy, and analysis from Africa's largest economy and Nigeria news.”.

  • One H1 headline

    Your main headline reads: “NGX fines 15 companies N123.17 million for late filings, experts seek tougher sanctions”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Nairametrics | Nigeria Business, Finance & Economic News”.

  • Canonical URL set

    The canonical URL is https://nairametrics.com/.

  • 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://nairametrics.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://nairametrics.com/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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

4 to fixGoogle 6983
  • 11 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “$(...).unload is not a function”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

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

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

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

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Sign Up”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 32 other companies contacted

    Loading the homepage contacts 32 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 nairametrics.com, 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
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on nairametrics.com, including 15 speed issues, 2 SEO issues and 3 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