ptsi.co.id website review

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

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

Reduce initial server response time. Google estimates savings of 1.5 s on a phone.

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

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

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

About 145 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

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

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

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

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

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.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Office & Branch Branch Office Our branch offices are strate…”. Most of its time is resource load delay (5.0 s).

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

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

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

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

1 image 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 175 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 20.6 MB in 121 requests on a phone: images 19.9 MB (69), scripts 520 KiB (35) and stylesheets 102 KiB (9). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 5.85 g of CO₂e: 701.6 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”.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

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.

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

25 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or '}' after property value in JSON at position)”.

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

A phone browser shows 511 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://www.ptsi.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.

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

Large scripts ship without source maps.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 511 words of visible text.

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