Website review, no card needed

accessbankplc.com logo

accessbankplc.com website review

Visit site (opens in a new tab)Reviewed 3 November 202656 issues · 94 checks

This review found 56 issues worth fixing on accessbankplc.com, 23 of them high impact, across 94 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
8.3 s6.5 sMay 16Oct 317.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20268.1 s
May 23, 20268.0 s
May 30, 20267.7 s
Jun 6, 20267.1 s
Jun 13, 20266.8 s
Jun 20, 20266.7 s
Jun 27, 20266.8 s
Jul 4, 20267.1 s
Jul 11, 20267.2 s
Jul 18, 20267.3 s
Jul 25, 20268.0 s
Aug 1, 20268.0 s
Aug 8, 20268.0 s
Aug 15, 20268.0 s
Aug 22, 20267.5 s
Aug 29, 20267.3 s
Sep 5, 20267.2 s
Sep 12, 20267.1 s
Sep 19, 20267.1 s
Sep 26, 20267.2 s
Oct 3, 20267.4 s
Oct 10, 20267.7 s
Oct 17, 20267.7 s
Oct 24, 20267.7 s
Oct 31, 20267.5 s
Real-visitor tap response (INP)75th percentile, phones
240 ms221 msMay 16Oct 31231 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026229 ms
May 23, 2026226 ms
May 30, 2026225 ms
Jun 6, 2026223 ms
Jun 13, 2026224 ms
Jun 20, 2026227 ms
Jun 27, 2026226 ms
Jul 4, 2026228 ms
Jul 11, 2026229 ms
Jul 18, 2026232 ms
Jul 25, 2026238 ms
Aug 1, 2026237 ms
Aug 8, 2026235 ms
Aug 15, 2026233 ms
Aug 22, 2026229 ms
Aug 29, 2026228 ms
Sep 5, 2026226 ms
Sep 12, 2026224 ms
Sep 19, 2026223 ms
Sep 26, 2026223 ms
Oct 3, 2026226 ms
Oct 10, 2026227 ms
Oct 17, 2026229 ms
Oct 24, 2026231 ms
Oct 31, 2026231 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 accessbankplc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. accessbankplc.com at 0.9 s0.9 s
  2. accessbankplc.com at 1.9 s1.9 s
  3. accessbankplc.com at 2.8 s2.8 s
  4. accessbankplc.com at 3.7 s3.7 s
  5. accessbankplc.com at 4.7 s4.7 s
  6. accessbankplc.com at 5.6 s5.6 s
  7. accessbankplc.com at 6.5 s6.5 s
  8. accessbankplc.com at 7.5 s7.5 s

Speed

12 to fix41
  • Use efficient cache lifetimes

    1.9 s · 3.9 MB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 41

    41/100

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

  • Improve image delivery

    2.0 MB

    13 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    900 ms · 480 KiB

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

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

  • Reduce unused CSS

    600 ms · 119 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 934 KiB and 622 ms of main-thread time.

  • Google Tag Manager adds 443 ms

    443 ms

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

  • Main-thread work: 3.8 s

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

  • Minify JavaScript

    300 ms · 53 KiB

    53 KiB could be saved by minifying JavaScript.

  • 2,818 HTML elements

    The page has 2,818 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Font display

    200 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

  • Minify CSS

    150 ms · 26 KiB

    26 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 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: 154 ms

    154 ms

    Your server sent the HTML in 154 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: 10.1 s

    10.1 s

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

  • Real-user FCP: 5.7 s

    5.7 s

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

  • Real-user TTFB: 3.5 s

    3.5 s

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

  • Largest Contentful Paint: 133.8 s

    133.8 s

    Your largest element takes 133.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Access Bank website uses cookies to collect information abo…”.

  • Speed Index: 36.4 s

    36.4 s

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

  • Time to Interactive: 135.8 s

    135.8 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user INP: 229 ms

    229 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

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

Images and page weight

4 to fix38
  • Page weight: 30.5 MB in 150 requests

    30.5 MB

    Your homepage downloads 30.5 MB in 150 requests on a phone: images 27.8 MB (80), scripts 1.2 MB (28) and fonts 1.2 MB (21). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

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

  • 25 images in older formats

    25 images (4.9 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.

  • 3 images below the first screen load straight away

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

  • About 8.6 g of CO₂ per visit

    8.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 8.64 g of CO₂e: 1037.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

12 to fixGoogle 7183
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 5 text elements with low contrast

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

  • 3 tap targets too small

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • <marquee> elements are deprecated and must not be used (1 element)

    <marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

  • 21 images without alt text

    21 images have no alt text, which hurts accessibility and image search.

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

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

  • 6 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

7 to fixGoogle 8370
  • Title is short (18 characters)

    Your title is only 18 characters: “Home | Access Bank”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“AMERICAN EXPRESS IS HERE UNCOVER MORE REWARDING W…”, “Unlock a world of possibility just for you! Exper…” and “Earn Locally, Invest around the world You can dec…”). One clear main headline is easier for people and search engines.

  • Meta description is long (239 characters)

    Your meta description is 239 characters; Google truncates after about 160, so the end of your pitch is cut.

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

    There is no robots.txt at accessbankplc.com/robots.txt, the first file search crawlers ask for.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 467 internal links, 57 external

    The homepage links to 467 pages on accessbankplc.com and 57 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.accessbankplc.com/.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.accessbankplc.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://www.accessbankplc.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 13 pages without a meta description

    https://www.accessbankplc.com/sustainable-banking, https://www.accessbankplc.com/investor-relations, https://www.accessbankplc.com/media, https://www.accessbankplc.com/contact-us/branch-atm-locator, https://www.accessbankplc.com/business/market-rates and https://www.accessbankplc.com/personal and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.accessbankplc.com/about-us, https://www.accessbankplc.com/investor-relations, https://www.accessbankplc.com/contact-us and https://www.accessbankplc.com/bancassurance have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.accessbankplc.com/media, https://www.accessbankplc.com/contact-us/branch-atm-locator, https://www.accessbankplc.com/business/market-rates, https://www.accessbankplc.com/personal and https://www.accessbankplc.com/corporate took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Titles are unique

    Every page we checked has its own title.

  • 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 9270
  • 1 broken image

    1 image failed to load on a phone, for example https://www.accessbankplc.com/assets/images/country-logos/nigeria.svg.

  • 16 small tap targets

    16 of 37 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 “Failed to load resource: the server responded with a status of 404 ()”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix71
  • 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 social proof

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

  • About 617 words of copy

    The homepage carries about 617 words of visible text.

5 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “Contact Us”, “Learn more” and “Get a Loan”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 16 cookies set on arrival

    16

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 accessbankplc.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
jQuery
Analytics
Google Analytics

Company

Employees
28,121
Founded
1989
Headquarters
Lagos State

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 56 issues on accessbankplc.com, including 23 speed issues, 7 SEO issues 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