5.2 sec in total
468 ms
4.2 sec
516 ms
Click here to check amazing Safari content for South Africa. Otherwise, check out these important facts you probably never knew about safari.com
Safaris and lodging throughout the African continent. Speak to one of our travel experts now to assist with planning the perfect safari holiday.
Visit safari.comWe analyzed Safari.com page load time and found that the first response time was 468 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
safari.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value16.2 s
0/100
25%
Value9.8 s
10/100
10%
Value1,900 ms
8/100
30%
Value0
100/100
15%
Value21.4 s
1/100
10%
468 ms
31 ms
107 ms
331 ms
6 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 61% of them (62 requests) were addressed to the original Safari.com, 7% (7 requests) were made to Apis.google.com and 5% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Safari.com.
Page size can be reduced by 170.1 kB (22%)
782.7 kB
612.6 kB
In fact, the total size of Safari.com main page is 782.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. 55% of websites need less resources to load. Images take 553.2 kB which makes up the majority of the site volume.
Potential reduce by 36.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. 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 36.2 kB or 78% of the original size.
Potential reduce by 21.8 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 61.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 61.6 kB or 51% of the original size.
Potential reduce by 50.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. Safari.com needs all CSS files to be minified and compressed as it can save up to 50.5 kB or 82% of the original size.
Number of requests can be reduced by 56 (59%)
95
39
The browser has sent 95 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 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.safari.com
468 ms
css
31 ms
style.css
107 ms
jquery.fancybox-1.2.6.css
331 ms
show_ads.js
6 ms
style-Red.css
1332 ms
shortcodes.css
1333 ms
jquery.min.js
83 ms
external-tracking.min.js
2335 ms
diggdigg-style.css
2337 ms
plusone.js
97 ms
jquery.cycle.all.min.js
207 ms
jquery.easing.1.3.js
311 ms
superfish.js
430 ms
jquery.fancybox-1.2.6.pack.js
431 ms
ctf_captcha.js
524 ms
ca-pub-2078872807231117.js
41 ms
zrt_lookup.html
35 ms
show_ads_impl.js
49 ms
body-bg.jpg
183 ms
logo-safari.png
279 ms
timthumb.php
601 ms
timthumb.php
666 ms
timthumb.php
903 ms
timthumb.php
764 ms
timthumb.php
862 ms
timthumb.php
959 ms
timthumb.php
1004 ms
timthumb.php
1056 ms
timthumb.php
1183 ms
timthumb.php
1183 ms
timthumb.php
1101 ms
timthumb.php
1152 ms
timthumb.php
1201 ms
timthumb.php
1250 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
80 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
81 ms
ads
104 ms
osd.js
5 ms
abg.js
23 ms
ga.js
41 ms
wr-bg.png
151 ms
header-bg.png
151 ms
cb=gapi.loaded_0
39 ms
ads
257 ms
menu-bg.png
117 ms
top-menu-linkbg.png
117 ms
secondary-menu-linkbg.png
117 ms
featured-bg.png
197 ms
featured-overlay.png
181 ms
featured-description2.png
180 ms
top-description-bg.png
210 ms
price.png
209 ms
hr-bg.png
208 ms
readmore-right.png
285 ms
readmore-left.png
286 ms
featured-left.png
313 ms
controller-bg-active.png
328 ms
controller-bg.png
321 ms
featured-right.png
327 ms
active-thumb-bg.png
355 ms
content-top.png
377 ms
main-bg.png
442 ms
entry-bg.png
476 ms
thumb-overlay.png
477 ms
price-small-bg.png
442 ms
hr2-bg.png
481 ms
listings-top.png
481 ms
listings-bg.png
501 ms
listings-title-top.png
515 ms
listings-title-bottom.png
516 ms
view-button.png
516 ms
listings-bottom.png
546 ms
widget-separator.png
588 ms
widget-title.png
598 ms
sidebar-bullet.png
604 ms
ads
423 ms
__utm.gif
66 ms
content-bottom.png
511 ms
aci.js
212 ms
cb=gapi.loaded_1
15 ms
fastbutton
145 ms
postmessageRelay
47 ms
m_js_controller.js
6 ms
api.js
48 ms
core:rpc:shindig.random:shindig.sha1.js
127 ms
2536007149-postmessagerelay.js
122 ms
favicon
127 ms
s
33 ms
googlelogo_color_112x36dp.png
115 ms
nessie_icon_tiamat_white.png
53 ms
x_button_blue2.png
80 ms
cb=gapi.loaded_0
49 ms
cb=gapi.loaded_1
48 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
163 ms
150 ms
213 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
3 ms
favicon
54 ms
255 ms
match
199 ms
safari.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
safari.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Safari.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Safari.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.
safari.com
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: