Website review, no card needed
crusaderpensions.com website review
Visit site (opens in a new tab)Reviewed 30 October 202642 issues · 86 checks
This review found 42 issues worth fixing on crusaderpensions.com, 19 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 6.1 s |
| Aug 1, 2026 | 6.3 s |
| Aug 8, 2026 | 6.1 s |
| Aug 15, 2026 | 6.0 s |
| Aug 22, 2026 | 5.6 s |
| Aug 29, 2026 | 5.3 s |
| Sep 5, 2026 | 5.3 s |
| Sep 12, 2026 | 5.3 s |
| Sep 19, 2026 | 5.4 s |
| Sep 26, 2026 | 5.5 s |
| Oct 3, 2026 | 5.6 s |
| Oct 10, 2026 | 5.9 s |
| Oct 17, 2026 | 6.1 s |
| Oct 24, 2026 | 6.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 261 ms |
| May 16, 2026 | 268 ms |
| May 23, 2026 | 269 ms |
| May 30, 2026 | 275 ms |
| Jun 6, 2026 | 274 ms |
| Jun 13, 2026 | 273 ms |
| Jun 20, 2026 | 260 ms |
| Jun 27, 2026 | 245 ms |
| Jul 4, 2026 | 245 ms |
| Jul 11, 2026 | 247 ms |
| Jul 18, 2026 | 244 ms |
| Jul 25, 2026 | 239 ms |
| Aug 1, 2026 | 235 ms |
| Aug 8, 2026 | 223 ms |
| Aug 15, 2026 | 226 ms |
| Aug 22, 2026 | 226 ms |
| Aug 29, 2026 | 236 ms |
| Sep 5, 2026 | 245 ms |
| Sep 12, 2026 | 252 ms |
| Sep 19, 2026 | 253 ms |
| Sep 26, 2026 | 245 ms |
| Oct 3, 2026 | 243 ms |
| Oct 10, 2026 | 239 ms |
| Oct 17, 2026 | 231 ms |
| Oct 24, 2026 | 231 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.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Reduce unused JavaScript
3.6 s · 753 KiBAbout 753 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Render-blocking requests
4.0 s67 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Use efficient cache lifetimes
3.0 s · 777 KiB174 files are served with short cache lifetimes, so returning visitors download them again (777 KiB).
Improve image delivery
500 ms · 1.3 MB7 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
620 ms · 130 KiBAbout 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 620 ms faster on a phone.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 966 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,071 HTML elements
The page has 2,071 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (LiveChat, ClickDesk and Google Fonts), adding 1.0 MB and 77 ms of main-thread time.
LiveChat adds 53 ms
53 msLiveChat costs a phone 53 ms of main-thread work and 593 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.
ClickDesk adds 23 ms
23 msClickDesk costs a phone 23 ms of main-thread work and 361 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 175 ms. During a long task the page ignores taps.
Legacy JavaScript
49 KiBPolyfills for old browsers add 49 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
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 279 ms
279 msYour server sent the HTML in 279 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: 9.8 s
9.8 sReal visitors wait 9.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.26
0.26For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.
Real-user FCP: 4.3 s
4.3 sReal visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.7 s
2.7 sReal visitors wait 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 20.7 s
20.7 sYour largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.1 s
21.1 sThe page becomes fully interactive after 21.1 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user INP: 223 ms
223 msReal visitors wait 223 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 68% slower for real visitors
+68%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 6.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 261 ms to 231 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Total Blocking Time: 9 ms
9 msScripts block the page for only 9 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.3 MB in 201 requests
4.3 MBYour homepage downloads 4.3 MB in 201 requests on a phone: images 1.7 MB (20), scripts 1.6 MB (81) and fonts 668 KiB (9). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
unnamed-19.png weighs 664 KiB. On a phone connection a single image that size takes seconds.
8 images in older formats
8 images (1.7 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.
4 images below the first screen load straight away
4 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
144 KiB2 images are downloaded at several times the size a phone draws them, for example unnamed-19.png at 1,005 px wide, shown at 300 px. Resized copies would save about 144 KiB.
About 1.2 g of CO₂ per visit
1.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 147.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
19 text elements with low contrast
19 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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (37 elements)
All page content should be contained by landmarks: 37 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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 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 checks passed
Every image has alt text
All 33 images in the HTML carry an alt attribute.
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“Demonstrating our commitment to quality, efficien…”, “Safeguarding your data with globally recognised i…” and ““Pension Fund Managers in the ‘AA-(PFM)’ category…”). One clear main headline is easier for people and search engines.
Meta description is long (167 characters)
Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
214 internal links, 68 external
The homepage links to 214 pages on crusaderpensions.com and 68 external pages.
6 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “CrusaderSterling Pensions - Pension Company in Nigeria”.
Canonical URL set
The canonical URL is https://crusaderpensions.com/.
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://crusaderpensions.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,406 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://crusaderpensions.com/llms.txt (67 KiB, 223 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
14 pages without an H1
https://crusaderpensions.com/about-us, https://crusaderpensions.com/leadership, https://crusaderpensions.com/management, https://crusaderpensions.com/retirement-savings, https://crusaderpensions.com/retirement-pack and https://crusaderpensions.com/foreign-currency-pension and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
6 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
28 of 30 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 914 words of copy
The homepage carries about 914 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
20 calls to action
The homepage has 20 calls to action, for example “Contact”, “Learn More” and “Learn More ➜”.
2 short forms
2 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 14 testimonial or review blocks and 4 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 1 email link.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 4 of them by other companies (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.
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 crusaderpensions.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
- React
- Analytics
- Google Analytics
- Hosting
- Hostinger
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on crusaderpensions.com, including 23 speed issues and 3 SEO issues. 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.