ide-tech.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: 6.3 s

  6.3 s

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

• Real-user FCP: 5.6 s

  5.6 s

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

• Real-user TTFB: 4.3 s

  4.3 s

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

• Largest content (LCP) got 30% slower for real visitors

  +30%

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

• 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 113 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 5.7 MB

  5.7 MB

  Your homepage downloads 5.7 MB on a phone, 4.0 MB of it images (70%). Under 2 MB keeps phones on slow connections fast.

• 5 images far larger than shown

  1.1 MB

  5 images are downloaded at several times the size a phone draws them, for example shutterstock_609092363-scaled.jpg at 2,560 px wide, shown at 306 px. Resized copies would save about 1.1 MB.

  Elements (5)

• 16 images below the first screen load straight away

  16 images further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• About 1.6 g of CO₂ per visit

  1.62 g

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

• 15 buttons without a name

  15 buttons have no accessible name, so screen readers announce just “button”.

  Elements (3)

• 8 tap targets too small

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

  Elements (3)

• 6 text elements with low contrast

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

  Elements (3)

• Interactive controls must not be nested (2 elements)

  Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  Elements (2)

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

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

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

  Elements (3)

• No main landmark

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

  Elements (1)

• Zoom is disabled

  The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  Elements (1)

• 41 links without text

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

  Elements (3)

• 1 form field without a label

  1 form field has no label, so screen readers announce an empty box and autofill guesses.

  View source

• ARIA role should be appropriate for the element (2 elements)

  ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  Elements (2)

• Elements marked as presentational should be consistently ignored (2 elements)

  Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  Elements (2)

• No social preview image

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

  View source

• 100 internal links, 2 external

  The homepage links to 100 pages on ide-tech.com and 2 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.

  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.

• 2 pages slow to respond

  /en/water-solutions/sea-water-desalination and /en/water-solutions/sea-water-desalination/intake-and-outfall-systems took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 4 small tap targets

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

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• No HSTS header

  No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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

• DNSSEC is off

  ide-tech.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 direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

  The homepage carries about 794 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be ide-tech.com is still delivered. Reports are on, so moving to quarantine is the next step.

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

• 7 trackers load before any consent

  7

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

• 18 cookies set on arrival

  18

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

• 45 other companies contacted

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