larissa.co.id website review

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

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

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

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

About 469 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.2 s faster on a phone.

Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

97 KiB could be saved by minifying CSS.

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

A phone's processor spends 3.9 s on main-thread work while loading, 967 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,723 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 third-party services load with your homepage (Facebook, TikTok and Google Tag Manager and others), adding 1,012 KiB and 365 ms of main-thread time.

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

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

23 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 76.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slider Larissa Aesthetic Center”.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 20.0 MB in 170 requests on a phone: images 17.3 MB (56), scripts 1.3 MB (57) and fonts 771 KiB (11). Under 2 MB keeps phones on slow connections fast.

14 images weigh 14.8 MB together. On a phone connection a single image that size takes seconds.

20 images are downloaded at several times the size a phone draws them, for example 20261015131606-bio-pigmentation-light-therapy.png at 1,254 px wide, shown at 264 px. Resized copies would save about 8.6 MB.

22 images (15.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.

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

1792564459-mobile-54zTv.png 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).

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

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

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

ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 63 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 79 characters, so Google will cut it off around 60: “Klinik Kecantikan Natural & Perawatan Kulit Estetika - Larissa Aesthetic Center”.

No XML sitemap at https://larissa.co.id/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 102 pages on larissa.co.id and 58 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://larissa.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://larissa.co.id/faq, https://larissa.co.id/karir and https://larissa.co.id/produk/osn-after-acne-regeneration-booster-serum use the same meta description. A description written for each page earns more clicks.

https://larissa.co.id/kontak, https://larissa.co.id/karir, https://larissa.co.id/produk/osn-acne-serum and https://larissa.co.id/produk/osn-after-acne-regeneration-booster-serum have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

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: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

The homepage carries about 616 words of visible text.

Before a visitor clicks anything, the page loads 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.

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.