avrist.com website review

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

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

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

8 images could be 5.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

4 files are served with short cache lifetimes, so returning visitors download them again (135 KiB).

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

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

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

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

3 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics), adding 644 KiB and 405 ms of main-thread time.

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

About 13 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.

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

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.

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

Your largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “loop-image”.

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

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

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

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

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

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

Your homepage downloads 7.6 MB in 80 requests on a phone: images 6.6 MB (33), scripts 890 KiB (26) and fonts 63 KiB (3). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example a18f9817-705f-48cc-9e57-3cacf9941ffb-zzzzzzzzaaaaa.png at 1,440 px wide, shown at 390 px. Resized copies would save about 969 KiB.

5 images (2.9 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.

a18f9817-705f-48cc-9e57-3cacf9941ffb-zzzzzzzzaaaaa.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 2.15 g of CO₂e: 258.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

Your title is only 16 characters: “Avrist Assurance”. 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.

Your meta description is only 16 characters: “Avrist Assurance”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://avrist.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 21 pages on avrist.com and 41 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 /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.

/, /tanya-avrista, /pencarian, /produk/individu, /produk/korporasi and /klaim-layanan/klaim and 3 others all use the title “Avrist Assurance”. Search engines can't tell which page to show for a search, so each competes with the others.

/tanya-avrista, /pencarian, /produk/individu, /produk/korporasi, /klaim-layanan/klaim and /hubungi-kami and 2 others use the same meta description. A description written for each page earns more clicks.

/pencarian, /produk/individu, /produk/korporasi, /klaim-layanan/klaim, /hubungi-kami and /syarat-penggunaan and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

/tanya-avrista, /pencarian, /produk/individu, /produk/korporasi, /klaim-layanan/klaim and /hubungi-kami and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

24 of 47 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 “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

Requests the geolocation permission on page load.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

avrist.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

avrist.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

There is no form on the homepage, so every lead has to click through to another page first.

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 416 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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 4 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.