Website review, no card needed
bhinneka.com website review
Visit site (opens in a new tab)Reviewed 18 November 202641 issues · 79 checks
This review found 41 issues worth fixing on bhinneka.com, 14 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 151 ms |
| Jul 11, 2026 | 160 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 197 ms |
| Aug 29, 2026 | 211 ms |
| Sep 5, 2026 | 214 ms |
| Sep 12, 2026 | 208 ms |
| Sep 19, 2026 | 193 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 148 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 146 ms |
| Nov 7, 2026 | 148 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
Render-blocking requests
1.6 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.
Font display
1.3 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.3 s).
Improve image delivery
650 ms · 882 KiB31 images could be 882 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (bmdstatic.com, Google Tag Manager and Cloudflare and others), adding 2.5 MB and 687 ms of main-thread time.
Reduce unused CSS
750 ms · 153 KiBAbout 153 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
bmdstatic.com adds 368 ms
368 msbmdstatic.com costs a phone 368 ms of main-thread work and 2.1 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.
Reduce unused JavaScript
512 KiBAbout 512 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 301 ms
301 msGoogle Tag Manager costs a phone 301 ms of main-thread work and 321 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 297 ms. During a long task the page ignores taps.
2,361 HTML elements
The page has 2,361 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
127 KiB8 files are served with short cache lifetimes, so returning visitors download them again (127 KiB).
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
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.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 666 ms of it running JavaScript. That is comfortably low.
Server response: 47 ms
47 msYour server sent the HTML in 47 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.
Time to Interactive: 13.1 s
13.1 sThe page becomes fully interactive after 13.1 s. Good is under 3.8 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “wasabi”.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
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.
Cumulative Layout Shift: 0.233
0.233The layout shifts by 0.233 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 348 ms
348 msScripts block taps and scrolling for 348 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
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 162 ms to 148 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 184 ms
184 msReal visitors wait 184 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 758 ms
758 msReal visitors wait 758 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 2.5 MB in 70 requests
2.5 MBYour homepage downloads 2.5 MB in 70 requests on a phone: images 1.1 MB (43), scripts 983 KiB (7) and fonts 206 KiB (5). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
103 KiB3 images are downloaded at several times the size a phone draws them, for example EPSON-EcoTank-L5290-fc9b1c6242fd44ddb48ce5f8696f64ba_medium. at 500 px wide, shown at 96 px. Resized copies would save about 103 KiB.
9 images in older formats
9 images (390 KiB) 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.
About 0.7 g of CO₂ per visit
0.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.71 g of CO₂e: 85.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
[role="img"] and [role="image"] elements must have alternative text (120 elements)
[role="img"] and [role="image"] elements must have alternative text: 120 elements on the page fail this check, rated serious by axe-core.
Certain ARIA roles must contain particular children (4 elements)
Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
ARIA input fields must have an accessible name (4 elements)
ARIA input fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
52 images without alt text
52 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (6 elements)
Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 10 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.
No XML sitemap
No XML sitemap at https://bhinneka.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at bhinneka.com/robots.txt, the first file search crawlers ask for.
232 internal links, 14 external
The homepage links to 232 pages on bhinneka.com and 14 external pages.
4 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Bhinneka adalah toko online B2B yang menyediakan produk IT, MRO, Peralatan Kantor, dan Jasa untuk kebutuhan korporasi, …”.
Title: 59 characters
Your title is a healthy 59 characters: “Bhinneka: Toko Online B2B Terlengkap untuk Kebutuhan Bisnis”.
Canonical URL set
The canonical URL is https://www.bhinneka.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (2,251 words), so crawlers that don't run JavaScript still read it.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
66 of 73 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.
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.
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 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,394 words of copy
The homepage carries about 1,394 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
2 short forms
2 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Umami and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
7 other companies contacted
Loading the homepage contacts 7 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 bhinneka.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Odoo
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Headquarters
- Jakarta
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on bhinneka.com, including 20 speed issues, 4 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.