Website review, no card needed
creditlibanais.com website review
Visit site (opens in a new tab)Reviewed 28 October 202655 issues · 82 checks
This review found 55 issues worth fixing on creditlibanais.com, 27 of them high impact, across 82 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
56FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 11.1 s |
| May 16, 2026 | 10.8 s |
| May 23, 2026 | 10.8 s |
| May 30, 2026 | 10.4 s |
| Jun 6, 2026 | 10.0 s |
| Jun 13, 2026 | 9.3 s |
| Jun 20, 2026 | 9.3 s |
| Jun 27, 2026 | 9.5 s |
| Jul 4, 2026 | 10.8 s |
| Jul 11, 2026 | 10.9 s |
| Jul 18, 2026 | 11.0 s |
| Jul 25, 2026 | 11.2 s |
| Aug 1, 2026 | 10.8 s |
| Aug 8, 2026 | 10.3 s |
| Aug 15, 2026 | 10.0 s |
| Aug 22, 2026 | 9.3 s |
| Aug 29, 2026 | 7.3 s |
| Sep 5, 2026 | 6.9 s |
| Sep 12, 2026 | 6.8 s |
| Sep 19, 2026 | 6.5 s |
| Sep 26, 2026 | 6.9 s |
| Oct 3, 2026 | 6.9 s |
| Oct 10, 2026 | 7.0 s |
| Oct 17, 2026 | 7.2 s |
| Oct 24, 2026 | 6.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 225 ms |
| May 16, 2026 | 226 ms |
| May 23, 2026 | 225 ms |
| May 30, 2026 | 216 ms |
| Jun 6, 2026 | 220 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 181 ms |
| Jun 27, 2026 | 181 ms |
| Jul 4, 2026 | 199 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 206 ms |
| Jul 25, 2026 | 214 ms |
| Aug 1, 2026 | 210 ms |
| Aug 8, 2026 | 188 ms |
| Aug 15, 2026 | 189 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 158 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 164 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 181 ms |
| Oct 17, 2026 | 179 ms |
| Oct 24, 2026 | 176 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.9 s
1.8 s
2.8 s
3.7 s
4.6 s
5.5 s
6.5 s
7.4 s
Speed
Use efficient cache lifetimes
11.8 s · 11.1 MB142 files are served with short cache lifetimes, so returning visitors download them again (11.1 MB).
Improve image delivery
1.2 s · 7.7 MB36 images could be 7.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
7.8 s33 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.8 s.
Reduce unused JavaScript
5.1 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.
Mobile performance score: 11
11/100Your mobile performance score is 11 (desktop: 25). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google Maps and Facebook and others), adding 9.8 MB and 837 ms of main-thread time.
Reduce unused CSS
920 ms · 158 KiBAbout 158 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 920 ms faster on a phone.
Minify JavaScript
770 ms · 146 KiB146 KiB could be saved by minifying JavaScript.
creditlibanais.com adds 3 ms
3 mscreditlibanais.com costs a phone 3 ms of main-thread work and 8.3 MB 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.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 279 ms
279 msGoogle Tag Manager costs a phone 279 ms of main-thread work and 525 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.
2,655 HTML elements
The page has 2,655 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Maps adds 191 ms
191 msGoogle Maps costs a phone 191 ms of main-thread work and 396 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.
mypurecloud.com adds 177 ms
177 msmypurecloud.com costs a phone 177 ms of main-thread work and 357 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 227 ms. During a long task the page ignores taps.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Minify CSS
29 KiB29 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 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.8 s
6.8 sReal visitors wait 6.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.29
1.29For real visitors the layout shifts by 1.29 (75th percentile). Good is under 0.1.
Real-user FCP: 4.7 s
4.7 sReal visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 1.381
1.381The layout shifts by 1.381 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 22.1 s
22.1 sYour largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CLASI 1,826.43 10.27.26 YEAR HIGH 2,150.51 CHANGE % -0.129%…”.
Time to Interactive: 30.0 s
30.0 sThe page becomes fully interactive after 30.0 s. Good is under 3.8 s.
First Contentful Paint: 7.4 s
7.4 sThe first text or image appears after 7.4 s on a phone. Good is under 1.8 s.
Speed Index: 14.0 s
14.0 sVisually, the page fills in at 14.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 812 ms
812 msScripts block taps and scrolling for 812 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 827 ms
827 msReal visitors wait 827 ms for your server to start answering (75th percentile). Good is under 800 ms.
32 images without width and height
32 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user INP: 177 ms
177 msReal visitors wait 177 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 225 ms to 176 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 37% faster for real visitors
-37%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 11.1 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 12.4 MB in 278 requests
12.4 MBYour homepage downloads 12.4 MB in 278 requests on a phone: images 9.5 MB (112), scripts 2.0 MB (38) and fonts 537 KiB (11). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 6.1 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
5.7 MB8 images are downloaded at several times the size a phone draws them, for example mira-website-banner3.png at 2,783 px wide, shown at 390 px. Resized copies would save about 5.7 MB.
35 images in older formats
35 images (8.8 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 (756 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.5 g of CO₂ per visit
3.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.50 g of CO₂e: 420.5 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.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
3 tap targets too small
3 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.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (2 elements)
Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
23 links crawlers can't follow
23 links have no real href, so search engines can't follow them.
Meta description is long (195 characters)
Your meta description is 195 characters; Google truncates after about 160, so the end of your pitch is cut.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
5 checks passed
Title: 30 characters
Your title is a healthy 30 characters: “Credit Libanais - Close To You”.
Canonical URL set
The canonical URL is https://www.creditlibanais.com.lb/.
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://www.creditlibanais.com.lb/GoogleSitemap.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 1,161 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.creditlibanais.com.lb/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.
1 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.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.creditlibanais.com.lb/shutterstock_294637502261026114217161~.jpg.
38 small tap targets
38 of 101 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,161 words of copy
The homepage carries about 1,161 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US 24/7 1518” and “Apply for a card”.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
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 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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 1 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.
16 other companies contacted
Loading the homepage contacts 16 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 creditlibanais.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
- Angular
- Analytics
- Google Tag Manager
- Hosting
- Leaseweb
Company
- Founded
- 1991
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 55 issues on creditlibanais.com, including 27 speed issues, 5 SEO issues and 3 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.