Website review, no card needed

chandrakarya.com logo

chandrakarya.com website review

Visit site (opens in a new tab)Reviewed 25 October 202655 issues · 99 checks

This review found 55 issues worth fixing on chandrakarya.com, 21 of them high impact, across 99 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
3.4 s2.8 sMay 2Oct 172.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.1 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.2 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.3 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.2 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.3 s
Sep 19, 20263.3 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
156 ms115 msMay 2Oct 17120 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026131 ms
May 9, 2026127 ms
May 16, 2026129 ms
May 23, 2026135 ms
May 30, 2026133 ms
Jun 6, 2026133 ms
Jun 13, 2026130 ms
Jun 20, 2026127 ms
Jun 27, 2026128 ms
Jul 4, 2026128 ms
Jul 11, 2026131 ms
Jul 18, 2026135 ms
Jul 25, 2026133 ms
Aug 1, 2026130 ms
Aug 8, 2026132 ms
Aug 15, 2026135 ms
Aug 22, 2026139 ms
Aug 29, 2026151 ms
Sep 5, 2026146 ms
Sep 12, 2026142 ms
Sep 19, 2026141 ms
Sep 26, 2026131 ms
Oct 3, 2026131 ms
Oct 10, 2026128 ms
Oct 17, 2026120 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 chandrakarya.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. chandrakarya.com at 1.2 s1.2 s
  2. chandrakarya.com at 2.5 s2.5 s
  3. chandrakarya.com at 3.7 s3.7 s
  4. chandrakarya.com at 4.9 s4.9 s
  5. chandrakarya.com at 6.2 s6.2 s
  6. chandrakarya.com at 7.4 s7.4 s
  7. chandrakarya.com at 8.6 s8.6 s
  8. chandrakarya.com at 9.9 s9.9 s

Speed

10 to fix52
  • Improve image delivery

    3.6 s · 10.1 MB

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

  • Render-blocking requests

    4.0 s

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

  • Reduce unused JavaScript

    1.8 s · 533 KiB

    About 533 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.

  • Font display

    1.1 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 42). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 97 KiB

    About 97 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.

  • Use efficient cache lifetimes

    350 ms · 17 KiB

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

  • Legacy JavaScript

    350 ms · 9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • qontak.com adds 121 ms

    121 ms

    qontak.com costs a phone 121 ms of main-thread work and 316 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.

  • Google CDN adds 116 ms

    116 ms

    Google CDN costs a phone 116 ms of main-thread work and 348 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 third-party services on the page

    8 third-party services load with your homepage (qontak.com, Google Tag Manager and Google CDN and others), adding 993 KiB and 385 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • 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

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 490 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Real-user LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 3.7 s

    3.7 s

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 14.2 s

    14.2 s

    Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Branded Springbed Chandra Karya”.

  • Time to Interactive: 14.3 s

    14.3 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Real-user CLS: 0.16

    0.16

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

  • 24 images without width and height

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

  • Total Blocking Time: 265 ms

    265 ms

    Scripts block taps and scrolling for 265 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-17, real Chrome visitors' tap response (inp) went from 131 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -7%

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

2 checks passed
  • Real-user INP: 183 ms

    183 ms

    Real visitors wait 183 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Cumulative Layout Shift: 0.056

    0.056

    The layout barely moves while loading (CLS 0.056, good is under 0.1).

Images and page weight

5 to fix28
  • Page weight: 12.8 MB in 157 requests

    12.8 MB

    Your homepage downloads 12.8 MB in 157 requests on a phone: images 11.5 MB (71), scripts 911 KiB (13) and fonts 164 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 2.9 MB together. On a phone connection a single image that size takes seconds.

  • 24 images in older formats

    24 images (6.1 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.

  • 16 images below the first screen load straight away

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

  • 5 images far larger than shown

    419 KiB

    5 images are downloaded at several times the size a phone draws them, for example okt26banner-web-produk-01.png at 1,280 px wide, shown at 390 px. Resized copies would save about 419 KiB.

  • About 3.6 g of CO₂ per visit

    3.62 g

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

Accessibility

13 to fixGoogle 5279
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 24 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 21 images without alt text

    21 images have no alt text, which hurts accessibility and image search.

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

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

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

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

  • 30 links without text

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

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 29 automated accessibility rules passed

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

SEO

7 to fixGoogle 8365
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (29 characters)

    Your title is only 29 characters: “Home - Chandra Karya Furnitur”. 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.

  • 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 (188 characters)

    Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://www.chandrakarya.com/sitemap.xml, so Google discovers your pages only by following links.

  • 4 links with vague text

    4 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 set, so this is minor.

  • 250 internal links, 39 external

    The homepage links to 250 pages on chandrakarya.com and 39 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

1 to fix88
  • 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://www.chandrakarya.com/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,146 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 13 pages without a meta description

    https://www.chandrakarya.com/module/paymentconfirmation/confirm, https://www.chandrakarya.com/3-shop, https://www.chandrakarya.com/48-spring-bed, https://www.chandrakarya.com/54-sofa, https://www.chandrakarya.com/8-ruang-tamu and https://www.chandrakarya.com/4-ruang-makan and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.chandrakarya.com/3-shop, https://www.chandrakarya.com/48-spring-bed, https://www.chandrakarya.com/54-sofa, https://www.chandrakarya.com/8-ruang-tamu, https://www.chandrakarya.com/4-ruang-makan and https://www.chandrakarya.com/12-kamar-tidur and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.chandrakarya.com/4-ruang-makan, https://www.chandrakarya.com/12-kamar-tidur, https://www.chandrakarya.com/56-kamar-tidur-anak, https://www.chandrakarya.com/13-ruang-kerja, https://www.chandrakarya.com/53-bantal-guling and https://www.chandrakarya.com/31-springbeds took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 66 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.

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

Best practices

3 to fixGoogle 5085
  • 58 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-randall.82cartcloud.com/v.3.3.5/css/superfish-modified.css' from origin 'https…”.

  • 7 low-resolution images

    7 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

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

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 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 319 words of copy

    The homepage carries about 319 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP” and “PROJECT ORDER”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “SHOP”, “Project Order” and “Subscribe”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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 chandrakarya.com, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on chandrakarya.com, including 21 speed issues, 7 SEO issues and 2 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