Website review, no card needed
ynet.co.il website review
Visit site (opens in a new tab)Reviewed 12 October 202657 issues · 99 checks
This review found 57 issues worth fixing on ynet.co.il, 31 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 3.1 s |
| Apr 25, 2026 | 3.1 s |
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 331 ms |
| Apr 25, 2026 | 329 ms |
| May 2, 2026 | 327 ms |
| May 9, 2026 | 321 ms |
| May 16, 2026 | 314 ms |
| May 23, 2026 | 312 ms |
| May 30, 2026 | 313 ms |
| Jun 6, 2026 | 318 ms |
| Jun 13, 2026 | 318 ms |
| Jun 20, 2026 | 313 ms |
| Jun 27, 2026 | 312 ms |
| Jul 4, 2026 | 311 ms |
| Jul 11, 2026 | 309 ms |
| Jul 18, 2026 | 311 ms |
| Jul 25, 2026 | 311 ms |
| Aug 1, 2026 | 309 ms |
| Aug 8, 2026 | 308 ms |
| Aug 15, 2026 | 302 ms |
| Aug 22, 2026 | 294 ms |
| Aug 29, 2026 | 287 ms |
| Sep 5, 2026 | 280 ms |
| Sep 12, 2026 | 280 ms |
| Sep 19, 2026 | 280 ms |
| Sep 26, 2026 | 284 ms |
| Oct 3, 2026 | 289 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
Speed
Reduce unused JavaScript
10.6 s · 4.0 MBAbout 4.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.6 s faster on a phone.
Render-blocking requests
8.3 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.3 s.
Use efficient cache lifetimes
2.9 s · 5.0 MB136 files are served with short cache lifetimes, so returning visitors download them again (5.0 MB).
Minify JavaScript
3.6 s · 703 KiB703 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 1.8 s
1.8 sGoogle Tag Manager costs a phone 1.8 s of main-thread work and 1.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 18.3 s
A phone's processor spends 18.3 s on main-thread work while loading, 7.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 6
6/100Your mobile performance score is 6. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,899 HTML elements
The page has 5,899 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, yit.co.il and Google/Doubleclick Ads and others), adding 14.2 MB and 5.3 s of main-thread time.
Improve image delivery
150 ms · 1.7 MB59 images could be 1.7 MB 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.
yit.co.il adds 875 ms
875 msyit.co.il costs a phone 875 ms of main-thread work and 8.6 MB 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 adds 638 ms
638 msGoogle/Doubleclick Ads costs a phone 638 ms of main-thread work and 889 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.
Taboola adds 510 ms
510 msTaboola costs a phone 510 ms of main-thread work and 1.3 MB 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.
Other Google APIs/SDKs adds 458 ms
458 msOther Google APIs/SDKs costs a phone 458 ms of main-thread work and 743 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 on the main thread
20 long tasks block the main thread while loading, the longest for 396 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 81 KiBPolyfills for old browsers add 81 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page.
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.
1 checks passed
Server response: 50 ms
50 msYour server sent the HTML in 50 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user CLS: 0.49
0.49For real visitors the layout shifts by 0.49 (75th percentile). Good is under 0.1.
First Contentful Paint: 11.2 s
11.2 sThe first text or image appears after 11.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 35.9 s
35.9 sYour largest element takes 35.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “תיעוד התקיפה בשדה התעופה בריאד”.
Speed Index: 30.8 s
30.8 sVisually, the page fills in at 30.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 92.2 s
92.2 sThe page becomes fully interactive after 92.2 s. Good is under 3.8 s.
Total Blocking Time: 3.7 s
3.7 sScripts block taps and scrolling for 3.7 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.431
0.431The layout shifts by 0.431 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 344 ms
344 msReal visitors wait 344 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
5 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 337 ms
337 msReal visitors wait 337 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 331 ms to 289 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 19.6 MB in 1,078 requests
19.6 MBYour homepage downloads 19.6 MB in 1,078 requests on a phone: images 9.5 MB (439), scripts 7.8 MB (115) and HTML 797 KiB (93). Under 2 MB keeps phones on slow connections fast.
10 images far larger than shown
668 KiB10 images are downloaded at several times the size a phone draws them, for example B1zISItjGg_0_0_425_240_0_medium.gif at 425 px wide, shown at 131 px. Resized copies would save about 668 KiB.
40 images below the first screen load straight away
40 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
12 images in older formats
12 images (491 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.
About 5.6 g of CO₂ per visit
5.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.56 g of CO₂e: 667.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
237 text elements with low contrast
237 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 buttons without a name
5 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
104 elements hidden from screen readers can still receive keyboard focus.
ARIA roles used must conform to valid values (1 element)
ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
15 images without alt text
15 images have no alt text, which hurts accessibility and image search.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
All page content should be contained by landmarks (368 elements)
All page content should be contained by landmarks: 368 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
62 links without text
62 visible links have no text or label, so screen readers cannot say where they go.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (27 elements).
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (10 elements).
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 13 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
296 internal links, 80 external
The homepage links to 296 pages on ynet.co.il and 80 external pages.
8 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “אתר החדשות המוביל בישראל מבית ידיעות אחרונות. סיקור מלא של חדשות מישראל והעולם, ספורט, כלכלה, תרבות, אוכל, מדע וטבע, כל…”.
One H1 headline
Your main headline reads: “ישראל תתקוף בתימן? שיחת האמריקנים עם הרמטכ"ל, אזהרתו - ורגע הפגיעה בנמל התעופה”.
Title: 65 characters
Your title is a healthy 65 characters: “ynet - חדשות, כלכלה, ספורט ובריאות - דיווחים שוטפים מהארץ ומהעולם”.
Canonical URL set
The canonical URL is https://www.ynet.co.il/home/0,7340,L-8,00.html.
Structured data in place
Structured data found: Organization and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.ynet.co.il/iphone/json/api/20m/google_site_map/8-2-3-6-538-1208-550-544-4003.
AI search readiness
Most text only appears after JavaScript runs
25%A phone browser shows 597 words, but the HTML your server sends has only 152. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No llms.txt
There is no https://www.ynet.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.
2 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
1 page without a title
https://www.ynet.co.il/home/0,7340,L-201,00.html has no <title>, so Google invents the link text in results.
3 pages without a meta description
https://www.ynet.co.il/redmail, https://www.ynet.co.il/home/0,7340,L-201,00.html and https://www.ynet.co.il/plus have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.ynet.co.il/redmail, https://www.ynet.co.il/home/0,7340,L-201,00.html, https://www.ynet.co.il/plus and https://www.ynet.co.il/radio have no <h1> headline, so visitors and search engines get no clear main topic.
12 pages with very little text
https://www.ynet.co.il/redmail, https://www.ynet.co.il/news, https://www.ynet.co.il/news/elections2026, https://www.ynet.co.il/plus, https://www.ynet.co.il/economy and https://www.ynet.co.il/sport and 6 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 152 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
89 small tap targets
89 of 111 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
42 third-party cookies
42 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “[GPT] Invalid arguments: googletag.display(''). https://goo.gle/gpt-message#96”.
12 distorted images
12 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 597 words of copy
The homepage carries about 597 words of visible text.
2 checks passed
Social proof on the page
Social proof on the homepage: 24 testimonial or review blocks, 3 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Cloudflare Web Analytics.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 2 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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies, 2 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.
61 other companies contacted
Loading the homepage contacts 61 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 ynet.co.il, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on ynet.co.il, including 24 speed issues, 1 SEO issue and 3 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.