Website review, no card needed

ipi.co.id logo

ipi.co.id website review

Visit site (opens in a new tab)Reviewed 3 November 202635 issues · 79 checks

This review found 35 issues worth fixing on ipi.co.id, 15 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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

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

How it loaded on a phone

  1. ipi.co.id at 2.0 s2.0 s
  2. ipi.co.id at 4.0 s4.0 s
  3. ipi.co.id at 6.0 s6.0 s
  4. ipi.co.id at 8.0 s8.0 s
  5. ipi.co.id at 9.9 s9.9 s
  6. ipi.co.id at 11.9 s11.9 s
  7. ipi.co.id at 13.9 s13.9 s
  8. ipi.co.id at 15.9 s15.9 s

Speed

10 to fix54
  • Use efficient cache lifetimes

    9.7 s · 5.7 MB

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

  • Render-blocking requests

    11.2 s

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

  • Reduce unused CSS

    6.7 s · 1.2 MB

    About 1.2 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.7 s faster on a phone.

  • Font display

    3.0 s

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

  • Reduce unused JavaScript

    1.1 s · 924 KiB

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

  • Main-thread work: 4.1 s

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

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

  • Document request latency

    550 ms · 116 KiB

    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

    561 ms

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

  • Server response: 661 ms

    661 ms

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

  • Minify CSS

    150 ms · 47 KiB

    47 KiB could be saved by minifying CSS.

  • 3 third-party services on the page

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

  • 5 long tasks on the main thread

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

  • Minify JavaScript

    82 KiB

    82 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    59 KiB

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

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Core Web Vitals

5 to fix65
  • First Contentful Paint: 11.7 s

    11.7 s

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

  • Largest Contentful Paint: 18.0 s

    18.0 s

    Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To provide the best Packaging Solutions for Indonesia with …”. Most of its time is element render delay (7.7 s).

  • Speed Index: 32.0 s

    32.0 s

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

  • Time to Interactive: 32.7 s

    32.7 s

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

  • 4 images without width and height

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Cumulative Layout Shift: 0.067

    0.067

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

  • Total Blocking Time: 69 ms

    69 ms

    Scripts block the page for only 69 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix60
  • Page weight: 6.3 MB in 120 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 120 requests on a phone: images 2.6 MB (27), scripts 1.8 MB (36) and stylesheets 1.3 MB (44). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (1.0 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.

  • 3 images below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.77 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9490
  • 3 text elements with low contrast

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

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    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)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 checks passed
  • 29 automated accessibility rules passed

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

SEO

4 to fixGoogle 9273
  • No meta description

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

  • No H1 headline

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

  • No structured data

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

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 40 internal links, 1 external

    The homepage links to 40 pages on ipi.co.id and 1 external page.

4 checks passed
  • Title: 55 characters

    Your title is a healthy 55 characters: “PT. Industri Pembungkus Internasional – Packaging Boxes”.

  • Canonical URL set

    The canonical URL is https://ipi.co.id/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://ipi.co.id/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 2 pages share a title

    / and https://ipi.co.id/id all use the title “PT. Industri Pembungkus Internasional – Packaging Boxes”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://ipi.co.id/2023/08/11/about-us, https://ipi.co.id/2023/08/24/awards, https://ipi.co.id/2023/08/11/corporate-social-responsibility, https://ipi.co.id/2023/08/24/policy, https://ipi.co.id/2024/01/04/certification and https://ipi.co.id/2023/08/24/products and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://ipi.co.id/contact-us and https://ipi.co.id/id have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://ipi.co.id/2023/08/11/about-us, https://ipi.co.id/2023/08/11/corporate-social-responsibility, https://ipi.co.id/2023/08/24/policy and https://ipi.co.id/2023/08/24/corrugated-box took over 3 s to send their 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.

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

  • 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

1 to fixGoogle 9293
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 (Bad Request)”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 163 words

    The homepage has only about 163 words of visible text; thin pages give Google and first-time buyers little to go on.

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 ipi.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

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on ipi.co.id, including 15 speed issues, 4 SEO issues and 3 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