13.5 sec in total
3.3 sec
9.8 sec
372 ms
Visit safari.in now to see the best up-to-date Safari content for India and also check out these interesting facts you probably never knew about safari.in
Have the best experience on online buying..
Visit safari.inWe analyzed Safari.in page load time and found that the first response time was 3.3 sec and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
safari.in performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value27.6 s
0/100
25%
Value13.7 s
2/100
10%
Value2,060 ms
7/100
30%
Value0.008
100/100
15%
Value20.9 s
1/100
10%
3349 ms
394 ms
398 ms
397 ms
400 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 96% of them (130 requests) were addressed to the original Safari.in, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to V2.zopim.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Safari.in.
Page size can be reduced by 1.1 MB (39%)
2.9 MB
1.8 MB
In fact, the total size of Safari.in main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 271.2 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 116.4 kB, which is 39% 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 271.2 kB or 92% of the original size.
Potential reduce by 89.1 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. Safari images are well optimized though.
Potential reduce by 498.6 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 498.6 kB or 76% of the original size.
Potential reduce by 280.4 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. Safari.in needs all CSS files to be minified and compressed as it can save up to 280.4 kB or 81% of the original size.
Number of requests can be reduced by 51 (38%)
133
82
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Safari. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
www.safari.in
3349 ms
styles.css
394 ms
widgets.css
398 ms
style.css
397 ms
amshopby.css
400 ms
slider.css
401 ms
jquery.fancybox.css
402 ms
jquery.fancybox-buttons.css
589 ms
jquery.fancybox-thumbs.css
590 ms
button.css
595 ms
button.css
599 ms
custommenu.css
601 ms
ajaxlogin.css
602 ms
custom.css
787 ms
custommenu.css
792 ms
responsive.css
794 ms
jquery.mCustomScrollbar.css
800 ms
responsive_custom.css
803 ms
allchanges.css
802 ms
override_a.css
982 ms
jquery.bxslider.css
983 ms
custom_s.css
994 ms
custom_a.css
1000 ms
custom_b.css
1209 ms
jquery.bxslider.css
1012 ms
jquery-1.7.2.min.js
1376 ms
jquery-noconflict.js
1219 ms
prototype.js
1437 ms
ccard.js
1240 ms
validation.js
1243 ms
builder.js
1409 ms
effects.js
1419 ms
dragdrop.js
1456 ms
controls.js
1458 ms
slider.js
1570 ms
js.js
1610 ms
form.js
1425 ms
menu.js
1251 ms
translate.js
1256 ms
cookies.js
1259 ms
slider.js
1376 ms
mycustom.validation.js
1422 ms
jquery.fancybox-1.3.4.js
1420 ms
custommenu.js
1256 ms
custom.min.js
1463 ms
analytics.js
25 ms
nav-blue.png
231 ms
logo.png
232 ms
sprite.png
228 ms
Traffik_white_board.jpg
1247 ms
4_Wheel_Trolley_3.jpg
1007 ms
BACKPACK_Banner_1.jpg
1246 ms
REVV_DUFFLE_Banner_2.jpg
1373 ms
EOSS_Red_600-x-400pix.jpg
1408 ms
4.jpg
1006 ms
new_safari_1.jpg
1247 ms
new_safari_2.jpg
1247 ms
new_safari_3.jpg
1375 ms
new_safari_4_1.jpg
1409 ms
concave-55-purple-2wh-2.jpg
1410 ms
concave-55-red-2wh-2.jpg
1413 ms
hexlite-plus-navy-blue-4wh-2.jpg
1569 ms
revv-55-brown-rdfl-2.jpg
1572 ms
quadra-55-purple-4wh-2.jpg
1606 ms
zinger-8-grey-backpack__1_.jpg
1609 ms
tierra-purple-rdfl-2.jpg
1608 ms
wave-55-purple-4wh-1.jpg
1610 ms
wave-55-brown-4wh-1.jpg
1764 ms
mach-55-purple-rdfl-2.jpg
1768 ms
breeze-57-purple-4wh-1.jpg
1806 ms
curv-purple-2wh-2.jpg
1808 ms
mach-55-red-rdfl-2.jpg
1814 ms
traffik-55-teal-4wh-2.jpg
1816 ms
curv-purple-rdfl-2.jpg
1957 ms
allstorm-brown-4wh-2.jpg
1960 ms
hawk4wh-blue-57__1_.jpg
2005 ms
pepper-67-silver-4wh-2.jpg
2008 ms
azure-lite-blue-backpack__1_.jpg
2007 ms
hexlite-plus-wine-4wh-2.jpg
2009 ms
curv-red-2wh-2.jpg
2152 ms
pump-55-maroon-4wh-2.jpg
2154 ms
slide-55-blue-2wh-2.jpg
2191 ms
widget_v2.132.js
25 ms
collect
108 ms
collect
134 ms
facepile.php
77 ms
roboto-regular-webfont.woff
1983 ms
zinger-11-red-backpack__1_.jpg
1982 ms
slide-55-burgandy-2wh-2.jpg
2012 ms
hawk4wh-red-57__1_.jpg
1347 ms
pergo-plus-50-navyblue-2wh-2.jpg
1125 ms
stronn-65-red-4wh-2.jpg
1165 ms
tango-65-purple-rdfl__1_.jpg
1166 ms
aztec-orange-2wh-2.jpg
1169 ms
aL63HcygAAVYuCCsAAA==
2 ms
zinger-4-purple-backpack__1_.jpg
1169 ms
vista-plus-60-navy-blue-rdfl-2.jpg
1177 ms
tierra-55-red-rdfl-2.jpg
1179 ms
breeze-57-red-4wh-1.jpg
1204 ms
zinger-11-brown-backpack__1_.jpg
1206 ms
tergo-55-maroon-2wh__1_.jpg
1204 ms
tango-65-red-rdfl__1_.jpg
1205 ms
tergo-55-blue-2wh__1_.jpg
1174 ms
zinger-11-navyblue-backpack__1_.jpg
1173 ms
traffik-55-nred-4wh-2.jpg
1203 ms
stylite-plus-red-4wh-2.jpg
1204 ms
aztec-50-purple-2wh-2.jpg
1205 ms
aztec-50-green-d-2.jpg
1204 ms
whirl-55-brown-2wh-1.jpg
1173 ms
slide-55-purple-2wh-2.jpg
1174 ms
revv-65-purple-rdfl-2.jpg
1202 ms
maasaimara-55-navyblue-4wh-2.jpg
1200 ms
zinger-8-navyblue-backpack__1_.jpg
1196 ms
zinger-4-red-backpack__1_.jpg
1195 ms
allstorm-black-4wh-2.jpg
1175 ms
curv-brown-2wh-2.jpg
1177 ms
aztec-orange-d-2.jpg
1203 ms
aztec-purple-d-2.jpg
1204 ms
aztec-green-2wh-2.jpg
1203 ms
zinger-4-grey-backpack__1_.jpg
1202 ms
zinger-4-yellow-backpack__1_.jpg
1177 ms
code-black-4wh-2.jpg
1179 ms
pepper-67-npurple-4wh-2.jpg
1204 ms
incom.png
1213 ms
search_icon.jpg
1180 ms
loader.gif
1179 ms
bx_loader.gif
1176 ms
controls_new.png
1175 ms
arrow-up-safari.jpg
1203 ms
slider-left.png
1202 ms
slider.png
1203 ms
pop_close.png
1202 ms
login-button-left.png
1173 ms
login-button-inner.png
1169 ms
login-button-right.png
1202 ms
print.css
203 ms
safari.in 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
safari.in SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Safari.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Safari.in 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.
safari.in
Open Graph description is not detected on the main page of Safari. 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: