magalcom.com website review

About 953 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.5 s faster on a phone.

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

About 377 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.

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

6 third-party services load with your homepage (Google CDN, Google Tag Manager and enable.co.il and others), adding 1.6 MB and 710 ms of main-thread time.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).

Google CDN costs a phone 360 ms of main-thread work and 733 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.

Google Tag Manager costs a phone 267 ms of main-thread work and 566 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.

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

12 long tasks block the main thread while loading, the longest for 146 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.

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 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

Your homepage downloads 3.3 MB in 137 requests on a phone: scripts 2.0 MB (83), stylesheets 409 KiB (20) and other files 355 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

3 images have no alt text, which hurts accessibility and image search.

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

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

Some list items are not inside a list.

Elements with role="dialog" or role="alertdialog" do not have accessible names. (2 elements).

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 56 pages on magalcom.com and 1 external page.

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 https://magalcom.com/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.

Your homepage links to https://magalcom.com/about-us/jobs, https://magalcom.com/solutions-2, https://magalcom.com/solutions-2/data-center, https://magalcom.com/solutions-2/control-rooms, https://magalcom.com/solutions-2/communication-infrastructure and https://magalcom.com/solutions-2/security-systems and 4 others, which answer with an error. Visitors hit a dead end and search engines drop them.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://magalcom.com/%d7%94%d7%a6%d7%94%d7%a8%d7%aa-%d7%a0%d7%92%d7%99%d7%a9%d7%95%d7%aa, whose canonical is https://magalcom.com/%D7%94%D7%A6%D7%94%D7%A8%D7%AA-%D7%A0%D7%92%D7%99%D7%A9%D7%95%D7%AA. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://magalcom.com/privacy, https://magalcom.com/about-us, https://magalcom.com/about-us/companys-advantages-2, https://magalcom.com/about-us/partners-2 and https://magalcom.com/%d7%94%d7%a6%d7%94%d7%a8%d7%aa-%d7%a0%d7%92%d7%99%d7%a9%d7%95%d7%aa have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.

2 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Mixed content”).

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 172 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

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.