hatcon.com website review

31 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

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

Your mobile performance score is 60 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

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

Google Tag Manager costs a phone 373 ms of main-thread work and 505 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 1,988 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google Tag Manager, Shopify and Google CDN and others), adding 799 KiB and 448 ms of main-thread time.

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

About 19 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

10 KiB could be saved by minifying CSS.

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

Desktop scores 92 but mobile only 60. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

2 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Tradition Of Excellence HATCON offers premier industrial …”.

The first text or image appears after 3.5 s on a phone. Good is under 1.8 s.

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

The layout shifts by 0.176 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Scripts block taps and scrolling for 263 ms in total while the page loads. Good is under 200 ms.

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

New_Project_cdfd828e-cdd1-4002-a914-9c84dbeb3304_1370x_1_170 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).

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

1 button has no accessible name, so screen readers announce just “button”.

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

ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 77 characters, so Google will cut it off around 60: “HATCON | Leading Industrial Solutions Provider in Saudi Arabia & GCC – Hatcon”.

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 148 pages on hatcon.com and 6 external pages.

/collections/machine-and-equipment-division and /collections/architectural-division have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 links to other sites are dead, for example https://twitter.com/hatcon81 (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.facebook.com/pages/Hajjan-Trading-and-Industrial-Services-Co-Ltd/1494541347472500.

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.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 1,145 words of visible text.

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 Ads, Google Analytics, Google Tag Manager 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.

Opening the homepage sets 11 cookies (measured from a US location before any click).

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.

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