Website review, no card needed

edotcogroup.com logo

edotcogroup.com website review

Visit site (opens in a new tab)Reviewed 27 October 202632 issues · 73 checks

This review found 32 issues worth fixing on edotcogroup.com, 12 of them high impact, across 73 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.1 s1.6 sMay 9Sep 261.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
146 ms121 msMay 9Sep 26131 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026132 ms
May 16, 2026133 ms
May 23, 2026132 ms
May 30, 2026127 ms
Jun 6, 2026124 ms
Jun 13, 2026127 ms
Jun 20, 2026132 ms
Jun 27, 2026139 ms
Jul 4, 2026140 ms
Jul 11, 2026136 ms
Jul 18, 2026143 ms
Jul 25, 2026131 ms
Aug 1, 2026129 ms
Aug 8, 2026136 ms
Aug 15, 2026131 ms
Aug 22, 2026131 ms
Aug 29, 2026129 ms
Sep 5, 2026130 ms
Sep 12, 2026128 ms
Sep 19, 2026130 ms
Sep 26, 2026131 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 edotcogroup.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. edotcogroup.com at 1.3 s1.3 s
  2. edotcogroup.com at 2.7 s2.7 s
  3. edotcogroup.com at 4.0 s4.0 s
  4. edotcogroup.com at 5.4 s5.4 s
  5. edotcogroup.com at 6.7 s6.7 s
  6. edotcogroup.com at 8.1 s8.1 s
  7. edotcogroup.com at 9.4 s9.4 s
  8. edotcogroup.com at 10.8 s10.8 s

Speed

6 to fix84
  • Improve image delivery

    1.4 s · 4.6 MB

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

  • Render-blocking requests

    1.4 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.4 s.

  • Mobile performance score: 84

    84/100

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

  • Font display

    850 ms

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

  • Use efficient cache lifetimes

    556 KiB

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

  • myqcloud.com adds 0 ms

    0 ms

    myqcloud.com costs a phone 0 ms of main-thread work and 556 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.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Analytics and myqcloud.com), adding 833 KiB and 146 ms of main-thread time.

  • Reduce unused JavaScript

    225 KiB

    About 225 KiB of JavaScript is downloaded but never used on this page.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    17 KiB

    About 17 KiB of CSS is downloaded but never applied on this page.

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 213 ms

    213 ms

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

Core Web Vitals

4 to fix86
  • Time to Interactive: 11.2 s

    11.2 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Largest Contentful Paint: 3.7 s

    3.7 s

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

  • 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

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 37 ms

    37 ms

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

Images and page weight

5 to fix18
  • Page weight: 21.7 MB in 64 requests

    21.7 MB

    Your homepage downloads 21.7 MB in 64 requests on a phone: media 15.2 MB (3), images 5.4 MB (30) and scripts 666 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 3.9 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    2.6 MB

    8 images are downloaded at several times the size a phone draws them, for example lifeedotco.png at 2,026 px wide, shown at 390 px. Resized copies would save about 2.6 MB.

  • 11 images in older formats

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

  • 10 images below the first screen load straight away

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

  • About 6.1 g of CO₂ per visit

    6.15 g

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

Accessibility

1 to fixGoogle 9698
  • 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.

  • 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 42 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 6343
  • Page is set to noindex

    The robots meta tag says “noindex”: Google is told not to list this page at all.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (17 characters)

    Your title is only 17 characters: “Homepage | EDOTCO”. 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 (53 characters)

    Your meta description is only 53 characters: “Building shared connectivity for a sustainable future”. 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 XML sitemap

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

  • No robots.txt

    There is no robots.txt at edotcogroup.com/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 80 internal links, 3 external

    The homepage links to 80 pages on edotcogroup.com and 3 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Shaping Future Connectivity in Asia”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    29%

    A phone browser shows 2,151 words, but the HTML your server sends has only 617. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://edotcogroup.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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix90
  • 14 linked pages hidden from search

    https://edotcogroup.com/about-us/our-brand, https://edotcogroup.com/about-us/meet-our-team, https://edotcogroup.com/about-us/corporate-governance, https://edotcogroup.com/about-us/ohs, https://edotcogroup.com/expertise and https://edotcogroup.com/expertise/infrastructure and 8 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 14 pages share a meta description

    https://edotcogroup.com/about-us/our-brand, https://edotcogroup.com/about-us/meet-our-team, https://edotcogroup.com/about-us/corporate-governance, https://edotcogroup.com/about-us/ohs, https://edotcogroup.com/expertise and https://edotcogroup.com/expertise/infrastructure and 8 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    6 of 6 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix63
  • 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 analytics detected

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

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

  • About 2,151 words of copy

    The homepage carries about 2,151 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us!”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us!” and “Join Us”.

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.

  • 2 cookies set on arrival

    2

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 edotcogroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Ace As Ap Ace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on edotcogroup.com, including 10 speed issues, 8 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