emircom.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 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 LCP: 3.4 s

  3.4 s

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

• Tap response (INP) got 20% slower for real visitors

  +20%

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

• Real-user FCP: 2.8 s

  2.8 s

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

• An image on the first screen is lazy-loaded

  motion-blur-of-train-moving-inside-tunnel-in-tokyo-2026-03-1 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)

• 2 images far larger than shown

  63 KiB

  2 images are downloaded at several times the size a phone draws them, for example 1a8393b0b83e4db5af6925a99a5ccfbf_a0e199161f3c48a96b7b375d5cd at 1,600 px wide, shown at 358 px. Resized copies would save about 63 KiB.

  Elements (2)

• 1 image below the first screen load straight away

  1 image further down the page (77 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  Elements (1)

• About 0.5 g of CO₂ per visit

  0.46 g

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

• Malformed lists

  Some lists contain elements other than list items, which screen readers announce wrongly.

  Elements (1)

• All page content should be contained by landmarks (2 elements)

  All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  Elements (2)

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

• 11 links without text

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

  Elements (3)

• Headings should not be empty (5 elements)

  Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Headings skip levels

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

  View sourceElements (2)

• No social preview image

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

  View source

• No XML sitemap

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

• 83 internal links, 6 external

  The homepage links to 83 pages on emircom.com and 6 external pages.

• Organization data is thin (3 of 6 facts)

  Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  View source

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

• 7 pages slow to respond

  /solutions, /services/network, /services/collaboration, /services/av-solutions, /services/it-asset-management and /services/customer-success and 1 other took over 3 s to send their HTML from our server.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 24 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 “Connecting to 'https://stats.g.doubleclick.net/g/collect?v=2&ngs=1&ibt=1&tid=G-R4Z29M27YD&cid=1926758878.1793183032&gtm…”.

• No security.txt

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

• DNSSEC is off

  emircom.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 639 words of copy

  The homepage carries about 639 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.

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

• 4 cookies set on arrival

  4

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