Website review, no card needed
bjc.co.th website review
Visit site (opens in a new tab)Reviewed 4 November 202646 issues · 89 checks
This review found 46 issues worth fixing on bjc.co.th, 18 of them high impact, across 89 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.7 s |
| Jun 6, 2026 | 4.5 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.8 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.5 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 4.3 s |
| Oct 24, 2026 | 4.4 s |
| Oct 31, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 74 ms |
| May 23, 2026 | 74 ms |
| May 30, 2026 | 74 ms |
| Jun 6, 2026 | 73 ms |
| Jun 13, 2026 | 72 ms |
| Jun 20, 2026 | 71 ms |
| Jun 27, 2026 | 70 ms |
| Jul 4, 2026 | 67 ms |
| Jul 11, 2026 | 70 ms |
| Jul 18, 2026 | 68 ms |
| Jul 25, 2026 | 74 ms |
| Aug 1, 2026 | 80 ms |
| Aug 15, 2026 | 81 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 82 ms |
| Sep 5, 2026 | 81 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
Improve image delivery
1.6 s · 7.7 MB49 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.6 s faster on a phone.
Render-blocking requests
4.0 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Font display
1.6 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
330 ms · 50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 330 ms faster on a phone.
Minify JavaScript
160 ms · 39 KiB39 KiB could be saved by minifying JavaScript.
Minify CSS
160 ms · 19 KiB19 KiB could be saved by minifying CSS.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 181 KiB and 92 ms of main-thread time.
Reduce unused JavaScript
93 KiBAbout 93 KiB of JavaScript is downloaded but never used on this page.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 91 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
16 KiB1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 294 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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: 4.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.6 s
4.6 sReal visitors see the first content after 4.6 s (75th percentile). Good is under 1.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 10.0 s
10.0 sThe page becomes fully interactive after 10.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.376
0.376The layout shifts by 0.376 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.17
0.17For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (2.7 s).
42 images without width and height
42 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 74 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user TTFB: 674 ms
674 msReal visitors wait 674 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 34 ms
34 msScripts block the page for only 34 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 10.1 MB in 118 requests
10.1 MBYour homepage downloads 10.1 MB in 118 requests on a phone: images 8.5 MB (59), fonts 1,023 KiB (5) and scripts 391 KiB (26). Under 2 MB keeps phones on slow connections fast.
19 images far larger than shown
3.5 MB19 images are downloaded at several times the size a phone draws them, for example S__660914180_01.jpg at 1,278 px wide, shown at 360 px. Resized copies would save about 3.5 MB.
3 images over 500 KB
3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.
40 images in older formats
40 images (8.2 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.
20 images below the first screen load straight away
20 images further down the page (6.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.9 g of CO₂ per visit
2.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.85 g of CO₂e: 342.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Orphan list items
Some list items are not inside a list.
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
51 images without alt text
51 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
42 links without text
42 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (12 characters)
Your title is only 12 characters: “BJC Official”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
18 H1 headlines
There are 18 <h1> headlines (“A.D. 1882”, “A.D. 1924” and “A.D. 1965”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
77 internal links, 7 external
The homepage links to 77 pages on bjc.co.th and 7 external pages.
2 checks passed
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.bjc.co.th/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.bjc.co.th/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 (818 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages share a title
https://www.bjc.co.th/home/index/language/th, https://www.bjc.co.th/home/index/language/en, https://www.bjc.co.th/contact, https://www.bjc.co.th/career, https://www.bjc.co.th/home/index and https://www.bjc.co.th/home and 9 others all use the title “Radware Captcha Page”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.bjc.co.th/home/index/language/th, https://www.bjc.co.th/home/index/language/en, https://www.bjc.co.th/contact, https://www.bjc.co.th/career, https://www.bjc.co.th/home/index and https://www.bjc.co.th/home and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages with very little text
https://www.bjc.co.th/home/index/language/th, https://www.bjc.co.th/home/index/language/en, https://www.bjc.co.th/contact, https://www.bjc.co.th/career, https://www.bjc.co.th/home/index and https://www.bjc.co.th/home and 9 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 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.
Every page has an H1
Each page we checked has a main headline.
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
30 small tap targets
30 of 80 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://bjc.co.th/18f5227b-e27b-445a-a53f-f845fbe69b40/stormcaster.js' violates the following Conte…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
6 low-resolution images
6 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
Thin social proof
Social proof on the homepage: 1 trust badge. 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 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 404 words of copy
The homepage carries about 404 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”.
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Contact us”.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 (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.
2 other companies contacted
Loading the homepage contacts 2 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 bjc.co.th, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Radware
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 bjc.co.th, including 15 speed issues, 8 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.