Website review, no card needed
bafleh.com website review
Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 84 checks
This review found 45 issues worth fixing on bafleh.com, 11 of them high impact, across 84 checks. The most urgent: page weight: 27.5 MB in 57 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
78C- #59,594 of 117,924 reviewed websitesbeats 44%
- #39,179 of 67,048 online storesbeats 36%
- #865 of 2,705 WooCommerce storesbeats 62%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 125 ms |
| May 23, 2026 | 126 ms |
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 123 ms |
| Jun 20, 2026 | 123 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 125 ms |
| Jul 11, 2026 | 125 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 108 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 115 ms |
| Sep 12, 2026 | 120 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 105 ms |
| Oct 10, 2026 | 101 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 114 ms |
| Oct 31, 2026 | 123 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.8 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Use efficient cache lifetimes
900 ms · 26.7 MB35 files are served with short cache lifetimes, so returning visitors download them again (26.7 MB).
Improve image delivery
22.9 MB7 images could be 22.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 82
82/100Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 675 KiB and 733 ms of main-thread time.
Google Tag Manager adds 437 ms
437 msGoogle Tag Manager costs a phone 437 ms of main-thread work and 398 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.
Reduce unused JavaScript
150 ms · 284 KiBAbout 284 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Facebook adds 293 ms
293 msFacebook costs a phone 293 ms of main-thread work and 228 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 284 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 790 ms of it running JavaScript. That is comfortably low.
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.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 82.7 s
82.7 sThe page becomes fully interactive after 82.7 s. Good is under 3.8 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 499 ms
499 msScripts block taps and scrolling for 499 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 125 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 127 ms
127 msReal visitors wait 127 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.
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “GOLDEN GRANDEUR ECHOES OF ETERNITY”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 27.5 MB in 57 requests
27.5 MBYour homepage downloads 27.5 MB in 57 requests on a phone: images 26.5 MB (12), scripts 735 KiB (20) and other files 62 KiB (13). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
46 KiB1 image is downloaded at several times the size a phone draws it, for example BAFLEH-Logo-Black-2048x610-1.png at 2,048 px wide, shown at 244 px. Resized copies would save about 46 KiB.
2 images in older formats
2 images (82 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 7.8 g of CO₂ per visit
7.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.79 g of CO₂e: 934.8 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
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another 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.
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.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 5 failed. 2 mores 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (16 characters)
Your title is only 16 characters: “Bafleh Jewellery”. 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.
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.
18 links crawlers can't follow
18 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
24 internal links, 1 external
The homepage links to 24 pages on bafleh.com and 1 external page.
3 checks passed
Canonical URL set
The canonical URL is https://bafleh.com/.
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://bafleh.com/wp-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://bafleh.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 (282 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://bafleh.com/retails and https://bafleh.com/retail all use the title “Showrooms – Bafleh Jewellery”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://bafleh.com/whole-sale, https://bafleh.com/laboratory, https://bafleh.com/about-us, https://bafleh.com/retails, https://bafleh.com/hong-kong and https://bafleh.com/bafleh-bullion and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://bafleh.com/retail, whose canonical is https://bafleh.com/retails. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://bafleh.com/whole-sale, https://bafleh.com/laboratory, https://bafleh.com/retails, https://bafleh.com/bafleh-bullion, https://bafleh.com/shop and https://bafleh.com/retail and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bafleh.com/wp-content/uploads/2026/06/Footer-Logo-scaled-e1781520242183.png.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
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
11 of 12 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.
Only about 203 words
The homepage has only about 203 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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: “CONTACT US” and “E-SHOP”.
9 calls to action
The homepage has 9 calls to action, for example “Contact Us”, “E Shop” and “Return to shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and Hotjar.
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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
10 other companies contacted
Loading the homepage contacts 10 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 bafleh.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
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Hotjar
- Hosting
- GoDaddy
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on bafleh.com, including 19 speed issues, 6 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.