sasa.co.id website review

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

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

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

6 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 59 (desktop: 68). Pages that score under 90 lose visitors before the first paint.

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

Google Tag Manager costs a phone 391 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.

About 303 KiB of JavaScript is downloaded but never used on this page.

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

About 39 KiB of CSS is downloaded but never applied on this page.

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 KiB could be saved by minifying JavaScript.

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.

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

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

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Masak Pakai Sasa, Habis Tanpa Sisa”. Most of its time is element render delay (9.3 s).

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

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

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

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

img-cookingclass2.png weighs 569 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.6 MB in 120 requests on a phone: images 2.3 MB (68), scripts 729 KiB (15) and fonts 490 KiB (13). Under 2 MB keeps phones on slow connections fast.

7 images (2.5 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.

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

1 image is downloaded at several times the size a phone draws it, for example sasa-logo-new.png at 4,500 px wide, shown at 60 px. Resized copies would save about 263 KiB.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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 on the page fail this check, rated minor by axe-core.

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

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 (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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 Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

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

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.

There is no https://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.

https://sasa.co.id/food-service, https://sasa.co.id/faq, https://sasa.co.id/our-products/view/sasa-msg, https://sasa.co.id/our-products/view/tepung-bumbu-serbaguna-original, https://sasa.co.id/our-products/view/santan-bubuk and https://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.

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

https://sasa.co.id/our-products and https://sasa.co.id/food-service have no <h1> headline, so visitors and search engines get no clear main topic.

https://sasa.co.id/our-products and https://sasa.co.id/our-products/view/bumbu-kaldu-rasa-ayam took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.

16 of 68 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 213 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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.

Opening the homepage sets 7 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.