codiant.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.5 s

  4.5 s

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

• Real-user FCP: 4.0 s

  4.0 s

  Real visitors see the first content after 4.0 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.

• Real-user CLS: 0.12

  0.12

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

• Tap response (INP) held steady for real visitors

  +8%

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

• Largest content (LCP) held steady for real visitors

  -6%

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

• Page weight: 3.3 MB

  3.3 MB

  Your homepage downloads 3.3 MB on a phone, 1.5 MB of it images (44%). Under 2 MB keeps phones on slow connections fast.

• 9 images below the first screen load straight away

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

  Elements (5)

• 8 images far larger than shown

  404 KiB

  8 images are downloaded at several times the size a phone draws them, for example Calcounts-e3e1746199ae74b735a5ab9432196a2d.webp at 2,964 px wide, shown at 389 px. Resized copies would save about 404 KiB.

  Elements (5)

• About 0.9 g of CO₂ per visit

  0.94 g

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

• 3 text elements with low contrast

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

  Elements (3)

• Scrollable region must have keyboard access (1 element)

  Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• 11 form fields without a label

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

  View source

• Users should be able to zoom and scale the text up to 500% (1 element)

  Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

  Elements (1)

• Headings skip levels

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

  View sourceElements (1)

• 274 internal links, 23 external

  The homepage links to 274 pages on codiant.com and 23 external pages.

• 15 internal pages checked

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

• 10 small tap targets

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

• HTTP/1.1 only

  The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

• No X-Content-Type-Options

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

• No security.txt

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

• No CAA record

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

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

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

  View source

• No opening hours

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

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• About 1,243 words of copy

  The homepage carries about 1,243 words of visible text.

• Email authentication score: 85/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.

• 3 cookies set on arrival

  3

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

• 7 other companies contacted

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