Website review, no card needed
bankboubyan.com website review
Visit site (opens in a new tab)Reviewed 19 November 202629 issues · 78 checks
This review found 29 issues worth fixing on bankboubyan.com, 10 of them high impact, across 78 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.7 s |
| Oct 31, 2026 | 3.6 s |
| Nov 7, 2026 | 3.5 s |
| Nov 14, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 192 ms |
| Jun 6, 2026 | 193 ms |
| Jun 13, 2026 | 197 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 191 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 176 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 168 ms |
| Aug 8, 2026 | 165 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 178 ms |
| Aug 29, 2026 | 181 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 179 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 151 ms |
| Oct 10, 2026 | 151 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 145 ms |
| Nov 7, 2026 | 139 ms |
| Nov 14, 2026 | 144 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
1.3 s
2.6 s
3.8 s
5.1 s
6.4 s
7.7 s
9.0 s
10.2 s
Speed
Reduce unused JavaScript
2.3 s · 977 KiBAbout 977 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
2.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Snapchat and others), adding 1.0 MB and 792 ms of main-thread time.
Google Tag Manager adds 472 ms
472 msGoogle Tag Manager costs a phone 472 ms of main-thread work and 540 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.
Use efficient cache lifetimes
362 KiB14 files are served with short cache lifetimes, so returning visitors download them again (362 KiB).
Reduce unused CSS
150 ms · 67 KiBAbout 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 208 ms. During a long task the page ignores taps.
Document request latency
136 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Improve image delivery
60 KiB2 images could be 60 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
54 KiBPolyfills for old browsers add 54 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: 359 ms
359 msYour server sent the HTML in 359 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.
Largest Contentful Paint: 11.7 s
11.7 sYour largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hp banners- Boubyan.jpeg”.
Speed Index: 14.8 s
14.8 sVisually, the page fills in at 14.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 885 ms
885 msReal visitors wait 885 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 489 ms
489 msScripts block taps and scrolling for 489 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.146
0.146The layout shifts by 0.146 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 171 ms
171 msReal visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 192 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.3 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 3.8 MB in 138 requests
3.8 MBYour homepage downloads 3.8 MB in 138 requests on a phone: scripts 2.6 MB (52), images 732 KiB (50) and stylesheets 214 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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 (74 elements)
All page content should be contained by landmarks: 74 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 65 images in the HTML carry an alt attribute.
45 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: 45 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
46 internal links, 17 external
The homepage links to 46 pages on bankboubyan.com and 17 external pages.
8 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Discover Boubyan Group’s commitment to innovation, global banking, and Sharia-compliant financial solutions. Explore ou…”.
One H1 headline
Your main headline reads: “Empowering Financial Growth with Boubyan Group”.
Title: 45 characters
Your title is a healthy 45 characters: “Boubyan Bank | Leading Islamic Bank in Kuwait”.
Canonical URL set
The canonical URL is https://www.bankboubyan.com/en.
Structured data in place
Structured data found: BreadcrumbList, Organization 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://www.bankboubyan.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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 (544 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bankboubyan.com/llms.txt (26 KiB, 178 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://www.bankboubyan.com/en/contact-us, https://www.bankboubyan.com/en/terms-and-conditions, https://www.bankboubyan.com/en/disclaimer, https://www.bankboubyan.com/en/investor-relations/corporate-governance and https://www.bankboubyan.com/en/investor-relations/sustainability-report have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.bankboubyan.com/en/contact-us, https://www.bankboubyan.com/en/legal-commitments-and-policies, https://www.bankboubyan.com/en/disclaimer, https://www.bankboubyan.com/en/investor-relations/corporate-governance and https://www.bankboubyan.com/en/report-fraud have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.bankboubyan.com/en/contact-us and https://www.bankboubyan.com/en/fees-and-commissions have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
4 pages slow to respond
https://www.bankboubyan.com/en/locate-us, https://www.bankboubyan.com/en/terms-and-conditions, https://www.bankboubyan.com/en/legal-commitments-and-policies and https://www.bankboubyan.com/en/disclaimer took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 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
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://www.bankboubyan.com/bnith__gTwutRet8B8oiouA5TrtVsbrFo-NuHntUIF1pSSqum2FLA6OgIQ81iYfwWrGsVIA…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
32 of 33 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 820 words of copy
The homepage carries about 820 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “contact us”, “Contact us” and “Learn more”.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 3 mores (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
17 other companies contacted
Loading the homepage contacts 17 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 bankboubyan.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
- Next.js
- Hosting
- Cloudflare
Company
- Founded
- 2004
- Headquarters
- Kuwait City
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on bankboubyan.com, including 17 speed 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.