Website review, no card needed
nabatisnack.co.id website review
Visit site (opens in a new tab)Reviewed 1 November 202641 issues · 77 checks
This review found 41 issues worth fixing on nabatisnack.co.id, 18 of them high impact, across 77 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.8 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 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 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 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 106 ms |
| May 16, 2026 | 107 ms |
| May 23, 2026 | 106 ms |
| May 30, 2026 | 107 ms |
| Jun 6, 2026 | 107 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 107 ms |
| Jun 27, 2026 | 107 ms |
| Jul 4, 2026 | 108 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 109 ms |
| Aug 8, 2026 | 107 ms |
| Aug 15, 2026 | 105 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 106 ms |
| Sep 19, 2026 | 107 ms |
| Sep 26, 2026 | 108 ms |
| Oct 3, 2026 | 108 ms |
| Oct 10, 2026 | 108 ms |
| Oct 17, 2026 | 107 ms |
| Oct 24, 2026 | 107 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
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.0 s
3.5 s
Speed
Use efficient cache lifetimes
18.5 s · 5.9 MB31 files are served with short cache lifetimes, so returning visitors download them again (5.9 MB).
Improve image delivery
16.3 s · 5.3 MB13 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 16.3 s faster on a phone.
Reduce unused JavaScript
3.6 s · 565 KiBAbout 565 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Render-blocking requests
1.5 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Cloudflare CDN and others), adding 1.3 MB and 545 ms of main-thread time.
Google CDN adds 459 ms
459 msGoogle CDN costs a phone 459 ms of main-thread work and 1.1 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.
Reduce unused CSS
160 ms · 30 KiBAbout 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 794 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 30.3 s
30.3 sYour largest element takes 30.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cek Semua Produk Nabati Selengkapnya”.
Time to Interactive: 30.9 s
30.9 sThe page becomes fully interactive after 30.9 s. Good is under 3.8 s.
Speed Index: 9.3 s
9.3 sVisually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 262 ms
262 msScripts block taps and scrolling for 262 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 106 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 101 ms
101 msReal visitors wait 101 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.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 589 ms
589 msReal visitors wait 589 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 7.5 MB in 51 requests
7.5 MBYour homepage downloads 7.5 MB in 51 requests on a phone: images 5.9 MB (18), scripts 1.1 MB (14) and other files 348 KiB (1). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 3.5 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
3.0 MB6 images are downloaded at several times the size a phone draws them, for example ic-ahh.png at 3,336 px wide, shown at 321 px. Resized copies would save about 3.0 MB.
8 images in older formats
8 images (4.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.
3 images below the first screen load straight away
3 images further down the page (113 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.12 g of CO₂e: 254.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 7 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 short (13 characters)
Your title is only 13 characters: “Nabati - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (266 characters)
Your meta description is 266 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token ']', ..."/", ] } "... is not va)”.
No XML sitemap
No XML sitemap at https://www.nabatisnack.co.id/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at nabatisnack.co.id/robots.txt, the first file search crawlers ask for.
Only 2 internal links
The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.
2 checks passed
Canonical URL set
The canonical URL is https://www.nabatisnack.co.id/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.nabatisnack.co.id/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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
1 page points its canonical at the homepage
https://www.nabatisnack.co.id/products.html declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
1 page without an H1
https://www.nabatisnack.co.id/products.html has no <h1> headline, so visitors and search engines get no clear main topic.
1 internal page checked
We fetched 1 page linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 1 page we checked loaded without an error.
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.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
5 of 5 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.
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.
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.
Only about 141 words
The homepage has only about 141 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
1 short form
A short form (2 fields at most) is right on the homepage.
Privacy and tracking
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.
6 other companies contacted
Loading the homepage contacts 6 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 nabatisnack.co.id, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- AWS
Company
- Founded
- 2002
- Headquarters
- Bandung
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on nabatisnack.co.id, including 13 speed issues, 7 SEO issues and 6 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.