Website review, no card needed
asushit.com website review
Visit site (opens in a new tab)Reviewed 21 November 202646 issues · 89 checks
This review found 46 issues worth fixing on asushit.com, 14 of them high impact, across 89 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
72C- #95,860 of 123,794 reviewed websitesbeats 19%
- #59,149 of 69,673 online storesbeats 12%
- #36 of 63 OpenCart storesbeats 35%
Closest competitors among OpenCart stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 4.0 s |
| Jul 11, 2026 | 3.7 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.1 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 3.9 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.7 s |
| Oct 31, 2026 | 4.0 s |
| Nov 7, 2026 | 4.3 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
How it loaded on a phone
1.1 s
2.1 s
3.2 s
4.3 s
5.3 s
6.4 s
7.4 s
8.5 s
Speed
Use efficient cache lifetimes
35.0 s · 8.2 MB56 files are served with short cache lifetimes, so returning visitors download them again (8.2 MB).
Improve image delivery
28.6 s · 6.5 MB27 images could be 6.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 28.6 s faster on a phone.
Render-blocking requests
3.9 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.
Reduce unused JavaScript
2.1 s · 370 KiBAbout 370 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Reduce unused CSS
1.6 s · 849 KiBAbout 849 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
10,896 HTML elements
The page has 10,896 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Document request latency
950 ms · 1.2 MBThe HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Reduce initial server response time
971 msReduce initial server response time. Google estimates savings of 971 ms on a phone.
Minify JavaScript
690 ms · 119 KiB119 KiB could be saved by minifying JavaScript.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 694 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Jivochat adds 137 ms
137 msJivochat costs a phone 137 ms of main-thread work and 374 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.
Server response: 1.1 s
1.1 sYour server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
4 third-party services on the page
4 third-party services load with your homepage (Jivochat, Google Tag Manager and Google Fonts and others), adding 608 KiB and 211 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 185 ms. During a long task the page ignores taps.
Minify CSS
170 ms · 6 KiB6 KiB could be saved by minifying CSS.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 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.
Core Web Vitals
First Contentful Paint: 12.9 s
12.9 sThe first text or image appears after 12.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 50.8 s
50.8 sYour largest element takes 50.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Clothing, shoes and accessories”.
Speed Index: 23.6 s
23.6 sVisually, the page fills in at 23.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 51.0 s
51.0 sThe page becomes fully interactive after 51.0 s. Good is under 3.8 s.
Largest content (LCP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.2 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 images without width and height
7 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
Total Blocking Time: 130 ms
130 msScripts block the page for only 130 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 10.5 MB in 70 requests
10.5 MBYour homepage downloads 10.5 MB in 70 requests on a phone: images 6.9 MB (29), HTML 1.8 MB (1) and scripts 1.1 MB (19). Under 2 MB keeps phones on slow connections fast.
11 images in older formats
11 images (2.0 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.
4 images far larger than shown
81 KiB4 images are downloaded at several times the size a phone draws them, for example 690738293(2)-1284x214.jpg at 1,284 px wide, shown at 350 px. Resized copies would save about 81 KiB.
5 images below the first screen load straight away
5 images further down the page (288 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.0 g of CO₂ per visit
2.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.97 g of CO₂e: 355.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
26 text elements with low contrast
26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (560 elements)
All page content should be contained by landmarks: 560 elements on the page fail this check, rated moderate by axe-core.
182 form fields without a label
182 form fields have no label, so screen readers announce an empty box and autofill guesses.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), 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).
2 checks passed
Every image has alt text
All 262 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
950 links crawlers can't follow
950 links have no real href, so search engines can't follow them.
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “ASUS-HIT™ online store: official website of the most popular online hypermarket”.
38 links with vague text
38 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Meta description is long (275 characters)
Your meta description is 275 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (DepartmentStore and WebSite) but with 1 problem, for example “WebSite: missing name”.
No XML sitemap
No XML sitemap at https://www.asushit.com/sitemap.xml, so Google discovers your pages only by following links.
455 internal links, 0 external
The homepage links to 455 pages on asushit.com and 0 external pages.
4 checks passed
One H1 headline
Your main headline reads: “ASUSHIT.COM”.
Canonical URL set
The canonical URL is https://www.asushit.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.
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://www.asushit.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 (4,639 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.asushit.com/contact-us has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.asushit.com/about-us and https://www.asushit.com/delivery-information use the same meta description. A description written for each page earns more clicks.
3 pages slow to respond
https://www.asushit.com/contact-us, https://www.asushit.com/frequently-asked-questions and https://www.asushit.com/household-appliances-interior-1028854/large-household-appliances-1029592 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 195 found) and read each the way a search engine does.
6 checks passed
Linked pages load
5 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.
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 5 pages that loaded have a <title>.
Best practices
63 small tap targets
63 of 161 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://code.jivosite.com/css/8a26600/widget.css' from origin 'https://www.asushit.com' ha…”.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 2,372 words of copy
The homepage carries about 2,372 words of visible text.
4 checks passed
114 calls to action
The homepage has 114 calls to action, for example “Contact”, “Buy Now” and “Register”.
2 short forms
2 short forms (0 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Opening hours shown
Your opening hours are on the homepage.
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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
8 other companies contacted
Loading the homepage contacts 8 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 asushit.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Columbus Pe Te Maxnet Telecom, Ltd
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on asushit.com, including 19 speed issues, 6 SEO issues and 5 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.