Website review, no card needed
baliston.com website review
Visit site (opens in a new tab)Reviewed 17 November 202634 issues · 77 checks
This review found 34 issues worth fixing on baliston.com, 16 of them high impact, across 77 checks. The most urgent: page weight: 45.8 MB in 423 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
66D- #107,978 of 118,069 reviewed websitesbeats 7%
- #64,185 of 67,110 online storesbeats 4%
- #58,974 of 61,191 Shopify storesbeats 3%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 1.8 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 2.1 s |
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
3.0 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
2.2 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Use efficient cache lifetimes
1.6 s · 438 KiB21 files are served with short cache lifetimes, so returning visitors download them again (438 KiB).
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Hotjar and Shopify and others), adding 41.5 MB and 1.4 s of main-thread time.
Shopify adds 172 ms
172 msShopify costs a phone 172 ms of main-thread work and 40.0 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.
Google CDN adds 558 ms
558 msGoogle CDN costs a phone 558 ms of main-thread work and 773 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 565 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 193 KiBAbout 193 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
341 KiB11 images could be 341 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need.
Minify JavaScript
37 KiB37 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
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
Largest Contentful Paint: 19.6 s
19.6 sYour largest element takes 19.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 30.0 s
30.0 sThe page becomes fully interactive after 30.0 s. Good is under 3.8 s.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 45.8 MB in 423 requests
45.8 MBYour homepage downloads 45.8 MB in 423 requests on a phone: media 39.6 MB (3), scripts 2.9 MB (101) and images 1.4 MB (80). Under 2 MB keeps phones on slow connections fast.
11 images in older formats
11 images (673 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.
1 image far larger than shown
37 KiB1 image is downloaded at several times the size a phone draws it, for example optimized_up-hp-step-counter-step-aside-final-img-final_1024 at 948 px wide, shown at 264 px. Resized copies would save about 37 KiB.
About 13.0 g of CO₂ per visit
13.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 13.00 g of CO₂e: 1559.4 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
42 images without alt text
42 images have no alt text, which hurts accessibility and image search.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (19 characters)
Your title is only 19 characters: “BAL Inc (Baliston®)”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (47 characters)
Your meta description is only 47 characters: “Baliston® INTRODUCING A NEW FOOTWEAR EXPERIENCE”. 70 to 160 characters is enough to sell the click.
44 internal links, 20 external
The homepage links to 44 pages on baliston.com and 20 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://baliston.com/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage, ImageObject, Organization and WebPage.
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://baliston.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://baliston.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.
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 sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (855 words), so crawlers that don't run JavaScript still read it.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://baliston.com/products/bundle-full-black, whose canonical is https://baliston.com/products/baliston%c2%ae-by-starck-smart-shoes-full-black. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
6 checks passed
Linked pages load
1 page of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 1 page that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97132364&Ver=2&mid=6d1f568d-3959-42d6-af30-186d3a428685&bo=1&sid=483c96e0e22a11f19196c10d3e8217e9&vid=483ccbd0e22a11f1949bb346850037ab&vids=1&msclkid=N&pi=918639831&lg.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
32 of 32 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 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 449 words of copy
The homepage carries about 449 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 3 trust badges and “over 120,000 patients”.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Hotjar and Amplitude.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amplitude, FullStory, Google Analytics, Google Tag Manager and Hotjar and 3 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
45 other companies contacted
Loading the homepage contacts 45 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 baliston.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Helium Customer Fields · Weglot Translate Your Store · Klaviyo Email Marketing Sms · Yoast Seo · Rivyo Product Review · rechargecdn.com · unpkg.com · shareasale.com · searchserverapi.com · adroll.com · useamp.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
- The footer still says © 2023.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar | Amplitude | FullStory
- Hosting
- Shopify
Company
- Headquarters
- Sunnyvale
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on baliston.com, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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.