Website review, no card needed

sasainti.co.id logo

sasainti.co.id website review

Visit site (opens in a new tab)Reviewed 5 November 202652 issues · 90 checks

This review found 52 issues worth fixing on sasainti.co.id, 21 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.1 s4.5 sMay 16Oct 315.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.1 s
May 23, 20265.2 s
May 30, 20265.7 s
Jun 6, 20265.9 s
Jun 13, 20265.9 s
Jun 20, 20265.9 s
Jun 27, 20265.4 s
Jul 4, 20265.3 s
Jul 11, 20265.2 s
Jul 18, 20265.3 s
Jul 25, 20265.3 s
Aug 1, 20265.5 s
Aug 8, 20265.6 s
Aug 15, 20265.6 s
Aug 22, 20265.5 s
Aug 29, 20265.2 s
Sep 5, 20264.9 s
Sep 12, 20264.8 s
Sep 19, 20264.7 s
Sep 26, 20264.7 s
Oct 3, 20264.7 s
Oct 10, 20264.7 s
Oct 17, 20264.8 s
Oct 24, 20264.9 s
Oct 31, 20265.1 s
Real-visitor tap response (INP)75th percentile, phones
183 ms112 msMay 16Oct 31175 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026125 ms
May 23, 2026125 ms
May 30, 2026124 ms
Jun 6, 2026124 ms
Jun 13, 2026124 ms
Jun 20, 2026125 ms
Jun 27, 2026125 ms
Jul 4, 2026126 ms
Jul 11, 2026127 ms
Jul 18, 2026126 ms
Jul 25, 2026123 ms
Aug 1, 2026120 ms
Aug 8, 2026120 ms
Aug 15, 2026125 ms
Aug 22, 2026136 ms
Aug 29, 2026145 ms
Sep 5, 2026152 ms
Sep 12, 2026157 ms
Sep 19, 2026157 ms
Sep 26, 2026158 ms
Oct 3, 2026161 ms
Oct 10, 2026165 ms
Oct 17, 2026171 ms
Oct 24, 2026174 ms
Oct 31, 2026175 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

Full-page screenshot of sasainti.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sasainti.co.id at 1.3 s1.3 s
  2. sasainti.co.id at 2.6 s2.6 s
  3. sasainti.co.id at 3.9 s3.9 s
  4. sasainti.co.id at 5.2 s5.2 s
  5. sasainti.co.id at 6.5 s6.5 s
  6. sasainti.co.id at 7.8 s7.8 s
  7. sasainti.co.id at 9.1 s9.1 s
  8. sasainti.co.id at 10.4 s10.4 s

Speed

8 to fix38
  • Use efficient cache lifetimes

    5.4 s · 29.5 MB

    83 files are served with short cache lifetimes, so returning visitors download them again (29.5 MB).

  • Improve image delivery

    1.9 s · 27.1 MB

    34 images could be 27.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Render-blocking requests

    2.1 s

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.

  • Reduce unused JavaScript

    1.6 s · 303 KiB

    About 303 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Font display

    1.5 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.5 s).

  • Mobile performance score: 38

    38/100

    Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Crazy Egg and others), adding 942 KiB and 692 ms of main-thread time.

  • Google Tag Manager adds 405 ms

    405 ms

    Google Tag Manager costs a phone 405 ms of main-thread work and 466 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.

  • Reduce unused CSS

    150 ms · 32 KiB

    About 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 715 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • 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.

  • Largest Contentful Paint: 21.5 s

    21.5 s

    Your largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Aneka Resep Nasi Goreng”.

  • Time to Interactive: 22.2 s

    22.2 s

    The page becomes fully interactive after 22.2 s. Good is under 3.8 s.

  • Speed Index: 10.3 s

    10.3 s

    Visually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.

  • Cumulative Layout Shift: 0.395

    0.395

    The layout shifts by 0.395 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 2.8 s

    2.8 s

    Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 283 ms

    283 ms

    Real visitors wait 283 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 40% slower for real visitors

    +40%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 125 ms to 175 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.4 s

    2.4 s

    Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 2.4 s

    2.4 s

    The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 290 ms

    290 ms

    Scripts block taps and scrolling for 290 ms in total while the page loads. Good is under 200 ms.

  • 14 images without width and height

    14 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.1 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 585 ms

    585 ms

    Real visitors wait 585 ms for your server to start answering (75th percentile). Good is under 800 ms.

Images and page weight

5 to fix18
  • Page weight: 31.8 MB in 123 requests

    31.8 MB

    Your homepage downloads 31.8 MB in 123 requests on a phone: images 30.6 MB (68), scripts 724 KiB (15) and fonts 490 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 22.4 MB together. On a phone connection a single image that size takes seconds.

  • 21 images far larger than shown

    20.9 MB

    21 images are downloaded at several times the size a phone draws them, for example 01M5EVHK0JAPFXBMH2WWTS7Y0J.jpg at 5,430 px wide, shown at 220 px. Resized copies would save about 20.9 MB.

  • 23 images in older formats

    23 images (26.4 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.

  • 20 images below the first screen load straight away

    20 images further down the page (23.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 9.0 g of CO₂ per visit

    9.02 g

    By the Sustainable Web Design model, a visit to your homepage emits about 9.02 g of CO₂e: 1082.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

11 to fixGoogle 7083
  • 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.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 24 text elements with low contrast

    24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • <object> elements must have alternative text (1 element)

    <object> elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 15 images without alt text

    15 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (15 elements)

    All page content should be contained by landmarks: 15 elements on the page fail 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.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 39 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: 39 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8579
  • Title is short (11 characters)

    Your title is only 11 characters: “Home | Sasa”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Masak Pakai Sasa, Habis Tanpa Sisa” and “Temukan inspirasi resep baru yang siap bikin mome…”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 93 internal links, 10 external

    The homepage links to 93 pages on sasainti.co.id and 10 external pages.

4 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Produsen penyedap rasa MSG (monosodium glutamat) dan aneka bumbu makanan merk Sasa yang dipercaya masyarakat Indonesia …”.

  • Canonical URL set

    The canonical URL is https://www.sasa.co.id/.

  • 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://www.sasa.co.id/sitemap.xml.

AI search readiness

1 to fix88
  • 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.sasa.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.

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 (338 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 8 pages share a title

    https://www.sasa.co.id/food-service, https://www.sasa.co.id/faq, https://www.sasa.co.id/our-products/view/sasa-msg, https://www.sasa.co.id/our-products/view/tepung-bumbu-serbaguna-original, https://www.sasa.co.id/our-products/view/santan-bubuk and https://www.sasa.co.id/our-products/view/saus-sambal-asli and 2 others all use the title “Sasa”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://www.sasa.co.id/food-service, https://www.sasa.co.id/faq, https://www.sasa.co.id/our-products/view/sasa-msg, https://www.sasa.co.id/our-products/view/tepung-bumbu-serbaguna-original, https://www.sasa.co.id/our-products/view/santan-bubuk and https://www.sasa.co.id/our-products/view/saus-sambal-asli and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.sasa.co.id/our-products and https://www.sasa.co.id/food-service have 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 51 found) and read each the way a search engine does.

4 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.

  • 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

2 to fixGoogle 8891
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    48 of 57 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • Only about 213 words

    The homepage has only about 213 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.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Subscribe Mengirim...”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before 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.

  • 7 cookies set on arrival

    7

    Opening 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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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 sasainti.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

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Akamai Cloud

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on sasainti.co.id, including 20 speed issues, 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25