idlc.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 4.2 s

  4.2 s

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

• Real-user CLS: 0.33

  0.33

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

• Real-user FCP: 3.3 s

  3.3 s

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

• Real-user TTFB: 1.1 s

  1.1 s

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

• Tap response (INP) held steady for real visitors

  0%

  Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 142 ms to 144 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 4.1 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 2.3 MB

  2.3 MB

  Your homepage downloads 2.3 MB on a phone, 32 KiB of it images (1%). Under 2 MB keeps phones on slow connections fast.

• About 0.6 g of CO₂ per visit

  0.65 g

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

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

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

  Elements (1)

• No H1 headline

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

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

• 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://idlc.com/sitemap.xml, so Google discovers your pages only by following links.

• No robots.txt

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

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

• No X (Twitter) card tag

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

• 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 /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 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors.”.

• http:// does not redirect

  http://idlc.com does not redirect to https, so some visitors land on the insecure version.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  idlc.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  idlc.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

• Only about 0 words

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

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

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 90/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 5 trackers load before any consent

  5

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel (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.

• 13 cookies set on arrival

  13

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