Website review, no card needed
electra.co.il website review
Visit site (opens in a new tab)Reviewed 18 November 202641 issues · 88 checks
This review found 41 issues worth fixing on electra.co.il, 18 of them high impact, across 88 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.1 s |
| Nov 14, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 175 ms |
| Jun 6, 2026 | 179 ms |
| Jun 13, 2026 | 184 ms |
| Jun 20, 2026 | 184 ms |
| Jun 27, 2026 | 185 ms |
| Jul 4, 2026 | 183 ms |
| Jul 11, 2026 | 182 ms |
| Jul 18, 2026 | 183 ms |
| Jul 25, 2026 | 180 ms |
| Aug 1, 2026 | 190 ms |
| Aug 8, 2026 | 190 ms |
| Aug 15, 2026 | 193 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 193 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 164 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 160 ms |
| Oct 31, 2026 | 157 ms |
| Nov 7, 2026 | 155 ms |
| Nov 14, 2026 | 155 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
1.9 s
2.9 s
3.9 s
4.8 s
5.8 s
6.8 s
7.7 s
Speed
Improve image delivery
20.4 s · 4.9 MB22 images could be 4.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 20.4 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
460 ms · 457 KiBAbout 457 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 626 KiB15 files are served with short cache lifetimes, so returning visitors download them again (626 KiB).
Render-blocking requests
500 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Minify JavaScript
300 ms · 53 KiB53 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 176 ms
176 msGoogle Tag Manager costs a phone 176 ms of main-thread work and 447 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, purple-lens.com and Facebook and others), adding 939 KiB and 447 ms of main-thread time.
Reduce unused CSS
150 ms · 35 KiBAbout 35 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 111 ms. During a long task the page ignores taps.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 581 ms of it running JavaScript. That is comfortably low.
Server response: 174 ms
174 msYour server sent the HTML in 174 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 25.4 s
25.4 sYour largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 25.4 s
25.4 sThe page becomes fully interactive after 25.4 s. Good is under 3.8 s.
Speed Index: 14.9 s
14.9 sVisually, the page fills in at 14.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.508
0.508The layout shifts by 0.508 while loading, so content jumps under the reader's thumb. Good is under 0.1.
35 images without width and height
35 images have no width and height attributes, so the layout jumps as each one loads.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 93 ms
93 msReal visitors wait 93 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 491 ms
491 msReal visitors wait 491 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 175 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 105 ms
105 msScripts block the page for only 105 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 20.0 MB in 135 requests
20.0 MBYour homepage downloads 20.0 MB in 135 requests on a phone: media 10.3 MB (1), images 8.2 MB (72) and scripts 1.1 MB (40). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 5.2 MB together. On a phone connection a single image that size takes seconds.
13 images in older formats
13 images (7.2 MB) 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.
10 images below the first screen load straight away
10 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
398 KiB2 images are downloaded at several times the size a phone draws them, for example 1583074629705-0.png at 1,350 px wide, shown at 107 px. Resized copies would save about 398 KiB.
About 5.7 g of CO₂ per visit
5.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.66 g of CO₂e: 679.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Orphan list items
Some list items are not inside a list.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (4 elements)
Form elements should have a visible label: 4 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
58 internal links, 45 external
The homepage links to 58 pages on electra.co.il and 45 external pages.
6 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “חברה מובילה במתן מענה לכל השלבים והתחומים במחזור החיים של פרויקטים למבנים, מתקנים ומערכות אלקטרו-מכניות החל משלב הייזום…”.
One H1 headline
Your main headline reads: “ליזום, להקים ולתפעל”.
Title: 31 characters
Your title is a healthy 31 characters: “קבוצת אלקטרה | ELECTRA | אלקטרה”.
Canonical URL set
The canonical URL is https://www.electra.co.il/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.electra.co.il/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no https://www.electra.co.il/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.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
1 linked page is broken
Your homepage links to https://www.electra.co.il/%D7%A2%D7%9C_%D7%94%D7%A7%D7%91%D7%95%D7%A6%D7%94, which answers with an error. Visitors hit a dead end and search engines drop it.
12 pages share a meta description
https://www.electra.co.il/sitemap and https://www.electra.co.il/%D7%AA%D7%97%D7%95%D7%9E%D7%99_%D7%A4%D7%A2%D7%99%D7%9C%D7%95%D7%AA use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.electra.co.il/%D7%AA%D7%97%D7%95%D7%9E%D7%99_%D7%A4%D7%A2%D7%99%D7%9C%D7%95%D7%AA, whose canonical is https://www.electra.co.il/%D7%AA%D7%97%D7%95%D7%9E%D7%99%20%D7%94%D7%A4%D7%A2%D7%99%D7%9C%D7%95%D7%AA. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages with very little text
https://www.electra.co.il/%D7%A6%D7%95%D7%A8_%D7%A7%D7%A9%D7%A8, https://www.electra.co.il/%D7%A2%D7%9C_%D7%94%D7%A7%D7%91%D7%95%D7%A6%D7%94/%D7%9E%D7%99_%D7%90%D7%A0%D7%97%D7%A0%D7%95, https://www.electra.co.il/%D7%A2%D7%9C_%D7%94%D7%A7%D7%91%D7%95%D7%A6%D7%94/%D7%97%D7%96%D7%95%D7%9F, https://www.electra.co.il/%D7%A2%D7%9C_%D7%94%D7%A7%D7%91%D7%95%D7%A6%D7%94/%D7%94%D7%A0%D7%94%D7%9C%D7%94_%D7%A8%D7%90%D7%A9%D7%99%D7%AA, https://www.electra.co.il/%D7%A2%D7%9C_%D7%94%D7%A7%D7%91%D7%95%D7%A6%D7%94/%D7%90%D7%91%D7%A0%D7%99_%D7%93%D7%A8%D7%9A and https://www.electra.co.il/%D7%A2%D7%9C_%D7%94%D7%A7%D7%91%D7%95%D7%A6%D7%94/%D7%A2%D7%A8%D7%9B%D7%99_%D7%94%D7%9C%D7%99%D7%91%D7%94 and 7 others 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.
1 page slow to respond
https://www.electra.co.il/sitemap took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
5 checks passed
Every page has a meta description
All 14 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 26 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”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 24 words
The homepage has only about 24 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
2 short forms
2 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 1 of them by other companies (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.
14 other companies contacted
Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at electra.co.il, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Imperva
Company
- Headquarters
- Ramat Gan
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on electra.co.il, including 13 speed issues, 3 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.