walla.co.il website review

Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Rubicon Project, Google Tag Manager and Google/Doubleclick Ads and others), adding 2.2 MB and 2.6 s of main-thread time.

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

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

About 754 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 492 ms of main-thread work and 637 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/Doubleclick Ads costs a phone 483 ms of main-thread work and 570 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.

Rubicon Project costs a phone 522 ms of main-thread work and 149 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.

Facebook costs a phone 346 ms of main-thread work and 409 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.

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

Pubmatic costs a phone 276 ms of main-thread work and 75 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.

3 images could be 28 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

7 KiB could be saved by minifying JavaScript.

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.

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

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

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

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 “פגישת טראמפ נתניהו”.

Real visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.

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

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

Your homepage downloads 4.0 MB in 1,145 requests on a phone: scripts 2.4 MB (126), other files 399 KiB (502) and fonts 395 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

All page content should be contained by landmarks: 88 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.

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

2 form fields have 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 120 pages on walla.co.il and 233 external pages.

The HTML your server sends has 175 of the 310 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.walla.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.

https://www.walla.co.il/entertainment/ontheagenda is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.walla.co.il/entertainment, https://www.walla.co.il/entertainment/moviesreview, https://www.walla.co.il/entertainment/music and https://www.walla.co.il/entertainment/ontheagenda all use the title “חדשות תרבות מהארץ והעולם, מוסיקה, טלוויזיה וקולנוע | וואלה תרבות”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.walla.co.il/news and https://www.walla.co.il/entertainment have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.walla.co.il/news, https://www.walla.co.il/news/breaking-news, https://www.walla.co.il/news/military, https://www.walla.co.il/news/israel, https://www.walla.co.il/news/politics and https://www.walla.co.il/news/world and 8 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.

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

1 image failed to load on a phone, for example https://sync.intentiq.com/profiles_engine/ProfilesEngineServlet?at=20&mi=10&secure=1&dpi=undefined&iiqidtype=2&iiqpcid=ae5d80e7-e9bc-4e96-b2c1-766a78ffb9d3&iiqpciddate=1793719107931&tsrnd=599_17937191.

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

27 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 310 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 4 mores (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 17 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 107 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.