incora.com website review

7 images could be 863 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

About 65 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

A phone's processor spends 2.0 s on main-thread work while loading, 575 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

3 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and Google Fonts), adding 235 KiB and 147 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

4 long tasks block the main thread while loading, the longest for 104 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 files are served with short cache lifetimes, so returning visitors download them again (2 KiB).

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Incora_Edited_Images_DSC07574”.

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

The page becomes fully interactive after 6.5 s. Good is under 3.8 s.

35 images have no width and height attributes, so the layout jumps as each one loads.

Visually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.

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

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

Incora_Website_Edited_Images_DSC07281_2500x1667-767x511.jpg 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).

6 images (371 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

[role="img"] and [role="image"] elements must have alternative text: 16 elements on the page fail this check, rated serious by axe-core.

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

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

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.

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

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

There are 4 <h1> headlines (“We Simplifythe Complex”, “Temperature Controlled, Traceable Storage” and “Authorized Distributor of Critical Aerospace Hard…”). One clear main headline is easier for people and search engines.

There is no robots.txt at incora.com/robots.txt, the first file search crawlers ask for.

The homepage links to 89 pages on incora.com and 6 external pages.

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.

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.

/about-us, /about-us/executive-leadership and /markets/aerospace have no meta description, so Google writes the search snippet from whatever text it finds.

/markets and /products use the same meta description. A description written for each page earns more clicks.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 728 words of visible text.

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

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.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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