Website review, no card needed

elcorps.co.id logo

elcorps.co.id website review

Visit site (opens in a new tab)Reviewed 27 October 202646 issues · 85 checks

This review found 46 issues worth fixing on elcorps.co.id, 20 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
5.6 s2.4 sMay 9Oct 175.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
Jul 11, 20262.8 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20263.2 s
Oct 17, 20265.3 s
Real-visitor tap response (INP)75th percentile, phones
124 ms99 msJul 11Aug 1121 ms
Show as table
DateReal-visitor tap response (INP)
Jul 11, 2026102 ms
Jul 18, 2026102 ms
Jul 25, 2026113 ms
Aug 1, 2026121 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 elcorps.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. elcorps.co.id at 2.4 s2.4 s
  2. elcorps.co.id at 4.9 s4.9 s
  3. elcorps.co.id at 7.3 s7.3 s
  4. elcorps.co.id at 9.7 s9.7 s
  5. elcorps.co.id at 12.2 s12.2 s
  6. elcorps.co.id at 14.6 s14.6 s
  7. elcorps.co.id at 17.0 s17.0 s
  8. elcorps.co.id at 19.5 s19.5 s

Speed

11 to fix55
  • Use efficient cache lifetimes

    21.1 s · 5.7 MB

    141 files are served with short cache lifetimes, so returning visitors download them again (5.7 MB).

  • Render-blocking requests

    14.5 s

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

  • Reduce unused CSS

    9.1 s · 1.5 MB

    About 1.5 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 9.1 s faster on a phone.

  • Reduce unused JavaScript

    5.1 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.

  • Improve image delivery

    1.1 s · 986 KiB

    17 images could be 986 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • Document request latency

    800 ms · 158 KiB

    The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    784 ms

    Reduce initial server response time. Google estimates savings of 784 ms on a phone.

  • Minify CSS

    310 ms · 49 KiB

    49 KiB could be saved by minifying CSS.

  • Google Maps adds 238 ms

    238 ms

    Google Maps costs a phone 238 ms of main-thread work and 474 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.

  • Server response: 884 ms

    884 ms

    Your server takes 884 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 Maps, cleantalk.org and Other Google APIs/SDKs), adding 486 KiB and 248 ms of main-thread time.

  • Minify JavaScript

    90 ms · 18 KiB

    18 KiB could be saved by minifying JavaScript.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 79 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.

1 checks passed
  • Main-thread work: 1.8 s

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

Core Web Vitals

9 to fix67
  • 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 FCP: 4.8 s

    4.8 s

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

  • Real-user TTFB: 3.4 s

    3.4 s

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

  • First Contentful Paint: 16.2 s

    16.2 s

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

  • Largest Contentful Paint: 38.4 s

    38.4 s

    Your largest element takes 38.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 33.8 s

    33.8 s

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

  • Time to Interactive: 38.9 s

    38.9 s

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

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

    +34%

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

  • 14 images without width and height

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

2 checks passed
  • Cumulative Layout Shift: 0.011

    0.011

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

  • Total Blocking Time: 29 ms

    29 ms

    Scripts block the page for only 29 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 6.4 MB in 162 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 162 requests on a phone: images 2.4 MB (25), scripts 1.9 MB (68) and stylesheets 1.7 MB (56). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (846 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.

  • 11 images below the first screen load straight away

    11 images further down the page (834 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.80 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8690
  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

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

  • 2 links without text

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

6 to fixGoogle 8565
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (7 characters)

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

  • 99 internal links, 4 external

    The homepage links to 99 pages on elcorps.co.id and 4 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://elcorps.co.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://elcorps.co.id/wp-sitemap.xml.

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://elcorps.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 (671 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 11 pages without a meta description

    https://elcorps.co.id/index.php/tentang-kami, https://elcorps.co.id/index.php/struktur-kepemilikan, https://elcorps.co.id/index.php/management, https://elcorps.co.id/index.php/penghargaan, https://elcorps.co.id/index.php/mitra-elcorps and https://elcorps.co.id/index.php/agen-elcorps and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://elcorps.co.id/index.php/tentang-kami, whose canonical is https://elcorps.co.id/tentang-kami. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages slow to respond

    https://elcorps.co.id/index.php/tentang-kami, https://elcorps.co.id/index.php/struktur-kepemilikan, https://elcorps.co.id/index.php/management, https://elcorps.co.id/index.php/penghargaan, https://elcorps.co.id/index.php/mitra-elcorps and https://elcorps.co.id/index.php/agen-elcorps and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

7 to fix29
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 335 words of visible text.

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

CMS
WordPress
Framework
jQuery
Hosting
CV. Rumahweb Indonesia

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on elcorps.co.id, including 20 speed issues, 6 SEO issues and 7 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