Tools & Wizards About Us
nafsha.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

nafsha.com

הדרכת הורים: נָפְשַׁא היא ארגון המעניק טיפול משפחתי מקיף בשיטת ReachingOut

Page Load Speed

6.7 sec in total

First Response

574 ms

Resources Loaded

4.7 sec

Page Rendered

1.4 sec

nafsha.com screenshot

About Website

Click here to check amazing Nafsha content. Otherwise, check out these important facts you probably never knew about nafsha.com

מחפשים הדרכת הורים? נפשא היא ארגון מטפלים המציע מערך טיפולים מקיף הכולל טיפול משפחתי, מפגשים פרטניים וזמינות טלפונית מלאה.

Visit nafsha.com

Key Findings

We analyzed Nafsha.com page load time and found that the first response time was 574 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

nafsha.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value550 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

nafsha.com

574 ms

css

128 ms

ae2ab14122ff3caa140c5f9bc0dadf41.css

305 ms

jquery.min.js

1582 ms

lazyload.min.js

1535 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 62% of them (23 requests) were addressed to the original Nafsha.com, 35% (13 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Nafsha.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.6 kB (11%)

Content Size

630.7 kB

After Optimization

562.1 kB

  • HTML
  • Images

In fact, the total size of Nafsha.com main page is 630.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 546.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 68.6 kB

  • Original 84.0 kB
  • After minification 79.9 kB
  • After compression 15.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 68.6 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 13 B

  • Original 546.6 kB
  • After minification 546.6 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Nafsha images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nafsha. According to our analytics all requests are already optimized.

Network Requests Diagram

nafsha.com

nafsha.com

574 ms

css

css

128 ms

ae2ab14122ff3caa140c5f9bc0dadf41.css

ae2ab14122ff3caa140c5f9bc0dadf41.css

305 ms

jquery.min.js

jquery.min.js

1582 ms

lazyload.min.js

lazyload.min.js

1535 ms

80f487ea56390ad959af6c05bc301433.js

80f487ea56390ad959af6c05bc301433.js

1789 ms

homepage_100_nafsha6.jpg

homepage_100_nafsha6.jpg

899 ms

homepage_button_blue1.gif

homepage_button_blue1.gif

822 ms

homepage_button_green1.gif

homepage_button_green1.gif

822 ms

homepage_button_white1.gif

homepage_button_white1.gif

901 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EVyusd0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EVyusd0mj.ttf

183 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Ebiusd0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Ebiusd0mj.ttf

344 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSusd0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSusd0mj.ttf

339 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EICusd0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EICusd0mj.ttf

239 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyysd0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyysd0mj.ttf

341 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysd0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysd0mj.ttf

328 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yysd0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yysd0mj.ttf

340 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSysd0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSysd0mj.ttf

340 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiS2sd0mj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiS2sd0mj.ttf

374 ms

yiddishkeit-bold-fm.ttf

yiddishkeit-bold-fm.ttf

339 ms

fa-solid-900.woff

fa-solid-900.woff

632 ms

fa-solid-900.woff

fa-solid-900.woff

338 ms

fa-regular-400.woff

fa-regular-400.woff

338 ms

fa-brands-400.woff

fa-brands-400.woff

632 ms

fa-brands-400.woff

fa-brands-400.woff

610 ms

OpenSansHebrew-Regular.woff

OpenSansHebrew-Regular.woff

630 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

341 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

342 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

341 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

339 ms

LOGO.png

LOGO.png

569 ms

%D7%9E%D7%99-%D7%90%D7%A0%D7%97%D7%A0%D7%95-1.png

%D7%9E%D7%99-%D7%90%D7%A0%D7%97%D7%A0%D7%95-1.png

551 ms

homepage_2235-768x1224.jpg

homepage_2235-768x1224.jpg

805 ms

%D7%9C%D7%9E%D7%94-%D7%90%D7%A0%D7%97%D7%A0%D7%95-2-1.png

%D7%9C%D7%9E%D7%94-%D7%90%D7%A0%D7%97%D7%A0%D7%95-2-1.png

590 ms

homepage43-n0167.jpg

homepage43-n0167.jpg

591 ms

title_20N.png

title_20N.png

583 ms

homepage_4N.jpg

homepage_4N.jpg

592 ms

Accessibility Review

nafsha.com accessibility score

93

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

nafsha.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

nafsha.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    IW

  • Language Claimed

    HE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nafsha.com can be misinterpreted by Google and other search engines. Our service has detected that Hebrew is used on the page, and it does not match the claimed language. Our system also found out that Nafsha.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

nafsha.com

Open Graph data is detected on the main page of Nafsha. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: