Website review, no card needed
hock.id website review
Visit site (opens in a new tab)Reviewed 20 October 202643 issues · 83 checks
This review found 43 issues worth fixing on hock.id, 17 of them high impact, across 83 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
67D- #105,649 of 117,615 reviewed websitesbeats 9%
- #63,312 of 66,923 online storesbeats 4%
- #58,262 of 61,018 Shopify storesbeats 4%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 190 ms |
| May 9, 2026 | 185 ms |
| May 16, 2026 | 182 ms |
| May 23, 2026 | 174 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 163 ms |
| Jun 20, 2026 | 172 ms |
| Jun 27, 2026 | 188 ms |
| Jul 4, 2026 | 189 ms |
| Jul 11, 2026 | 190 ms |
| Jul 18, 2026 | 194 ms |
| Jul 25, 2026 | 184 ms |
| Aug 1, 2026 | 189 ms |
| Aug 8, 2026 | 194 ms |
| Aug 15, 2026 | 198 ms |
| Aug 22, 2026 | 206 ms |
| Aug 29, 2026 | 190 ms |
| Sep 5, 2026 | 210 ms |
| Sep 12, 2026 | 216 ms |
| Sep 19, 2026 | 223 ms |
| Sep 26, 2026 | 256 ms |
| Oct 3, 2026 | 235 ms |
| Oct 10, 2026 | 235 ms |
| Oct 17, 2026 | 242 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
Use efficient cache lifetimes
2.4 s · 4.9 MB121 files are served with short cache lifetimes, so returning visitors download them again (4.9 MB).
Reduce unused JavaScript
5.6 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.6 s faster on a phone.
Mobile performance score: 32
32/100Your mobile performance score is 32 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 1.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 (YouTube, Google Tag Manager and Facebook and others), adding 2.2 MB and 958 ms of main-thread time.
Render-blocking requests
900 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused CSS
450 ms · 254 KiBAbout 254 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
YouTube adds 372 ms
372 msYouTube costs a phone 372 ms of main-thread work and 975 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.
Improve image delivery
468 KiB12 images could be 468 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
350 ms · 52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.
Duplicated JavaScript
150 ms · 17 KiB17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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.
First Contentful Paint: 11.5 s
11.5 sThe first text or image appears after 11.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 22.3 s
22.3 sYour largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ahli Dapur Terpercaya”.
Time to Interactive: 35.7 s
35.7 sThe page becomes fully interactive after 35.7 s. Good is under 3.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.351
0.351The layout shifts by 0.351 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 190 ms to 242 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 814 ms
814 msReal visitors wait 814 ms for your server to start answering (75th percentile). Good is under 800 ms.
22 images without width and height
22 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 297 ms
297 msScripts block taps and scrolling for 297 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 19.6 MB in 714 requests
19.6 MBYour homepage downloads 19.6 MB in 714 requests on a phone: scripts 14.7 MB (228), stylesheets 2.1 MB (125) and other files 1.1 MB (282). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Web_Banner_HOCK_July_2023HI-101_1200x.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).
4 images far larger than shown
70 KiB4 images are downloaded at several times the size a phone draws them, for example dapur-modern_1200x.jpg at 1,200 px wide, shown at 346 px. Resized copies would save about 70 KiB.
About 5.5 g of CO₂ per visit
5.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.55 g of CO₂e: 665.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“<img src="//hock.id/cdn/shop/files/logo-hock-red_…”, “” and “Ahli Dapur Terpercaya”). One clear main headline is easier for people and search engines.
91 internal links, 12 external
The homepage links to 91 pages on hock.id and 12 external pages.
7 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Jual alat dapur modern Hock, harga terbaik, kualitas terjamin dan original | Garansi Service hingga 3 tahun ✅ Pengirima…”.
Title: 62 characters
Your title is a healthy 62 characters: “Toko Alat Dapur Modern Online, Harga Terbaik & Original – Hock”.
Canonical URL set
The canonical URL is https://hock.id/.
Structured data in place
Structured data found: Organization 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://hock.id/sitemap.xml.
AI search readiness
4 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 (806 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://hock.id/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://hock.id/pages/pusat-servis and https://hock.id/blogs, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages share a title
https://hock.id/collections/oven and https://hock.id/pages/produk-oven all use the title “Oven – Hock”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://hock.id/collections/oven, https://hock.id/collections/semua-kompor, https://hock.id/pages/produk-kompor-gas, https://hock.id/collections/kompor-induksi-1-tungku, https://hock.id/pages/produk-kompor-aluminium and https://hock.id/collections/kompor-komersial and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://hock.id/pages/daftar-toko has 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 44 found) and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
16 of 19 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 466 words of copy
The homepage carries about 466 words of visible text.
3 checks passed
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (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.
40 other companies contacted
Loading the homepage contacts 40 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 hock.id, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
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 hock.id, including 21 speed issues, 1 SEO issue 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.