Website review, no card needed

gandariacity.co.id logo

gandariacity.co.id website review

Visit site (opens in a new tab)Reviewed 20 November 202649 issues · 83 checks

This review found 49 issues worth fixing on gandariacity.co.id, 15 of them high impact, across 83 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
2.0 s1.0 sMay 30Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.1 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.2 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Oct 10, 20261.9 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
89 ms72 msMay 30Sep 1986 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202680 ms
Jun 6, 202680 ms
Jun 13, 202686 ms
Jun 20, 202683 ms
Jun 27, 202682 ms
Jul 4, 202682 ms
Jul 11, 202681 ms
Jul 18, 202682 ms
Jul 25, 202686 ms
Aug 1, 202687 ms
Aug 8, 202684 ms
Aug 15, 202684 ms
Aug 22, 202679 ms
Aug 29, 202674 ms
Sep 5, 202675 ms
Sep 12, 202678 ms
Sep 19, 202686 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 gandariacity.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gandariacity.co.id at 1.8 s1.8 s
  2. gandariacity.co.id at 3.7 s3.7 s
  3. gandariacity.co.id at 5.5 s5.5 s
  4. gandariacity.co.id at 7.4 s7.4 s
  5. gandariacity.co.id at 9.2 s9.2 s
  6. gandariacity.co.id at 11.1 s11.1 s
  7. gandariacity.co.id at 12.9 s12.9 s
  8. gandariacity.co.id at 14.8 s14.8 s

Speed

10 to fix29
  • Improve image delivery

    4.3 s · 1.2 MB

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

  • Render-blocking requests

    3.1 s

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

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    900 ms · 215 KiB

    29 files are served with short cache lifetimes, so returning visitors download them again (215 KiB).

  • Reduce unused JavaScript

    660 ms · 141 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Unpkg and Google Fonts and others), adding 304 KiB and 627 ms of main-thread time.

  • Google Tag Manager adds 620 ms

    620 ms

    Google Tag Manager costs a phone 620 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.

  • Reduce unused CSS

    490 ms · 106 KiB

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

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 492 ms. During a long task the page ignores taps.

  • Main-thread work: 2.2 s

    A phone's processor spends 2.2 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Minify JavaScript

    10 ms · 23 KiB

    23 KiB could be saved by minifying JavaScript.

  • Minify CSS

    10 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

12 to fix0
  • 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: 12.7 s

    12.7 s

    Your largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (8.8 s).

  • Speed Index: 15.2 s

    15.2 s

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

  • Time to Interactive: 13.6 s

    13.6 s

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

  • Cumulative Layout Shift: 0.29

    0.29

    The layout shifts by 0.29 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 692 ms

    692 ms

    Scripts block taps and scrolling for 692 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.0 s

    3.0 s

    Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.17

    0.17

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

  • Largest content (LCP) got 40% slower for real visitors

    +40%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

1 checks passed
  • Real-user TTFB: 793 ms

    793 ms

    Real visitors wait 793 ms for your server to start answering (75th percentile). Good is under 800 ms.

Images and page weight

5 to fix33
  • 3 images over 500 KB

    3 images weigh 4.0 MB together. On a phone connection a single image that size takes seconds.

  • 10 images far larger than shown

    3.6 MB

    10 images are downloaded at several times the size a phone draws them, for example 20230117094656.jpg at 6,000 px wide, shown at 390 px. Resized copies would save about 3.6 MB.

  • 17 images in older formats

    17 images (5.7 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.

  • Page weight: 2.4 MB in 44 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 44 requests on a phone: images 1.8 MB (20), scripts 334 KiB (9) and fonts 151 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 9 images below the first screen load straight away

    9 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.68 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.68 g of CO₂e: 81.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fixGoogle 8191
  • 5 tap targets too small

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

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

    All page content should be contained by landmarks: 3 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 8 links without text

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

7 to fixGoogle 9271
  • Title is short (13 characters)

    Your title is only 13 characters: “Gandaria City”. 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.

  • Meta description is short (57 characters)

    Your meta description is only 57 characters: “Gandaria City is the largest retail mall in South Jakarta”. 70 to 160 characters is enough to sell the click.

  • 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 XML sitemap

    No XML sitemap at https://gandariacity.co.id/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 16 internal links, 5 external

    The homepage links to 16 pages on gandariacity.co.id and 5 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Follow Our Social Media”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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://gandariacity.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.

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

2 to fix93
  • 12 pages share a meta description

    https://gandariacity.co.id/shop, https://gandariacity.co.id/dine, https://gandariacity.co.id/art/gallery, https://gandariacity.co.id/whats_on, https://gandariacity.co.id/royalty and https://gandariacity.co.id/about and 6 others use the same meta description. A description written for each page earns more clicks.

  • 10 pages without an H1

    https://gandariacity.co.id/shop, https://gandariacity.co.id/dine, https://gandariacity.co.id/whats_on, https://gandariacity.co.id/royalty, https://gandariacity.co.id/whats_on/detail/853/holoholo and https://gandariacity.co.id/whats_on/detail/852/holycow and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://gandariacity.co.id/art/gallery, https://gandariacity.co.id/whats_on, https://gandariacity.co.id/whats_on/detail/853/holoholo, https://gandariacity.co.id/whats_on/detail/852/holycow, https://gandariacity.co.id/whats_on/detail/851/electronic-city and https://gandariacity.co.id/whats_on/detail/850/mako and 1 other 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.

  • 4 pages slow to respond

    https://gandariacity.co.id/dine, https://gandariacity.co.id/art/gallery, https://gandariacity.co.id/whats_on and https://gandariacity.co.id/royalty took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 12 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 12 pages that loaded have a meta description.

  • 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 10 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 49 words

    The homepage has only about 49 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Shop”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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

    4

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 gandariacity.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

Framework
jQuery
Analytics
Google Analytics
Hosting
Ardh As Id Ardh Global Indonesia, Pt

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on gandariacity.co.id, including 22 speed issues, 7 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