Website review, no card needed
gli.id website review
Visit site (opens in a new tab)Reviewed 29 October 202637 issues · 83 checks
This review found 37 issues worth fixing on gli.id, 10 of them high impact, across 83 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 121 ms |
| May 16, 2026 | 122 ms |
| May 23, 2026 | 122 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 126 ms |
| Jun 27, 2026 | 125 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 134 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 141 ms |
| Aug 1, 2026 | 142 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 126 ms |
| Sep 5, 2026 | 124 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 115 ms |
| Oct 24, 2026 | 116 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
Use efficient cache lifetimes
2.4 s · 2.4 MB61 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).
Render-blocking requests
3.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Reduce unused JavaScript
1.9 s · 511 KiBAbout 511 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Font display
950 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 950 ms).
Reduce unused CSS
600 ms · 111 KiBAbout 111 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.
Improve image delivery
698 KiB19 images could be 698 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google Fonts), adding 226 KiB and 162 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 103 ms. During a long task the page ignores taps.
Document request latency
27 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 308 ms of it running JavaScript. That is comfortably low.
Server response: 159 ms
159 msYour server sent the HTML in 159 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.
First Contentful Paint: 5.6 s
5.6 sThe first text or image appears after 5.6 s on a phone. Good is under 1.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GLI shares its insights and lessons learned over the years …”. Most of its time is element render delay (4.0 s).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
39 images without width and height
39 images have no width and height attributes, so the layout jumps as each one loads.
Time to Interactive: 6.2 s
6.2 sThe page becomes fully interactive after 6.2 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 121 ms to 116 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.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.7 MB in 70 requests
2.7 MBYour homepage downloads 2.7 MB in 70 requests on a phone: images 1.6 MB (55), scripts 770 KiB (3) and stylesheets 165 KiB (6). Under 2 MB keeps phones on slow connections fast.
16 images below the first screen load straight away
16 images further down the page (971 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
9 images in older formats
9 images (589 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.
8 images far larger than shown
161 KiB8 images are downloaded at several times the size a phone draws them, for example cover_1128_824_home---alfagift-illustration.png.webp at 1,128 px wide, shown at 358 px. Resized copies would save about 161 KiB.
About 0.8 g of CO₂ per visit
0.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 91.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (14 elements)
ARIA role should be appropriate for the element: 14 elements on the page fail this check, rated minor by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 57 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
60 internal links, 4 external
The homepage links to 60 pages on gli.id and 4 external pages.
6 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “GLI is a knowledge company from Alfamart, offering Alfagift (Omnichannel), Consumer Marketing, Data Solutions, Digital …”.
One H1 headline
Your main headline reads: “Leveraging over 11 years of expertise, GLI delivers innovative products and services that drive sustainable growth and …”.
Title: 59 characters
Your title is a healthy 59 characters: “PT Global Loyalty Indonesia (GLI) – Alfagift, CRM, Big Data”.
Canonical URL set
The canonical URL is https://gli.id/.
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://gli.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.
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 (510 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://gli.id/id all use the title “PT Global Loyalty Indonesia (GLI) – Alfagift, CRM, Big Data”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without an H1
https://gli.id/about-gli, https://gli.id/alfagift, https://gli.id/consumer-marketing, https://gli.id/data-solution, https://gli.id/digital-activation and https://gli.id/merchant and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://gli.id/faq 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.
8 pages slow to respond
https://gli.id/alfagift, https://gli.id/digital-activation, https://gli.id/merchant, https://gli.id/voucher-point-exchange-id, https://gli.id/insight-hub-1 and https://gli.id/career 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 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
1 broken image
1 image failed to load on a phone, for example https://gli.id/assets/source/images/material/icon-fb.svg.
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 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 421 words of copy
The homepage carries about 421 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: “Learn More”.
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “Learn More” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are 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.
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.
5 other companies contacted
Loading the homepage contacts 5 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 gli.id, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on gli.id, including 15 speed issues, 3 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.