Website review, no card needed
nobubank.com website review
Visit site (opens in a new tab)Reviewed 5 November 202644 issues · 86 checks
This review found 44 issues worth fixing on nobubank.com, 19 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.5 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 163 ms |
| May 23, 2026 | 165 ms |
| May 30, 2026 | 169 ms |
| Jun 6, 2026 | 166 ms |
| Jun 13, 2026 | 164 ms |
| Jun 20, 2026 | 164 ms |
| Jun 27, 2026 | 165 ms |
| Jul 4, 2026 | 165 ms |
| Jul 11, 2026 | 164 ms |
| Jul 18, 2026 | 164 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 164 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 166 ms |
| Sep 12, 2026 | 164 ms |
| Sep 19, 2026 | 165 ms |
| Sep 26, 2026 | 161 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 164 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 161 ms |
| Oct 31, 2026 | 152 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.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.2 s
8.4 s
9.6 s
Speed
Improve image delivery
21.3 s · 14.9 MB44 images could be 14.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 21.3 s faster on a phone.
Use efficient cache lifetimes
20.1 s · 15.5 MB87 files are served with short cache lifetimes, so returning visitors download them again (15.5 MB).
Reduce unused JavaScript
2.5 s · 480 KiBAbout 480 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
1.1 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. 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, Facebook and Google CDN and others), adding 19.5 MB and 628 ms of main-thread time.
Other Google APIs/SDKs adds 1 ms
1 msOther Google APIs/SDKs costs a phone 1 ms of main-thread work and 18.6 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.
Minify JavaScript
630 ms · 77 KiB77 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 423 ms
423 msGoogle Tag Manager costs a phone 423 ms of main-thread work and 342 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: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 72 ms
72 msGoogle CDN costs a phone 72 ms of main-thread work and 349 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 206 ms. During a long task the page ignores taps.
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.
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: 3 ms
3 msYour server sent the HTML in 3 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.7 s
6.7 sReal visitors wait 6.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 58.3 s
58.3 sYour largest element takes 58.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 60.9 s
60.9 sThe page becomes fully interactive after 60.9 s. Good is under 3.8 s.
Speed Index: 12.8 s
12.8 sVisually, the page fills in at 12.8 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.24
0.24For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 461 ms
461 msScripts block taps and scrolling for 461 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.197
0.197The layout shifts by 0.197 while loading, so content jumps under the reader's thumb. Good is under 0.1.
26 images without width and height
26 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 163 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 178 ms
178 msReal visitors wait 178 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 20.0 MB in 122 requests
20.0 MBYour homepage downloads 20.0 MB in 122 requests on a phone: images 18.7 MB (73), scripts 1.2 MB (20) and stylesheets 41 KiB (9). Under 2 MB keeps phones on slow connections fast.
37 images far larger than shown
11.9 MB37 images are downloaded at several times the size a phone draws them, for example LEVEL_UP-DDay_Website-06.original.png at 1,792 px wide, shown at 210 px. Resized copies would save about 11.9 MB.
12 images over 500 KB
12 images weigh 9.3 MB together. On a phone connection a single image that size takes seconds.
39 images in older formats
39 images (14.4 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.
1 image below the first screen load straight away
1 image further down the page (69 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 5.7 g of CO₂ per visit
5.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.68 g of CO₂e: 681.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
9 buttons without a name
9 buttons have no accessible name, so screen readers announce just “button”.
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (46 elements)
All page content should be contained by landmarks: 46 elements on the page fail this check, rated moderate by axe-core.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
Hidden but focusable
5 elements hidden from screen readers can still receive keyboard focus.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (5 elements)
Elements marked as presentational should be consistently ignored: 5 elements on the page fail this check, rated minor by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 3 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.
140 internal links, 18 external
The homepage links to 140 pages on nobubank.com and 18 external pages.
6 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Fleksibilitas keuangan untuk perorangan, bisnis & UMKM dari tabungan hingga investasi deposito – karena di NOBU, No One…”.
Title: 51 characters
Your title is a healthy 51 characters: “Nobu Bank - Layanan Banking untuk Individu & Bisnis”.
Canonical URL set
The canonical URL is https://www.nobubank.com/.
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.nobubank.com/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://www.nobubank.com/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,032 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.nobubank.com/id/perorangan/e-channel is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.nobubank.com/id/perorangan/e-channel has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages slow to respond
https://www.nobubank.com/id/perorangan/simpanan/deposito, https://www.nobubank.com/id/perorangan/simpanan/giro, https://www.nobubank.com/id/perorangan/pinjaman/nobu-kpr, https://www.nobubank.com/id/perorangan/pinjaman/nobu-loan, https://www.nobubank.com/id/perorangan/pinjaman/nobu-kta and https://www.nobubank.com/id/perorangan/pinjaman/nobukasbonsukasuka and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 102 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistration') https://www.nobubank.com/id/:5:6757”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
98 of 105 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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 902 words of copy
The homepage carries about 902 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Nobu Call 1 500 278”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
13 other companies contacted
Loading the homepage contacts 13 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 nobubank.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
- Tailwind CSS
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- PT Aplikanusa Lintasarta
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on nobubank.com, including 22 speed issues, 2 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.