4.6 sec in total
538 ms
3.4 sec
738 ms
Welcome to ozenbar.com homepage info - get ready to check Ozen Bar best content for Israel right away, or after learning these important things about ozenbar.com
,מועדון ה”אוזןבר”, מקבוצת האוזן השלישית,קולנוע, הופעות ובר,בית קפה
Visit ozenbar.comWe analyzed Ozenbar.com page load time and found that the first response time was 538 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ozenbar.com performance score
name
value
score
weighting
Value2.9 s
55/100
10%
Value16.8 s
0/100
25%
Value4.2 s
77/100
10%
Value140 ms
95/100
30%
Value0.799
5/100
15%
Value8.4 s
38/100
10%
538 ms
15 ms
91 ms
167 ms
168 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 56% of them (68 requests) were addressed to the original Ozenbar.com, 15% (18 requests) were made to Google.com and 10% (12 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ozenbar.com.
Page size can be reduced by 1.1 MB (18%)
5.8 MB
4.8 MB
In fact, the total size of Ozenbar.com main page is 5.8 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. 70% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 99.1 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. This page needs HTML code to be minified as it can gain 14.9 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 99.1 kB or 85% of the original size.
Potential reduce by 94.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. Ozen Bar images are well optimized though.
Potential reduce by 747.8 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 747.8 kB or 70% of the original size.
Potential reduce by 112.0 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. Ozenbar.com needs all CSS files to be minified and compressed as it can save up to 112.0 kB or 76% of the original size.
Number of requests can be reduced by 47 (42%)
113
66
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ozen Bar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.ozenbar.com
538 ms
jquery.min.js
15 ms
placeholder.js
91 ms
browser-selector.js
167 ms
responsiveslides.min.js
168 ms
owl.carousel.js
270 ms
shadowbox.js
269 ms
scripts.js
184 ms
responsive-calendar.js
534 ms
style.css
251 ms
k_css.css
249 ms
owl.carousel.css
279 ms
responsive-calendar.css
332 ms
responsive.css
332 ms
shadowbox.css
355 ms
styles.css
354 ms
styles-rtl.css
357 ms
css
43 ms
genericons.css
495 ms
style.css
413 ms
jquery.js
549 ms
jquery-migrate.min.js
441 ms
rtl.css
443 ms
tw-sack.min.js
494 ms
js
58 ms
backgroundVideo.min.js
213 ms
parallax.min.js
545 ms
jquery.form.min.js
564 ms
scripts.js
582 ms
skip-link-focus-fix.js
582 ms
comment-reply.min.js
628 ms
functions.js
627 ms
wp-emoji-release.min.js
191 ms
mob-f-icon.png
291 ms
img.jpg
860 ms
banner-txt.png
290 ms
star-icon.png
289 ms
inner_header_bg.png
290 ms
banner-txt.png
291 ms
inner_logo.png
430 ms
simple-smile.png
426 ms
star-icon1.png
429 ms
%D7%AA%D7%9E%D7%95%D7%A0%D7%AA-%D7%99%D7%97%D7%A6-%D7%A7%D7%A9%D7%A8-%D7%9C%D7%90%D7%97%D7%93-%D7%A8%D7%95%D7%99%D7%98%D7%9C-%D7%98%D7%95%D7%A4%D7%99%D7%95%D7%9C-%D7%9C%D7%90%D7%AA%D7%A8.jpg
911 ms
bowie.jpg
1368 ms
0a243dde-3d43-4f4e-8de0-7443751819f2.jpg
896 ms
footer-fb.png
660 ms
footer-instagram.png
661 ms
footer-youtube.png
857 ms
footer-tw.png
858 ms
eventiko.png
1105 ms
footer-logo2.jpg
1013 ms
footer-logo1.jpg
1014 ms
calender-bg.png
1405 ms
pop_down.png
998 ms
calender-icon.png
1131 ms
calender-dots.png
1124 ms
calender-dots2.png
1132 ms
news-bg.jpg
1145 ms
twitter-icon.png
1166 ms
facebook-icon.png
1174 ms
instagram-icon.png
1175 ms
youtube-icon.png
1231 ms
%D7%9B%D7%95%D7%A1%D7%95%D7%AA1.jpg
1245 ms
caffe-img.png
1965 ms
home-page-address-bg.png
1358 ms
almoni-dl-aaa-400.ttf
1405 ms
common.js
113 ms
map.js
227 ms
util.js
234 ms
marker.js
232 ms
analytics.js
223 ms
rnLNibKcVA.jpg
1116 ms
almoni-dl-aaa-700.ttf
1198 ms
MCSuchnM0R.jpg
1109 ms
jjEsvnk8X1.jpg
1032 ms
dots-img.png
1296 ms
dots2-img.png
1189 ms
AB6A9084-as-Smart-Object-1-%D7%9C%D7%90%D7%AA%D7%A8.jpg
1357 ms
ajax-loader.gif
1217 ms
openhand_8_8.cur
100 ms
master
185 ms
collect
70 ms
ViewportInfoService.GetViewportInfo
128 ms
stats.js
48 ms
controls.js
37 ms
collect
232 ms
transparent.png
178 ms
css
392 ms
widgets.js
144 ms
map_pin.png
993 ms
google4.png
279 ms
mapcnt6.png
278 ms
sv5.png
382 ms
tmapctrl.png
354 ms
cb_scout5.png
377 ms
tmapctrl4.png
368 ms
imgs8.png
374 ms
widget
216 ms
vt
197 ms
vt
290 ms
vt
221 ms
vt
290 ms
vt
224 ms
vt
224 ms
vt
288 ms
vt
248 ms
vt
321 ms
vt
320 ms
vt
288 ms
vt
322 ms
vt
334 ms
vt
321 ms
vt
332 ms
vt
327 ms
signed_in_api_icons2.png
59 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
73 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
87 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
130 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
130 ms
white_google_icon.png
44 ms
AuthenticationService.Authenticate
49 ms
ozenbar.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ozenbar.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
ozenbar.com 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 uses legible font sizes
IW
HE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozenbar.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 Ozenbar.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.
ozenbar.com
Open Graph description is not detected on the main page of Ozen Bar. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: