quantum.net.id website review

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

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

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

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

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

The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 558 ms on a phone.

9 images could be 284 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your server takes 658 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

5 KiB could be saved by minifying CSS.

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

1 third-party service load with your homepage (Google Fonts), adding 11 KiB and 0 ms of main-thread time.

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

Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (11.6 s).

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.2 MB in 33 requests on a phone: stylesheets 1.0 MB (7), images 655 KiB (13) and scripts 427 KiB (10). Under 2 MB keeps phones on slow connections fast.

7 images (512 KiB) 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.

1 image is downloaded at several times the size a phone draws it, for example infrastructuresolution_compressed.jpg at 1,249 px wide, shown at 320 px. Resized copies would save about 38 KiB.

5 images further down the page (313 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

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

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

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

The homepage links to 6 pages on quantum.net.id and 5 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.

https://www.quantum.net.id/about-us has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.quantum.net.id/about-us took over 3 s to send its HTML from our server.

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

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Opening the homepage sets 3 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.