Website review, no card needed

printmate.co.id logo

printmate.co.id website review

Visit site (opens in a new tab)Reviewed 3 November 202634 issues · 84 checks

This review found 34 issues worth fixing on printmate.co.id, 14 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
5.6 s3.7 sMay 16Oct 313.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.0 s
May 23, 20265.4 s
May 30, 20265.2 s
Jun 6, 20265.2 s
Jun 13, 20265.3 s
Jul 11, 20264.9 s
Jul 18, 20264.9 s
Jul 25, 20264.8 s
Aug 1, 20264.8 s
Aug 8, 20264.5 s
Aug 15, 20264.5 s
Aug 22, 20264.5 s
Aug 29, 20264.3 s
Sep 5, 20264.5 s
Sep 12, 20263.9 s
Sep 19, 20264.3 s
Sep 26, 20264.7 s
Oct 3, 20265.0 s
Oct 31, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
165 ms95 msMay 16Sep 26103 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026157 ms
May 30, 2026131 ms
Jun 13, 2026125 ms
Jul 18, 2026120 ms
Jul 25, 2026122 ms
Aug 1, 2026128 ms
Aug 8, 2026128 ms
Aug 15, 2026136 ms
Aug 22, 2026130 ms
Sep 26, 2026103 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 printmate.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. printmate.co.id at 2.2 s2.2 s
  2. printmate.co.id at 4.5 s4.5 s
  3. printmate.co.id at 6.7 s6.7 s
  4. printmate.co.id at 8.9 s8.9 s
  5. printmate.co.id at 11.2 s11.2 s
  6. printmate.co.id at 13.4 s13.4 s
  7. printmate.co.id at 15.6 s15.6 s
  8. printmate.co.id at 17.9 s17.9 s

Speed

7 to fix60
  • Improve image delivery

    3.0 s · 9.2 MB

    16 images could be 9.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

  • Render-blocking requests

    4.3 s

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

  • Use efficient cache lifetimes

    1.9 s · 1.4 MB

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

  • Font display

    1.8 s

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

  • Mobile performance score: 60

    60/100

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

  • Reduce unused CSS

    600 ms · 131 KiB

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

  • Reduce unused JavaScript

    450 ms · 99 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 54 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    11 KiB

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

  • 1 third-party service on the page

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

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 490 ms of it running JavaScript. That is comfortably low.

  • Server response: 436 ms

    436 ms

    Your server sent the HTML in 436 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • 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 FCP: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 13.7 s

    13.7 s

    Your largest element takes 13.7 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 (8.7 s).

  • Speed Index: 20.6 s

    20.6 s

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

  • Time to Interactive: 13.9 s

    13.9 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 26 images without width and height

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

5 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 19% faster for real visitors

    -19%

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

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

    -15%

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

  • Cumulative Layout Shift: 0.067

    0.067

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

  • Total Blocking Time: 4 ms

    4 ms

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

Images and page weight

3 to fix53
  • Page weight: 10.9 MB in 147 requests

    10.9 MB

    Your homepage downloads 10.9 MB in 147 requests on a phone: images 10.0 MB (55), scripts 388 KiB (46) and stylesheets 222 KiB (41). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Screen_Shot_2026-10-28_at_10.05.55-removebg-preview-300x278. is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 13 images in older formats

    13 images (752 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.

  • About 3.1 g of CO₂ per visit

    3.08 g

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

6 to fixGoogle 8991
  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

  • 2 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 55 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is short (26 characters)

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

  • 5 H1 headlines

    There are 5 <h1> headlines (“Budiman”, “Kelana” and “Odette”). One clear main headline is easier for people and search engines.

  • 9 links with vague text

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

  • 93 internal links, 35 external

    The homepage links to 93 pages on printmate.co.id and 35 external pages.

6 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Perusahaan penyedia mesin cetak digital dari brand besar seperti Atexco, Mimaki, Gongzheng, Beyond, Gmate, Shenlan, dan…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://printmate.co.id/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://printmate.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 (705 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 12 pages without a meta description

    https://printmate.co.id/products, https://printmate.co.id/products/creative-printers, https://printmate.co.id/products/engraving-and-laser-machines, https://printmate.co.id/products/cutting-plotters-machine, https://printmate.co.id/products/professional-photo-printers and https://printmate.co.id/products/paper-and-consumables and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://printmate.co.id/products, https://printmate.co.id/products/creative-printers, https://printmate.co.id/products/engraving-and-laser-machines, https://printmate.co.id/products/textile-and-apparel-printers, https://printmate.co.id/products/cutting-plotters-machine and https://printmate.co.id/products/professional-photo-printers and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://printmate.co.id/products/creative-printers, https://printmate.co.id/products/engraving-and-laser-machines, https://printmate.co.id/products/textile-and-apparel-printers, https://printmate.co.id/products/cutting-plotters-machine, https://printmate.co.id/products/professional-photo-printers and https://printmate.co.id/products/paper-and-consumables and 2 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 23 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 2 broken images

    2 images failed to load on a phone, for example https://printmate.co.id/.

  • 30 small tap targets

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

  • 2 low-resolution images

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 332 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact” and “BOOK A CALL”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact” and “Book A Call”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 2 other companies contacted

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

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
WordPress
Framework
jQuery

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on printmate.co.id, including 14 speed issues, 3 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