Website review, no card needed
metranet.co.id website review
Visit site (opens in a new tab)Reviewed 19 November 202639 issues · 67 checks
This review found 39 issues worth fixing on metranet.co.id, 13 of them high impact, across 67 checks. The most urgent: improve image delivery. 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.8 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.0 s |
| Nov 7, 2026 | 2.9 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 124 ms |
| Jun 6, 2026 | 123 ms |
| Jun 13, 2026 | 125 ms |
| Jun 27, 2026 | 106 ms |
| Jul 4, 2026 | 121 ms |
| Jul 18, 2026 | 103 ms |
| Jul 25, 2026 | 145 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 149 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
0.7 s
1.4 s
2.1 s
2.8 s
3.4 s
4.1 s
4.8 s
5.5 s
Speed
Improve image delivery
4.0 s · 3.3 MB15 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
15.3 MB45 files are served with short cache lifetimes, so returning visitors download them again (15.3 MB).
Reduce unused JavaScript
750 ms · 132 KiBAbout 132 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Document request latency
550 ms · 108 KiBThe 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
566 msReduce initial server response time. Google estimates savings of 566 ms on a phone.
Render-blocking requests
550 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 377 ms. During a long task the page ignores taps.
Google Tag Manager adds 311 ms
311 msGoogle Tag Manager costs a phone 311 ms of main-thread work and 160 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.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 809 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Server response: 666 ms
666 msYour server takes 666 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 221 KiB and 312 ms of main-thread time.
Reduce unused CSS
69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page.
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.
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: 100.9 s
100.9 sYour largest element takes 100.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We Start With Excellence Our governance solutions build tru…”.
Time to Interactive: 104.7 s
104.7 sThe page becomes fully interactive after 104.7 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 994 ms
994 msScripts block taps and scrolling for 994 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
24 images without width and height
24 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 124 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
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: 633 ms
633 msReal visitors wait 633 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.5 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 38.6 MB in 104 requests
38.6 MBYour homepage downloads 38.6 MB in 104 requests on a phone: images 24.5 MB (63), other files 13.5 MB (23) and scripts 398 KiB (9). Under 2 MB keeps phones on slow connections fast.
About 10.9 g of CO₂ per visit
10.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.94 g of CO₂e: 1313.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
5 buttons without a name
5 buttons have no accessible name, so screen readers announce just “button”.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (28 characters)
Your title is only 28 characters: “Metranet | Flying The Giants”. 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.
9 H1 headlines
There are 9 <h1> headlines (“Solutions”, “Advertisement Solutions Platform” and “Community Solutions Platform”). 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.
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 favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
33 internal links, 9 external
The homepage links to 33 pages on metranet.co.id and 9 external pages.
2 checks passed
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://metranet.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.
1 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.
Other pages
9 linked pages are broken
Your homepage links to https://www.metranet.co.id/company/about-us, https://www.metranet.co.id/company/client, https://www.metranet.co.id/esg, https://www.metranet.co.id/news, https://www.metranet.co.id/careers and https://www.metranet.co.id/contact and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.
4 pages without a title
https://www.metranet.co.id/business/cazbox, https://www.metranet.co.id/business/xooply, https://www.metranet.co.id/news/detail/140 and https://www.metranet.co.id/news/detail/138 have no <title>, so Google invents the link text in results.
6 pages without a meta description
https://www.metranet.co.id/company/investor-relation, https://www.metranet.co.id/business, https://www.metranet.co.id/business/cazbox, https://www.metranet.co.id/business/xooply, https://www.metranet.co.id/news/detail/140 and https://www.metranet.co.id/news/detail/138 have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://www.metranet.co.id/company/investor-relation, https://www.metranet.co.id/business, https://www.metranet.co.id/business/cazbox, https://www.metranet.co.id/business/xooply, https://www.metranet.co.id/news/detail/140 and https://www.metranet.co.id/news/detail/138 have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.metranet.co.id/business has 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.
4 pages slow to respond
https://www.metranet.co.id/company/investor-relation, https://www.metranet.co.id/business, https://www.metranet.co.id/business/cazbox and https://www.metranet.co.id/business/xooply took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage and read each the way a search engine does.
3 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
4 console errors
4 errors were logged to the browser console during Google's test (“Failed to load resource: net::ERR_TIMED_OUT”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 448 words of copy
The homepage carries about 448 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
Social proof on the page
Social proof on the homepage: 15 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Analytics.
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 metranet.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
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on metranet.co.id, including 19 speed issues, 8 SEO issues and 1 conversion gap. 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.