Website review, no card needed
trapo.co.id website review
Visit site (opens in a new tab)Reviewed 6 November 202646 issues · 90 checks
This review found 46 issues worth fixing on trapo.co.id, 15 of them high impact, across 90 checks. The most urgent: page weight: 131.4 MB in 382 requests. 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
69D- #102,066 of 118,776 reviewed websitesbeats 12%
- #61,899 of 67,423 online storesbeats 7%
- #57,216 of 61,470 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 170 ms |
| May 23, 2026 | 171 ms |
| May 30, 2026 | 177 ms |
| Jun 6, 2026 | 185 ms |
| Jun 13, 2026 | 186 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 159 ms |
| Jul 25, 2026 | 156 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 161 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 171 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 176 ms |
| Oct 17, 2026 | 170 ms |
| Oct 24, 2026 | 164 ms |
| Oct 31, 2026 | 177 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
Speed
Render-blocking requests
2.0 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and TikTok and others), adding 127.6 MB and 697 ms of main-thread time.
Shopify adds 190 ms
190 msShopify costs a phone 190 ms of main-thread work and 126.6 MB 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.
Reduce unused JavaScript
600 ms · 817 KiBAbout 817 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
500 ms · 571 KiB16 images could be 571 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 124 KiBAbout 124 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 248 KiB20 files are served with short cache lifetimes, so returning visitors download them again (248 KiB).
Google Tag Manager adds 211 ms
211 msGoogle Tag Manager costs a phone 211 ms of main-thread work and 441 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.
Minify JavaScript
65 KiB65 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
42 KiBPolyfills for old browsers add 42 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 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.
Largest Contentful Paint: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 22.8 s
22.8 sThe page becomes fully interactive after 22.8 s. Good is under 3.8 s.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 170 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 198 ms
198 msReal visitors wait 198 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 790 ms
790 msReal visitors wait 790 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 181 ms
181 msScripts block the page for only 181 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.037
0.037The layout barely moves while loading (CLS 0.037, good is under 0.1).
Images and page weight
Page weight: 131.4 MB in 382 requests
131.4 MBYour homepage downloads 131.4 MB in 382 requests on a phone: media 125.2 MB (20), images 2.6 MB (44) and scripts 2.0 MB (91). Under 2 MB keeps phones on slow connections fast.
10 images below the first screen load straight away
10 images further down the page (545 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
34 KiB1 image is downloaded at several times the size a phone draws it, for example Indonesia_Menyumbang_Sampah.jpg at 1,176 px wide, shown at 370 px. Resized copies would save about 34 KiB.
About 37.3 g of CO₂ per visit
37.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 37.26 g of CO₂e: 4470.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Invalid ARIA attributes
20 elements use ARIA attributes their role does not allow, which confuses screen readers.
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
11 tap targets too small
11 tap targets are too small or too close together to hit reliably with a finger.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (25 elements)
All page content should be contained by landmarks: 25 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.
29 links without text
29 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 (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
35 links crawlers can't follow
35 links have no real href, so search engines can't follow them.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
199 internal links, 26 external
The homepage links to 199 pages on trapo.co.id and 26 external pages.
5 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “Aksesoris Mobil TRAPO Indonesia - Stylish & Protective”.
Canonical URL set
The canonical URL is https://trapo.co.id/.
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://trapo.co.id/sitemap.xml.
AI search readiness
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://trapo.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 (1,052 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://trapo.co.id/products/karpet-mobil-trapo-indonesia-hyundai-ioniq-5-2022-sekarang-trapo-xtreme, which answers with an error. Visitors hit a dead end and search engines drop it.
9 pages without a meta description
https://trapo.co.id/products/karpet-mobil-trapo-indonesia-chery-omoda-5-2023-sekarang-trapo-xtreme, https://trapo.co.id/products/karpet-mobil-trapo-indonesia-chery-omoda-e5-2023-sekarang-trapo-xtreme, https://trapo.co.id/products/karpet-mobil-trapo-indonesia-mitsubishi-xpander-2022-sekarang-trapo-xtreme, https://trapo.co.id/products/karpet-mobil-trapo-indonesia-hyundai-kona-electric-2021-sekarang-trapo-xtreme, https://trapo.co.id/products/karpet-mobil-trapo-indonesia-honda-br-v-2022-sekarang-trapo-xtreme and https://trapo.co.id/products/karpet-mobil-trapo-indonesia-toyota-rush-2018-sekarang-trapo-xtreme and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 107 found) and read each the way a search engine does.
5 checks passed
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.
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 9 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
48 of 50 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 532 words of copy
The homepage carries about 532 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: “Shop”.
7 calls to action
The homepage has 7 calls to action, for example “Shop”, “Learn More” and “Shop Now”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
45 other companies contacted
Loading the homepage contacts 45 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 trapo.co.id, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 21 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pwa Mobile App · Loyalty Rewards And Referrals · Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · Sales Discounts · Koala Upsell Gift · Selleasy · Avada Faqs · Booster Kit By Qikify · cloudfront.net · trackedlink.net · develic.com · hulkapps.com · apaylater.com · nfcube.com · herokuapp.com · nice-team.net · amazonaws.com · oxiapps.com · cart-bot.net · good-apps.co
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on trapo.co.id, including 19 speed issues, 4 SEO issues and 4 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.