Website review, no card needed

spil.co.id logo

spil.co.id website review

Visit site (opens in a new tab)Reviewed 17 November 202642 issues · 86 checks

This review found 42 issues worth fixing on spil.co.id, 20 of them high impact, across 86 checks. The most urgent: reduce unused CSS. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
8.0 s3.1 sAug 8Nov 144.5 s
Show as table
DateReal-visitor load time (LCP)
Aug 8, 20267.5 s
Aug 15, 20266.7 s
Aug 22, 20265.9 s
Aug 29, 20264.7 s
Sep 5, 20264.5 s
Sep 12, 20264.2 s
Sep 19, 20264.0 s
Sep 26, 20263.9 s
Oct 3, 20263.7 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.7 s
Oct 31, 20264.2 s
Nov 7, 20264.7 s
Nov 14, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
609 ms364 msAug 8Nov 14532 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026392 ms
Aug 15, 2026435 ms
Aug 22, 2026581 ms
Aug 29, 2026505 ms
Sep 5, 2026564 ms
Sep 12, 2026544 ms
Sep 19, 2026517 ms
Sep 26, 2026526 ms
Oct 3, 2026488 ms
Oct 10, 2026483 ms
Oct 17, 2026492 ms
Oct 24, 2026505 ms
Oct 31, 2026517 ms
Nov 7, 2026532 ms
Nov 14, 2026532 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

Full-page screenshot of spil.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. spil.co.id at 2.3 s2.3 s
  2. spil.co.id at 4.6 s4.6 s
  3. spil.co.id at 6.9 s6.9 s
  4. spil.co.id at 9.2 s9.2 s
  5. spil.co.id at 11.5 s11.5 s
  6. spil.co.id at 13.8 s13.8 s
  7. spil.co.id at 16.1 s16.1 s
  8. spil.co.id at 18.3 s18.3 s

Speed

16 to fix29
  • Reduce unused CSS

    4.8 s · 986 KiB

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

  • Render-blocking requests

    5.3 s

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

  • LinkedIn Ads adds 1.4 s

    1.4 s

    LinkedIn Ads costs a phone 1.4 s of main-thread work and 21.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Font display

    3.0 s

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

  • Google CDN adds 1.4 s

    1.4 s

    Google CDN costs a phone 1.4 s of main-thread work and 5.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • protechts.net adds 1.9 s

    1.9 s

    protechts.net costs a phone 1.9 s of main-thread work and 732 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 13.4 s

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

  • Mobile performance score: 29

    29/100

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

  • Use efficient cache lifetimes

    10.2 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (protechts.net, Google CDN and LinkedIn Ads and others), adding 28.4 MB and 5.5 s of main-thread time.

  • Reduce unused JavaScript

    5.6 MB

    About 5.6 MB of JavaScript is downloaded but never used on this page.

  • Document request latency

    650 ms · 73 KiB

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

  • Reduce initial server response time

    632 ms

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

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 460 ms

    460 ms

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

  • Server response: 732 ms

    732 ms

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

  • Improve image delivery

    96 KiB

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

Core Web Vitals

11 to fix33
  • 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.

  • Real-user LCP: 4.5 s

    4.5 s

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

  • Real-user INP: 532 ms

    532 ms

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Speed Index: 42.1 s

    42.1 s

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

  • Time to Interactive: 82.5 s

    82.5 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Largest Contentful Paint: 6.8 s

    6.8 s

    Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Menggerakkan Perekonomian Nasional”. Most of its time is element render delay (6.3 s).

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • Tap response (INP) got 29% slower for real visitors

    +29%

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

  • Real-user TTFB: 970 ms

    970 ms

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

3 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Largest content (LCP) got 35% faster for real visitors

    -35%

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

  • Cumulative Layout Shift: 0.015

    0.015

    The layout barely moves while loading (CLS 0.015, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 35.9 MB in 435 requests

    35.9 MB

    Your homepage downloads 35.9 MB in 435 requests on a phone: media 18.4 MB (5), scripts 10.3 MB (91) and other files 3.4 MB (216). Under 2 MB keeps phones on slow connections fast.

  • About 10.2 g of CO₂ per visit

    10.18 g

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

3 checks passed
  • 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.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 10096
  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (46 elements)

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 2 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10087
  • No canonical URL

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

  • Meta description is long (164 characters)

    Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

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

  • 19 internal links, 13 external

    The homepage links to 19 pages on spil.co.id and 13 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Menggerakkan Perekonomian Nasional”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “PT Salam Pacific Indonesia Lines”.

  • Structured data in place

    Structured data found: Corporation.

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

AI search readiness

100
  • No llms.txt

    There is no https://spil.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.

3 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (281 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://spil.co.id/id and / all use the title “PT Salam Pacific Indonesia Lines”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages share a meta description

    /, https://spil.co.id/id/kontak, https://spil.co.id/id/myspil, https://spil.co.id/id/dampak-hijau, https://spil.co.id/id/tentang-spil and https://spil.co.id/id/layanan and 6 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://spil.co.id/id/kontak has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://spil.co.id/id/kontak, https://spil.co.id/id/berita, https://spil.co.id/id/wawasan and https://spil.co.id/sitemap 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.

  • 1 page slow to respond

    https://spil.co.id/id/dampak-hijau took over 3 s to send its HTML from our server.

  • 12 internal pages checked

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

5 checks passed
  • Linked pages load

    All 12 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 12 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    14 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix63
  • 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.

  • Phone number is not tap-to-call

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

  • No form on the homepage

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

  • 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 326 words of copy

    The homepage carries about 326 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Book Now”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 1 of them by other companies (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.

  • 13 other companies contacted

    Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 spil.co.id, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Analytics
Google Analytics | Google Tag Manager
Hosting
CV Linkmedia Nusantara

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on spil.co.id, including 27 speed issues, 3 SEO 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25