Website review, no card needed

krungsri.com logo

krungsri.com website review

Visit site (opens in a new tab)Reviewed 29 October 202655 issues · 98 checks

This review found 55 issues worth fixing on krungsri.com, 21 of them high impact, across 98 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.7 s3.9 sMay 9Oct 244.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.0 s
May 23, 20264.0 s
May 30, 20264.0 s
Jun 6, 20264.1 s
Jun 13, 20264.2 s
Jun 20, 20264.3 s
Jun 27, 20264.4 s
Jul 4, 20264.5 s
Jul 11, 20264.4 s
Jul 18, 20264.3 s
Jul 25, 20264.3 s
Aug 1, 20264.3 s
Aug 8, 20264.3 s
Aug 15, 20264.4 s
Aug 22, 20264.3 s
Aug 29, 20264.3 s
Sep 5, 20264.4 s
Sep 12, 20264.4 s
Sep 19, 20264.4 s
Sep 26, 20264.4 s
Oct 3, 20264.5 s
Oct 10, 20264.5 s
Oct 17, 20264.5 s
Oct 24, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
324 ms283 msMay 9Oct 24319 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026299 ms
May 16, 2026292 ms
May 23, 2026289 ms
May 30, 2026288 ms
Jun 6, 2026291 ms
Jun 13, 2026291 ms
Jun 20, 2026292 ms
Jun 27, 2026294 ms
Jul 4, 2026291 ms
Jul 11, 2026290 ms
Jul 18, 2026289 ms
Jul 25, 2026289 ms
Aug 1, 2026294 ms
Aug 8, 2026297 ms
Aug 15, 2026302 ms
Aug 22, 2026308 ms
Aug 29, 2026312 ms
Sep 5, 2026314 ms
Sep 12, 2026312 ms
Sep 19, 2026307 ms
Sep 26, 2026306 ms
Oct 3, 2026309 ms
Oct 10, 2026312 ms
Oct 17, 2026317 ms
Oct 24, 2026319 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

Full-page screenshot of krungsri.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. krungsri.com at 1.3 s1.3 s
  2. krungsri.com at 2.6 s2.6 s
  3. krungsri.com at 3.9 s3.9 s
  4. krungsri.com at 5.3 s5.3 s
  5. krungsri.com at 6.6 s6.6 s
  6. krungsri.com at 7.9 s7.9 s
  7. krungsri.com at 9.2 s9.2 s
  8. krungsri.com at 10.5 s10.5 s

Speed

17 to fix43
  • Render-blocking requests

    8.0 s

    33 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.0 s.

  • Reduce unused JavaScript

    4.7 s · 924 KiB

    About 924 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

  • Reduce unused CSS

    4.3 s · 812 KiB

    About 812 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.3 s faster on a phone.

  • Font display

    3.0 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).

  • Minify CSS

    1.1 s · 216 KiB

    216 KiB could be saved by minifying CSS.

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    750 ms · 1.5 MB

    10 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

  • Reduce initial server response time

    959 ms

    Reduce initial server response time. Google estimates savings of 959 ms on a phone.

  • Document request latency

    950 ms

    The HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    750 ms · 163 KiB

    163 KiB could be saved by minifying JavaScript.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, cookieplus.com and Clarity and others), adding 1.0 MB and 593 ms of main-thread time.

  • Google Tag Manager adds 549 ms

    549 ms

    Google Tag Manager costs a phone 549 ms of main-thread work and 964 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.

  • Improve image delivery

    300 ms · 196 KiB

    9 images could be 196 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 2.7 s

    A phone's processor spends 2.7 s on main-thread work while loading, 804 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 252 ms. During a long task the page ignores taps.

  • 2,090 HTML elements

    The page has 2,090 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 1.1 s

    1.1 s

    Your server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Legacy JavaScript

    150 ms · 25 KiB

    Polyfills for old browsers add 25 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.

Core Web Vitals

12 to fix33
  • 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.

  • First Contentful Paint: 8.8 s

    8.8 s

    The first text or image appears after 8.8 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 22.0 s

    22.0 s

    Your largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “มาตรการช่วยเหลือลูกค้าที่ได้รับผลกระทบจากน้ำท่วม หรือสถานกา…”.

  • Time to Interactive: 28.8 s

    28.8 s

    The page becomes fully interactive after 28.8 s. Good is under 3.8 s.

  • Speed Index: 13.5 s

    13.5 s

    Visually, the page fills in at 13.5 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 3.3 s

    3.3 s

    Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 377 ms

    377 ms

    Real visitors wait 377 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.8 s

    2.8 s

    Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.159

    0.159

    The layout shifts by 0.159 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 270 ms

    270 ms

    Scripts block taps and scrolling for 270 ms in total while the page loads. Good is under 200 ms.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 299 ms to 319 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 15% slower for real visitors

    +15%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 checks passed
  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

Images and page weight

2 to fix69
  • Page weight: 5.0 MB in 111 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 111 requests on a phone: scripts 1.7 MB (38), fonts 1.5 MB (10) and stylesheets 858 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    bts-world-tour-arirang-banner-mobile.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image below the first screen load straight away

    1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.42 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

12 to fixGoogle 7385
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 11 text elements with low contrast

    11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (25 elements)

    All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 8 form fields without a label

    8 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9290
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 317 internal links, 43 external

    The homepage links to 317 pages on krungsri.com and 43 external pages.

7 checks passed
  • Meta description: 107 characters

    Your meta description is 107 characters: “เข้าใจและรู้ใจลูกค้า ด้วยบริการสินเชี่อส่วนบุคคลที่หลากหลายและครอบคลุมทุกความต้องการ โดยธนาคารกรุงศรีอยุธยา”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “ลูกค้าบุคคล | ธนาคารกรุงศรีอยุธยา จำกัด (มหาชน)”.

  • Canonical URL set

    The canonical URL is https://www.krungsri.com/th/personal.

  • Structured data in place

    Structured data found: Organization.

  • 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.krungsri.com/sitemap.xml.

AI search readiness

100
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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

  • llms.txt published

    The site publishes https://www.krungsri.com/llms.txt (195 KiB, 356 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.krungsri.com/th/personal/mutual-fund, whose canonical is https://www.krungsri.com/th/personal/mutual-fund/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.krungsri.com/th/business, https://www.krungsri.com/jp/japan/home and https://www.krungsri.com/en/personal have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.krungsri.com/jp/japan/home has 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.

  • 3 pages slow to respond

    https://www.krungsri.com/th/business, https://www.krungsri.com/th/investor-relations/main and https://www.krungsri.com/th/personal/mutual-fund took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 172 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.

  • 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 to fixGoogle 9279
  • 13 small tap targets

    13 of 43 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://scripts.clarity.ms/0.8.73-beta/clarity.js' violates the following Content Security Policy d…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix60
  • 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 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Only about 58 words

    The homepage has only about 58 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

5 checks passed
  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Microsoft Clarity (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

    10

    Opening 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 krungsri.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Imperva

Company

Founded
1947
Headquarters
Bangkok

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 krungsri.com, including 29 speed issues, 1 SEO issue and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25