elligo.com website review

Not measured in this review.

• Largest content (LCP) held steady for real visitors

  -9%

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

• Page weight: 2.2 MB

  2.2 MB

  Your homepage downloads 2.2 MB on a phone, 64 KiB of it images (3%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  690e1b7fb05ffccabc706d57_home-hero-original-m-p-500.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  Elements (1)

• About 0.6 g of CO₂ per visit

  0.63 g

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

• 2 tap targets too small

  2 tap targets are too small or too close together to hit reliably with a finger.

  Elements (2)

• Frames without titles

  1 frame has no title, so screen-reader users cannot tell what it contains.

  Elements (1)

• Interactive controls must not be nested (1 element)

  Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

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

  Elements (1)

• 1 link without text

  1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

• 75 internal links, 13 external

  The homepage links to 75 pages on elligo.com and 13 external pages.

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

• 3 pages without a meta description

  /contact-us, /resource-center and /news have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (3)

• 8 pages without an H1

  /resource-center, /sponsors-cros, /sites, /services/site-network, /services/decentralized-clinical-trials and /services/recruitment-engagement and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 1 broken image

  1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=138004327&tm=gtm002&Ver=2&mid=2306f256-8198-46fb-a43b-d20777387a71&bo=1&sid=2f2d5e30d7e011f1a41aab3daffd4dd7&vid=2f2d4dc0d7e011f192b5e3f323d91410&vids=1&msclkid=N&pi=9.

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

• No Content-Security-Policy

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

• No clickjacking protection

  Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

• No X-Content-Type-Options

  X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

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

• No CAA record

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

  elligo.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 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 street address 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.

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

  The homepage carries about 828 words of visible text.

• No DMARC policy

  elligo.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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

• 7 trackers load before any consent

  7

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

• 17 cookies set on arrival

  17

  Opening the homepage sets 17 cookies, 3 of them by other companies (measured from a US location before any click).

• 32 other companies contacted

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