Website review, no card needed
tripakarta.co.id website review
Visit site (opens in a new tab)Reviewed 27 October 202653 issues · 94 checks
This review found 53 issues worth fixing on tripakarta.co.id, 19 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 99 ms |
| May 16, 2026 | 99 ms |
| May 23, 2026 | 105 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 105 ms |
| Jun 13, 2026 | 106 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 101 ms |
| Jul 18, 2026 | 99 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 99 ms |
| Aug 15, 2026 | 97 ms |
| Aug 22, 2026 | 97 ms |
| Aug 29, 2026 | 101 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 109 ms |
| Sep 26, 2026 | 101 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 96 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
1.2 s
2.3 s
3.5 s
4.6 s
5.8 s
6.9 s
8.1 s
9.2 s
Speed
Use efficient cache lifetimes
10.8 s · 29.7 MB49 files are served with short cache lifetimes, so returning visitors download them again (29.7 MB).
Improve image delivery
6.0 s · 6.5 MB22 images could be 6.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.0 s faster on a phone.
Reduce unused JavaScript
1.8 s · 315 KiBAbout 315 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.8 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Font display
1.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.0 s).
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, lenna.ai and Cloudflare CDN and others), adding 1.6 MB and 551 ms of main-thread time.
Reduce unused CSS
450 ms · 121 KiBAbout 121 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 255 ms
255 msGoogle Tag Manager costs a phone 255 ms of main-thread work and 178 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.
lenna.ai adds 190 ms
190 mslenna.ai costs a phone 190 ms of main-thread work and 627 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.
Amazon Web Services adds 0 ms
0 msAmazon Web Services costs a phone 0 ms of main-thread work and 548 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 202 ms. During a long task the page ignores taps.
Minify CSS
17 KiB17 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 455 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 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: 64.8 s
64.8 sYour largest element takes 64.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Sesuatu Hal yang Baru Sedang Kami Persiapkan.”.
Time to Interactive: 69.6 s
69.6 sThe page becomes fully interactive after 69.6 s. Good is under 3.8 s.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.223
0.223The layout shifts by 0.223 while loading, so content jumps under the reader's thumb. Good is under 0.1.
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 277 ms
277 msScripts block taps and scrolling for 277 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 99 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 116 ms
116 msReal visitors wait 116 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 30.2 MB in 83 requests
30.2 MBYour homepage downloads 30.2 MB in 83 requests on a phone: images 28.9 MB (45), scripts 836 KiB (6) and fonts 252 KiB (3). Under 2 MB keeps phones on slow connections fast.
12 images over 500 KB
12 images weigh 26.1 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
4.6 MB7 images are downloaded at several times the size a phone draws them, for example The-most-Promising-General-Insurance-2026.jpg at 4,860 px wide, shown at 326 px. Resized copies would save about 4.6 MB.
28 images in older formats
28 images (28.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.
14 images below the first screen load straight away
14 images further down the page (5.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
1786354216_6a799a288917a.png 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).
About 8.6 g of CO₂ per visit
8.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.55 g of CO₂e: 1026.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (29 elements)
All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Asuransi Tri pakarta”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“.”, “TRIPA Travel Insurance” and “TRIPA Smart”). One clear main headline is easier for people and search engines.
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 (270 characters)
Your meta description is 270 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://tripakarta.co.id/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
40 internal links, 8 external
The homepage links to 40 pages on tripakarta.co.id and 8 external pages.
2 checks passed
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.
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://tripakarta.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,414 words), so crawlers that don't run JavaScript still read it.
Other pages
16 pages share 2 titles
/, https://tripakarta.co.id/produk, https://tripakarta.co.id/jaringan, https://tripakarta.co.id/tentang-kami, https://tripakarta.co.id/pengajuan/polis and https://tripakarta.co.id/pengajuan/klaim and 1 other all use the title “Asuransi Tri pakarta”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://tripakarta.co.id/produk, https://tripakarta.co.id/jaringan, https://tripakarta.co.id/tentang-kami, https://tripakarta.co.id/pengajuan/polis, https://tripakarta.co.id/pengajuan/klaim and https://tripakarta.co.id/pengajuan/pengaduan and 9 others use the same meta description. A description written for each page earns more clicks.
13 pages without an H1
https://tripakarta.co.id/tentang-kami, https://tripakarta.co.id/pengajuan/polis, https://tripakarta.co.id/pengajuan/klaim, https://tripakarta.co.id/pengajuan/pengaduan, https://tripakarta.co.id/pembelian/polis-kendaraan and https://tripakarta.co.id/pembelian/polis-kecelakaan-diri and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://tripakarta.co.id/pengajuan/klaim, https://tripakarta.co.id/pembelian/status, https://tripakarta.co.id/klaim/form/polis-kendaraan, https://tripakarta.co.id/klaim/form/polis-kebakaran, https://tripakarta.co.id/klaim/form/polis-kecelakaan-diri and https://tripakarta.co.id/klaim/form/polis-travel 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
5 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.
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 broken images
3 images failed to load on a phone, for example https://tripakarta.co.id/img/CLIENT'.png.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
6 of 7 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.
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 707 words of copy
The homepage carries about 707 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Subscribe Now”.
1 call to action
The homepage has 1 call to action, for example “Subscribe Now”.
1 short form
A short form (2 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks, 1 customer or partner logo and 2 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
10 other companies contacted
Loading the homepage contacts 10 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 tripakarta.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
- jQuery
- Analytics
- Google Analytics
- Hosting
- PT Biznet Gio Nusantara
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on tripakarta.co.id, including 22 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.