Website review, no card needed
bonia.com website review
Visit site (opens in a new tab)Reviewed 4 November 202649 issues · 88 checks
This review found 49 issues worth fixing on bonia.com, 17 of them high impact, across 88 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
74C- #81,202 of 115,210 reviewed websitesbeats 26%
- #52,084 of 66,425 online storesbeats 18%
- #49,126 of 60,744 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 187 ms |
| May 23, 2026 | 184 ms |
| May 30, 2026 | 182 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 192 ms |
| Jun 27, 2026 | 195 ms |
| Jul 4, 2026 | 190 ms |
| Jul 11, 2026 | 188 ms |
| Jul 18, 2026 | 188 ms |
| Jul 25, 2026 | 187 ms |
| Aug 1, 2026 | 194 ms |
| Aug 8, 2026 | 203 ms |
| Aug 15, 2026 | 214 ms |
| Aug 22, 2026 | 221 ms |
| Aug 29, 2026 | 230 ms |
| Sep 5, 2026 | 233 ms |
| Sep 12, 2026 | 234 ms |
| Sep 19, 2026 | 239 ms |
| Sep 26, 2026 | 238 ms |
| Oct 3, 2026 | 239 ms |
| Oct 10, 2026 | 235 ms |
| Oct 17, 2026 | 233 ms |
| Oct 24, 2026 | 235 ms |
| Oct 31, 2026 | 230 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
Reduce unused JavaScript
4.0 s · 773 KiBAbout 773 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Use efficient cache lifetimes
2.3 s · 547 KiB13 files are served with short cache lifetimes, so returning visitors download them again (547 KiB).
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Facebook and others), adding 4.7 MB and 1.1 s of main-thread time.
Improve image delivery
1.1 MB21 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 486 ms
486 msGoogle Tag Manager costs a phone 486 ms of main-thread work and 664 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.
Shopify adds 156 ms
156 msShopify costs a phone 156 ms of main-thread work and 3.2 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 CSS
350 ms · 33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 350 ms faster on a phone.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 123 ms
123 msKlaviyo costs a phone 123 ms of main-thread work and 386 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.
1,501 HTML elements
The page has 1,501 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.
Minify JavaScript
20 KiB20 KiB could be saved by minifying JavaScript.
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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 11 ms
11 msYour server sent the HTML in 11 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: 32.3 s
32.3 sYour largest element takes 32.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: 34.8 s
34.8 sThe page becomes fully interactive after 34.8 s. Good is under 3.8 s.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Real-user INP: 228 ms
228 msReal visitors wait 228 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 187 ms to 230 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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: 818 ms
818 msReal visitors wait 818 ms for your server to start answering (75th percentile). Good is under 800 ms.
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 264 ms
264 msScripts block taps and scrolling for 264 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 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 CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.8 MB in 269 requests
7.8 MBYour homepage downloads 7.8 MB in 269 requests on a phone: images 4.6 MB (52), scripts 2.2 MB (92) and other files 698 KiB (103). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
nzd.jpg weighs 801 KiB. On a phone connection a single image that size takes seconds.
5 images far larger than shown
242 KiB5 images are downloaded at several times the size a phone draws them, for example 0ef10e4371e80cf73e6333efa87b2188.jpg at 1,080 px wide, shown at 326 px. Resized copies would save about 242 KiB.
8 images below the first screen load straight away
8 images further down the page (485 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (254 KiB) is 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 2.2 g of CO₂ per visit
2.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.21 g of CO₂e: 264.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
42 images without alt text
42 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail 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.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “BONIA | International Luxury Brand & Leather Expert Est. 1974 – BONIA International”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
169 internal links, 15 external
The homepage links to 169 pages on bonia.com and 15 external pages.
5 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “Shop the BONIA Official Website. Browse the latest collections and discover our online array of bags, shoes, and access…”.
Canonical URL set
The canonical URL is https://bonia.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://bonia.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.
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 (470 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bonia.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
https://bonia.com/collections/all, https://bonia.com/collections/nadia, https://bonia.com/collections/monogram, https://bonia.com/collections/la-luna, https://bonia.com/collections/travel and https://bonia.com/collections/parfum and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://bonia.com/collections/all, https://bonia.com/collections/festive-exclusive, https://bonia.com/collections/new-arrivals, https://bonia.com/collections/nadia, https://bonia.com/collections/monogram and https://bonia.com/collections/la-luna and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 84 found) and read each the way a search engine does.
5 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
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 12 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'value')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
92 of 103 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 21-field form
Your longest form asks for 21 fields (0 required). Every extra field lowers completion.
Only about 248 words
The homepage has only about 248 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now” and “SHOP BY”.
10 calls to action
The homepage has 10 calls to action, for example “Start shopping”, “Shop Now” and “SHOP BY”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
43 other companies contacted
Loading the homepage contacts 43 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 bonia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Size Charts Jotly · Hulk Gdpr Cookie Bar · Helium Customer Fields · Starapps Variant Image · Geoip Country Redirect · Ecomsend · azureedge.net · nfcube.com · Swym Wishlist Plus
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Company
- Employees
- 833
- Founded
- 1974
- Headquarters
- Kuala Lumpur
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on bonia.com, including 23 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.