Website review, no card needed
ha-ko.com website review
Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 82 checks
This review found 43 issues worth fixing on ha-ko.com, 22 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
60D- #114,473 of 117,615 reviewed websitesbeats 2%
- #66,295 of 66,923 online storesbeats 1%
- #2,646 of 2,700 WooCommerce storesbeats 1%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
15.1 s · 4.0 MB114 files are served with short cache lifetimes, so returning visitors download them again (4.0 MB).
Improve image delivery
7.5 s · 1.6 MB6 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.5 s faster on a phone.
Render-blocking requests
5.1 s60 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.1 s.
Reduce unused CSS
2.3 s · 448 KiBAbout 448 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
450 ms · 102 KiBAbout 102 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Minify CSS
300 ms · 59 KiB59 KiB could be saved by minifying CSS.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 333 ms. During a long task the page ignores taps.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 678 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 118 KiB and 7 ms of main-thread time.
Minify JavaScript
12 KiB12 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.
1 checks passed
Server response: 24 ms
24 msYour server sent the HTML in 24 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.1 s
17.1 sYour largest element takes 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 13.1 s
13.1 sVisually, the page fills in at 13.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.1 s
17.1 sThe page becomes fully interactive after 17.1 s. Good is under 3.8 s.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.41
0.41The layout shifts by 0.41 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 420 ms
420 msScripts block taps and scrolling for 420 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 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.
Images and page weight
Page weight: 4.2 MB in 127 requests
4.2 MBYour homepage downloads 4.2 MB in 127 requests on a phone: images 2.7 MB (14), stylesheets 593 KiB (55) and scripts 487 KiB (46). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
hklogo20.jpg weighs 1.2 MB. On a phone connection a single image that size takes seconds.
5 images in older formats
5 images (1.6 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.
An image on the first screen is lazy-loaded
1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.2 g of CO₂ per visit
1.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.18 g of CO₂e: 141.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Certain ARIA roles must be contained by particular parents (1 element)
Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
29 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (1 element).
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
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
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 10 failed. 1 more 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.
Title is long (123 characters)
Your title is 123 characters, so Google will cut it off around 60: “Ha-Ko Group India | cricketRollers | Gravity ball machines| supersopper, cricket ground r…”.
32 links with vague text
32 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Meta description is long (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
247 internal links, 9 external
The homepage links to 247 pages on ha-ko.com and 9 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://ha-ko.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://ha-ko.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://ha-ko.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (610 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://ha-ko.com/product-category/ground-roller-riding-lawn-mower/ride-on-pitch-rollers has no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://ha-ko.com/product/manual-hand-rollers took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 72 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
30 small tap targets
30 of 108 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 153 words
The homepage has only about 153 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Download” and “Contact”.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
7 cookies set on arrival
7Opening the homepage sets 7 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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 ha-ko.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
- Hosting
- Oracle Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on ha-ko.com, including 16 speed issues, 4 SEO issues and 4 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.