embitel.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: 5.1 s

  5.1 s

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

• Real-user FCP: 4.6 s

  4.6 s

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

• Real-user TTFB: 2.9 s

  2.9 s

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

• Tap response (INP) held steady for real visitors

  +1%

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

• Largest content (LCP) held steady for real visitors

  +8%

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

• 1 image far larger than shown

  27 KiB

  1 image is downloaded at several times the size a phone draws it, for example section-2-slide-2.webp at 1,408 px wide, shown at 342 px. Resized copies would save about 27 KiB.

  Elements (1)

• 2 images below the first screen load straight away

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

  Elements (2)

• About 0.5 g of CO₂ per visit

  0.53 g

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

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  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)

• 6 form fields without a label

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

• 5 links without text

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

  Elements (3)

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

  Elements (2)

• Headings skip levels

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

  Elements (1)

• Title is long (76 characters)

  Your title is 76 characters, so Google will cut it off around 60: “Product Engineering Services | IoT Solutions | Digital Commerce & Experience”.

  View source

• Meta description is long (258 characters)

  Your meta description is 258 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• No social preview image

  No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  View source

• 291 internal links, 6 external

  The homepage links to 291 pages on embitel.com and 6 external pages.

• 15 internal pages checked

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

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://embitel.com/wp-content/themes/astra/assets/css/minified/main.min.css' from origin …”.

• 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

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

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

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

  The homepage carries about 274 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be embitel.com is still delivered. Add a report address, check the reports, then move to quarantine.

• Email authentication score: 75/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 LinkedIn Insight (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.

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

• 17 other companies contacted

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