Website review, no card needed
suryasarana.com website review
Visit site (opens in a new tab)Reviewed 18 October 202615 issues · 73 checks
This review found 15 issues worth fixing on suryasarana.com, 3 of them high impact, across 73 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
95AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.5 s |
| May 2, 2026 | 2.5 s |
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 154 ms |
| May 2, 2026 | 156 ms |
| May 9, 2026 | 145 ms |
| May 16, 2026 | 181 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 173 ms |
| Jun 6, 2026 | 186 ms |
| Jun 13, 2026 | 159 ms |
| Jun 20, 2026 | 164 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 149 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 140 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 122 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 147 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 166 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 169 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 297 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused CSS
300 ms · 153 KiBAbout 153 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.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Improve image delivery
108 KiB3 images could be 108 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
3 checks passed
Mobile performance score: 93
93/100Your mobile performance score is 93 (desktop: 97). That is in Google's “good” band (90 and up).
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 22 ms of it running JavaScript. That is comfortably low.
Server response: 271 ms
271 msYour server sent the HTML in 271 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Tap response (INP) got 48% slower for real visitors
+48%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 154 ms to 297 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.5 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 895 ms
895 msReal visitors wait 895 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 2.8 s
2.8 sYour largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (1.4 s).
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 182 ms
182 msReal visitors wait 182 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 2.8 s
2.8 sThe page is fully interactive after 2.8 s.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
38 KiB1 image is downloaded at several times the size a phone draws it, for example img-20260911173920.webp at 1,854 px wide, shown at 390 px. Resized copies would save about 38 KiB.
About 0.1 g of CO₂ per visit
0.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.12 g of CO₂e: 14.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 440 KiB in 19 requests
440 KiBYour homepage downloads 440 KiB in 19 requests on a phone: images 220 KiB (13), fonts 145 KiB (3) and HTML 53 KiB (1). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 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 (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
112 internal links, 30 external
The homepage links to 112 pages on suryasarana.com and 30 external pages.
8 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “PT Surya Sarana Dinamika menyediakan solusi Automation, Robotics, IoT, dan AI untuk transformasi Industri 4.0 didukung …”.
One H1 headline
Your main headline reads: “MASIH MEMBAYAR LEBIH UNTUK PROSES YANG EFISIEN?”.
Title: 31 characters
Your title is a healthy 31 characters: “Home | PT Surya Sarana Dinamika”.
Canonical URL set
The canonical URL is https://suryasarana.com/.
Structured data in place
Structured data found: Corporation, LocalBusiness and Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://suryasarana.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,833 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://suryasarana.com/llms.txt (22 KiB, 201 links), a plain-text guide to the site for AI tools.
Other pages
9 pages slow to respond
https://suryasarana.com/visi-misi, https://suryasarana.com/lokasi, https://suryasarana.com/surat-keagenan, https://suryasarana.com/podcast, https://suryasarana.com/e-katalog and https://suryasarana.com/kategori-produk and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
27 of 27 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,381 words of copy
The homepage carries about 1,381 words of visible text.
6 checks passed
1 call to action
The homepage has 1 call to action, for example “Download e-Katalog Kami”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 5 phone links and 5 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
No consent tool detected
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at suryasarana.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 15 issues on suryasarana.com, including 8 speed issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.