Website review, no card needed
cf.lk website review
Visit site (opens in a new tab)Reviewed 1 November 202646 issues · 88 checks
This review found 46 issues worth fixing on cf.lk, 17 of them high impact, across 88 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.7 s |
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.9 s |
| May 30, 2026 | 4.9 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 5.0 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.9 s |
| Oct 3, 2026 | 5.1 s |
| Oct 10, 2026 | 5.2 s |
| Oct 17, 2026 | 5.3 s |
| Oct 24, 2026 | 5.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 236 ms |
| May 16, 2026 | 236 ms |
| May 23, 2026 | 236 ms |
| May 30, 2026 | 235 ms |
| Jun 6, 2026 | 228 ms |
| Jun 13, 2026 | 227 ms |
| Jun 20, 2026 | 223 ms |
| Jun 27, 2026 | 223 ms |
| Jul 4, 2026 | 226 ms |
| Jul 11, 2026 | 228 ms |
| Jul 18, 2026 | 234 ms |
| Jul 25, 2026 | 239 ms |
| Aug 1, 2026 | 243 ms |
| Aug 8, 2026 | 244 ms |
| Aug 15, 2026 | 241 ms |
| Aug 22, 2026 | 239 ms |
| Aug 29, 2026 | 241 ms |
| Sep 5, 2026 | 242 ms |
| Sep 12, 2026 | 247 ms |
| Sep 19, 2026 | 246 ms |
| Sep 26, 2026 | 245 ms |
| Oct 3, 2026 | 245 ms |
| Oct 10, 2026 | 241 ms |
| Oct 17, 2026 | 243 ms |
| Oct 24, 2026 | 241 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
Speed
Use efficient cache lifetimes
2.5 s · 4.8 MB107 files are served with short cache lifetimes, so returning visitors download them again (4.8 MB).
Reduce unused JavaScript
1.2 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
2.5 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, serviceform.com and Google CDN and others), adding 2.4 MB and 998 ms of main-thread time.
Reduce unused CSS
900 ms · 210 KiBAbout 210 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 366 ms
366 msGoogle Tag Manager costs a phone 366 ms of main-thread work and 699 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.
serviceform.com adds 278 ms
278 msserviceform.com costs a phone 278 ms of main-thread work and 911 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.
Google CDN adds 253 ms
253 msGoogle CDN costs a phone 253 ms of main-thread work and 736 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.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 281 ms. During a long task the page ignores taps.
Improve image delivery
213 KiB4 images could be 213 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
150 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
25 KiB25 KiB could be saved by minifying JavaScript.
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 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 54 ms
54 msYour server sent the HTML in 54 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: 6.0 s
6.0 sReal visitors wait 6.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.2 s
5.2 sReal visitors see the first content after 5.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 36.3 s
36.3 sThe page becomes fully interactive after 36.3 s. Good is under 3.8 s.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user INP: 209 ms
209 msReal visitors wait 209 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 210 ms
210 msScripts block taps and scrolling for 210 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 236 ms to 241 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.7 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 7.1 MB in 179 requests
7.1 MBYour homepage downloads 7.1 MB in 179 requests on a phone: scripts 2.8 MB (74), images 2.0 MB (51) and fonts 1.5 MB (10). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
tuk-tuk-leasing.jpg weighs 675 KiB. On a phone connection a single image that size takes seconds.
6 images in older formats
6 images (1.6 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.
5 images below the first screen load straight away
5 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
94 KiB1 image is downloaded at several times the size a phone draws it, for example banner_0.jpg at 1,500 px wide, shown at 370 px. Resized copies would save about 94 KiB.
About 2.0 g of CO₂ per visit
2.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.00 g of CO₂e: 240.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (29 characters)
Your title is only 29 characters: “Central Finance Company PLC |”. Between 30 and 65 characters leaves room to say what you do and for whom.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
95 internal links, 6 external
The homepage links to 95 pages on cf.lk and 6 external pages.
6 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Providing dynamic and innovative financial solutions since 1957, Central Finance Company Plc is Sri Lanka’s leading fin…”.
Canonical URL set
The canonical URL is https://cf.lk/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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.
XML sitemap found
Your XML sitemap is reachable at https://cf.lk/sitemap.xml.
AI search readiness
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://cf.lk/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,065 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
/, https://cf.lk/si and https://cf.lk/ta all use the title “Central Finance Company PLC |”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://cf.lk/customer-charter, https://cf.lk/regulatory-policies, https://cf.lk/si, https://cf.lk/ta, https://cf.lk/covid-19-special-notices and https://cf.lk/board-of-directors and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://cf.lk/si, https://cf.lk/ta and https://cf.lk/careers have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://cf.lk/achievements 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.
4 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.
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
14 small tap targets
14 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 1,000 words of copy
The homepage carries about 1,000 words of visible text.
5 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us” and “General Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
24 other companies contacted
Loading the homepage contacts 24 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 cf.lk, 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 | Google Tag Manager | Hotjar
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on cf.lk, including 22 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.