Website review, no card needed

nem-insurance.com logo

nem-insurance.com website review

Visit site (opens in a new tab)Reviewed 1 November 202633 issues · 83 checks

This review found 33 issues worth fixing on nem-insurance.com, 12 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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
4.7 s3.9 sMay 9Oct 244.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.6 s
May 16, 20264.5 s
May 23, 20264.4 s
May 30, 20264.4 s
Jun 6, 20264.5 s
Jun 13, 20264.2 s
Jun 20, 20264.0 s
Jun 27, 20264.1 s
Jul 4, 20264.2 s
Jul 11, 20264.5 s
Jul 18, 20264.5 s
Jul 25, 20264.4 s
Aug 1, 20264.3 s
Aug 8, 20264.3 s
Aug 15, 20264.4 s
Aug 22, 20264.5 s
Aug 29, 20264.4 s
Sep 5, 20264.4 s
Sep 12, 20264.3 s
Sep 19, 20264.3 s
Sep 26, 20264.4 s
Oct 3, 20264.5 s
Oct 10, 20264.5 s
Oct 17, 20264.4 s
Oct 24, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
332 ms75 msMay 9Oct 24302 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026113 ms
May 16, 2026121 ms
May 23, 2026114 ms
May 30, 2026116 ms
Jun 6, 2026120 ms
Jun 13, 2026118 ms
Jun 20, 2026120 ms
Jun 27, 2026121 ms
Jul 4, 2026123 ms
Jul 11, 2026118 ms
Jul 18, 2026112 ms
Jul 25, 2026107 ms
Aug 1, 2026105 ms
Aug 8, 2026106 ms
Aug 15, 2026112 ms
Aug 22, 2026111 ms
Aug 29, 2026113 ms
Sep 5, 2026122 ms
Sep 12, 2026122 ms
Sep 19, 2026140 ms
Sep 26, 2026140 ms
Oct 3, 2026140 ms
Oct 10, 2026171 ms
Oct 17, 2026201 ms
Oct 24, 2026302 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 nem-insurance.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nem-insurance.com at 0.7 s0.7 s
  2. nem-insurance.com at 1.4 s1.4 s
  3. nem-insurance.com at 2.1 s2.1 s
  4. nem-insurance.com at 2.8 s2.8 s
  5. nem-insurance.com at 3.5 s3.5 s
  6. nem-insurance.com at 4.2 s4.2 s
  7. nem-insurance.com at 4.9 s4.9 s
  8. nem-insurance.com at 5.6 s5.6 s

Speed

6 to fix51
  • Main-thread work: 6.8 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and prismic.io and others), adding 959 KiB and 988 ms of main-thread time.

  • Mobile performance score: 51

    51/100

    Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

  • Google CDN adds 887 ms

    887 ms

    Google CDN costs a phone 887 ms of main-thread work and 741 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.

  • 19 long tasks on the main thread

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

  • Reduce unused JavaScript

    150 ms · 455 KiB

    About 455 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    91 KiB

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

  • Render-blocking requests

    50 ms

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

  • Reduce unused CSS

    33 KiB

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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.

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

11 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.9 s

    4.9 s

    Real visitors wait 4.9 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: 2.1 s

    2.1 s

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

  • Time to Interactive: 14.4 s

    14.4 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Real-user INP: 357 ms

    357 ms

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

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

    +115%

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

  • Speed Index: 5.8 s

    5.8 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Cumulative Layout Shift: 0.003

    0.003

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

2 to fix83
  • Page weight: 2.7 MB in 95 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 95 requests on a phone: scripts 1.1 MB (31), images 1.0 MB (45) and other files 384 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • 1 image in older formats

    1 image (363 KiB) is 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 below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.76 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8990
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 5 tap targets too small

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

  • 1 text element with low contrast

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail 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.

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 82 images in the HTML carry an alt attribute.

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

SEO

1 to fixGoogle 10096
  • No structured data

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

  • 29 internal links, 8 external

    The homepage links to 29 pages on nem-insurance.com and 8 external pages.

7 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Nigeria's leading insurer since 1948. Buy motor, home, travel, marine, oil & gas insurance online. Regulated by NAICOM.…”.

  • One H1 headline

    Your main headline reads: “Drive with totalconfidence.”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “NEM Insurance Plc | No.1 Motor & General Insurance in Nigeria”.

  • Canonical URL set

    The canonical URL is https://nem-insurance.com/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://nem-insurance.com/sitemap.xml.

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://nem-insurance.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.

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,033 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 2 pages share a meta description

    https://nem-insurance.com/about and https://nem-insurance.com/leadership use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

2 to fixGoogle 9687
  • 10 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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 analytics detected

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

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

    The homepage carries about 1,039 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: “Get a Quote” and “Buy Insurance”.

  • 1 call to action

    The homepage has 1 call to action, for example “Buy Insurance”.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks and 3 trust badges.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 nem-insurance.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Netlify

Company

Founded
1948
Headquarters
Lagos

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on nem-insurance.com, including 17 speed issues, 1 SEO issue and 2 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