4.6 sec in total
265 ms
4.1 sec
213 ms
Welcome to fitlife.co.il homepage info - get ready to check Fitlife best content for Israel right away, or after learning these important things about fitlife.co.il
חיים בכושר הוא מגזין בריאות כושר ותזונה שמטרתו להביא לקהל הקוראים מידע מהימן ומדוייק בתחומים שונים כגון: דיאטה וירידה במשקל, כושר, בריאות תוספי תזונה ועוד
Visit fitlife.co.ilWe analyzed Fitlife.co.il page load time and found that the first response time was 265 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fitlife.co.il performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value6.0 s
13/100
25%
Value6.7 s
36/100
10%
Value670 ms
44/100
30%
Value0.055
98/100
15%
Value13.3 s
12/100
10%
265 ms
494 ms
985 ms
450 ms
338 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 88% of them (82 requests) were addressed to the original Fitlife.co.il, 4% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fitlife.co.il.
Page size can be reduced by 195.9 kB (10%)
1.9 MB
1.7 MB
In fact, the total size of Fitlife.co.il main page is 1.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 893.0 kB which makes up the majority of the site volume.
Potential reduce by 190.6 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 190.6 kB or 76% of the original size.
Potential reduce by 1.4 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. Fitlife images are well optimized though.
Potential reduce by 1.5 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 2.5 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Fitlife.co.il has all CSS files already compressed.
Number of requests can be reduced by 66 (78%)
85
19
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fitlife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
fitlife.co.il
265 ms
fitlife.co.il
494 ms
www.fitlife.co.il
985 ms
style-rtl.min.css
450 ms
woocommerce-layout-rtl.css
338 ms
woocommerce-rtl.css
355 ms
sidebar-app.css
353 ms
css2
30 ms
style.css
475 ms
style.css
453 ms
rtl.css
471 ms
font-awesome.min.css
472 ms
css
46 ms
woocommerce.css
561 ms
jquery.min.js
675 ms
jquery-migrate.min.js
588 ms
jquery.blockUI.min.js
591 ms
add-to-cart.min.js
590 ms
js.cookie.min.js
672 ms
woocommerce.min.js
707 ms
scripts.js
708 ms
wc-blocks-rtl.css
654 ms
sourcebuster.min.js
672 ms
order-attribution.min.js
678 ms
wp-polyfill-inert.min.js
720 ms
regenerator-runtime.min.js
721 ms
wp-polyfill.min.js
723 ms
react.min.js
783 ms
hooks.min.js
785 ms
deprecated.min.js
829 ms
dom.min.js
833 ms
react-dom.min.js
914 ms
escape-html.min.js
921 ms
element.min.js
920 ms
is-shallow-equal.min.js
946 ms
i18n.min.js
950 ms
keycodes.min.js
960 ms
priority-queue.min.js
1005 ms
compose.min.js
1010 ms
private-apis.min.js
1064 ms
redux-routine.min.js
953 ms
data.min.js
860 ms
lodash.min.js
883 ms
wc-blocks-registry.js
894 ms
url.min.js
849 ms
api-fetch.min.js
851 ms
wc-settings.js
844 ms
data-controls.min.js
874 ms
html-entities.min.js
874 ms
notices.min.js
855 ms
wc-blocks-middleware.js
831 ms
wc-blocks-data.js
844 ms
dom-ready.min.js
869 ms
a11y.min.js
791 ms
primitives.min.js
846 ms
warning.min.js
831 ms
gtm.js
100 ms
blocks-components.js
792 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
16 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf
21 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf
33 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf
33 ms
blocks-checkout.js
805 ms
order-attribution-blocks.min.js
791 ms
gtm4wp-form-move-tracker.js
863 ms
moment.min.js
823 ms
date.min.js
836 ms
analytics.js
16 ms
rich-text.min.js
830 ms
collect
12 ms
components.min.js
1144 ms
plugins.min.js
872 ms
collect
27 ms
js
46 ms
sidebar-app.js
954 ms
comment-reply.min.js
857 ms
fontawesome-webfont.woff
877 ms
countrydistance_0458.jpg
1089 ms
%D7%9E%D7%A1%D7%90%D7%96.jpg
1024 ms
%D7%92%D7%91%D7%99%D7%A0%D7%94_%D7%A6%D7%A8%D7%A4%D7%AA%D7%99%D7%AA.jpg
1072 ms
%D7%90%D7%95%D7%9E%D7%92%D7%94_3.jpg
959 ms
%D7%92%D7%A8%D7%A3_%D7%A7%D7%A6%D7%91_%D7%9C%D7%91_%D7%A2%D7%9D_%D7%9C%D7%91.jpg
1077 ms
%D7%AA%D7%A8%D7%92%D7%99%D7%9C_%D7%9B%D7%95%D7%97_%D7%9C%D7%97%D7%99%D7%A6%D7%AA-%D7%A8%D7%92%D7%9C%D7%99%D7%99%D7%9D.jpg
1033 ms
%D7%A4%D7%A8%D7%97-%D7%99%D7%A1%D7%9E%D7%99%D7%9F.jpg
1036 ms
%D7%90%D7%A9%D7%9B%D7%95%D7%9C%D7%99%D7%AA.jpg
1063 ms
%D7%9C%D7%97%D7%99%D7%A6%D7%AA_%D7%97%D7%96%D7%94_%D7%91%D7%9E%D7%95%D7%98.jpg
1185 ms
%D7%9E%D7%95%D7%98_%D7%9E%D7%A9%D7%A7%D7%95%D7%9C%D7%95%D7%AA_%D7%A2%D7%9C_%D7%94%D7%9B%D7%AA%D7%A4%D7%99%D7%99%D7%9D.jpg
1068 ms
%D7%93%D7%99%D7%90%D7%98%D7%94_%D7%90%D7%95_%D7%A4%D7%A2%D7%99%D7%9C%D7%95%D7%AA-%D7%92%D7%95%D7%A4%D7%A0%D7%99%D7%AA.jpg
1019 ms
%D7%9E%D7%A8%D7%99%D7%9E%D7%99%D7%9D_%D7%92%D7%9C%D7%92%D7%9C.jpg
1151 ms
%D7%93%D7%95%D7%91%D7%93%D7%91%D7%A0%D7%99%D7%9D.jpg
1180 ms
%D7%99%D7%9C%D7%93%D7%94_%D7%A2%D7%9D_%D7%A2%D7%9C%D7%99_%D7%A1%D7%9C%D7%A7.jpg
1075 ms
placeholder-medium.png
1065 ms
woocommerce-smallscreen-rtl.css
120 ms
fitlife.co.il accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
fitlife.co.il best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fitlife.co.il SEO score
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
IW
HE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fitlife.co.il 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 Fitlife.co.il 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.
fitlife.co.il
Open Graph data is detected on the main page of Fitlife. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: