Website review, no card needed
accesspensions.ng website review
Visit site (opens in a new tab)Reviewed 16 November 202640 issues · 87 checks
This review found 40 issues worth fixing on accesspensions.ng, 17 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 1, 2026 | 10.8 s |
| Aug 8, 2026 | 10.8 s |
| Aug 15, 2026 | 11.4 s |
| Aug 22, 2026 | 10.9 s |
| Aug 29, 2026 | 10.5 s |
| Sep 5, 2026 | 8.0 s |
| Sep 12, 2026 | 7.9 s |
| Sep 19, 2026 | 7.7 s |
| Sep 26, 2026 | 8.1 s |
| Oct 3, 2026 | 8.8 s |
| Oct 10, 2026 | 8.9 s |
| Oct 17, 2026 | 9.4 s |
| Oct 24, 2026 | 9.3 s |
| Oct 31, 2026 | 9.2 s |
| Nov 7, 2026 | 9.4 s |
| Nov 14, 2026 | 9.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 5, 2026 | 311 ms |
| Sep 12, 2026 | 307 ms |
| Sep 19, 2026 | 307 ms |
| Sep 26, 2026 | 307 ms |
| Oct 3, 2026 | 309 ms |
| Oct 10, 2026 | 307 ms |
| Oct 17, 2026 | 299 ms |
| Oct 24, 2026 | 297 ms |
| Oct 31, 2026 | 297 ms |
| Nov 7, 2026 | 296 ms |
| Nov 14, 2026 | 300 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
How it loaded on a phone
0.7 s
1.3 s
2.0 s
2.6 s
3.3 s
4.0 s
4.6 s
5.3 s
Speed
Use efficient cache lifetimes
8.1 s · 2.9 MB110 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).
Reduce unused JavaScript
2.7 s · 685 KiBAbout 685 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
2.6 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Improve image delivery
1.9 s · 543 KiB2 images could be 543 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 134 KiBAbout 134 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.
8 third-party services on the page
8 third-party services load with your homepage (infobip.com, Google Tag Manager and Google Maps and others), adding 1.7 MB and 428 ms of main-thread time.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
infobip.com adds 265 ms
265 msinfobip.com costs a phone 265 ms of main-thread work and 564 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.
1,804 HTML elements
The page has 1,804 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 559 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 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: 453 ms
453 msYour server sent the HTML in 453 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 11.0 s
11.0 sReal visitors wait 11.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 7.5 s
7.5 sReal visitors see the first content after 7.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.7 s
3.7 sReal visitors wait 3.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 21.7 s
21.7 sYour largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Access Pensions uses cookies to collect information about y…”.
Time to Interactive: 28.7 s
28.7 sThe page becomes fully interactive after 28.7 s. Good is under 3.8 s.
Speed Index: 12.7 s
12.7 sVisually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Real-user INP: 338 ms
338 msReal visitors wait 338 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 311 ms to 300 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 10.8 s to 9.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Total Blocking Time: 55 ms
55 msScripts block the page for only 55 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.4 MB in 157 requests
6.4 MBYour homepage downloads 6.4 MB in 157 requests on a phone: images 2.9 MB (20), scripts 1.6 MB (60) and fonts 1.4 MB (25). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
369 KiB1 image is downloaded at several times the size a phone draws it, for example access_logo.webp at 2,046 px wide, shown at 137 px. Resized copies would save about 369 KiB.
2 images in older formats
2 images (181 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.
About 1.8 g of CO₂ per visit
1.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.81 g of CO₂e: 217.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
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.
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.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (20 elements)
ARIA role should be appropriate for the element: 20 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 25 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 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 H1 headlines
There are 6 <h1> headlines (“We Help in shaping Futures, Lives & AmbitionsFami…”, “Why Choose Us?” and “Introducing Access Buddy”). One clear main headline is easier for people and search engines.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
77 internal links, 37 external
The homepage links to 77 pages on accesspensions.ng and 37 external pages.
7 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “Access Pensions, (a subsidiary of the Access Corporation) is a licensed Pension Fund Administrator in Nigeria.”.
Title: 37 characters
Your title is a healthy 37 characters: “Access Pensions • Shaping your future”.
Canonical URL set
The canonical URL is https://accesspensions.ng/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://accesspensions.ng/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://accesspensions.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: 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 (962 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a title
/, https://accesspensions.ng/rsa-fund-7, https://accesspensions.ng/personal-pensions-plan and https://accesspensions.ng/pension-backed-mortgage all use the title “Access Pensions • Shaping your future”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://accesspensions.ng/about, https://accesspensions.ng/retirement-savings-account, https://accesspensions.ng/multi-fund, https://accesspensions.ng/benefits-application, https://accesspensions.ng/rsa-transfer and https://accesspensions.ng/portfolio-structure and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://accesspensions.ng/rsa-fund-7, https://accesspensions.ng/personal-pensions-plan and https://accesspensions.ng/pension-backed-mortgage use the same meta description. A description written for each page earns more clicks.
1 page slow to respond
https://accesspensions.ng/about took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 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 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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
2 checks passed
Tap targets are thumb-sized
13 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 632 words of copy
The homepage carries about 632 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: “Click to get started”.
9 calls to action
The homepage has 9 calls to action, for example “Contact”, “Click to get started” and “Click to learn more”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 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
2 trackers load before any consent
2Before 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
9 other companies contacted
Loading the homepage contacts 9 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 accesspensions.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
- jQuery
- Analytics
- Google Analytics
- Hosting
- Oracle Cloud
Company
- Headquarters
- Abuja
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 accesspensions.ng, including 22 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.