3.7 sec in total
84 ms
2.9 sec
689 ms
Click here to check amazing Bloom Saigon content for Vietnam. Otherwise, check out these important facts you probably never knew about bloom-saigon.com
We serve traditional, elegant fare, with a contemporary flair and no MSG. Housed in a beautifully restored French colonial villa down a dimly lit alley, BLOOM Restaurant Saigon serves you healthy aut...
Visit bloom-saigon.comWe analyzed Bloom-saigon.com page load time and found that the first response time was 84 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
bloom-saigon.com performance score
name
value
score
weighting
Value2.7 s
62/100
10%
Value12.3 s
0/100
25%
Value9.3 s
13/100
10%
Value11,910 ms
0/100
30%
Value1.5
0/100
15%
Value21.4 s
1/100
10%
84 ms
24 ms
36 ms
11 ms
106 ms
Our browser made a total of 175 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Bloom-saigon.com, 17% (29 requests) were made to Maps.googleapis.com and 15% (26 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Nebula.wsimg.com.
Page size can be reduced by 1.2 MB (7%)
17.0 MB
15.9 MB
In fact, the total size of Bloom-saigon.com main page is 17.0 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. 85% 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 15.4 MB which makes up the majority of the site volume.
Potential reduce by 210.9 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 210.9 kB or 78% of the original size.
Potential reduce by 30.3 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. Bloom Saigon images are well optimized though.
Potential reduce by 837.0 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 837.0 kB or 65% of the original size.
Potential reduce by 98.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. Bloom-saigon.com needs all CSS files to be minified and compressed as it can save up to 98.4 kB or 83% of the original size.
Number of requests can be reduced by 90 (55%)
164
74
The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bloom Saigon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 69 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.bloom-saigon.com
84 ms
css
24 ms
css
36 ms
site.css
11 ms
duel.js
106 ms
addthis_widget.js
13 ms
tcc_l.combined.1.0.5.min.js
66 ms
wejs
87 ms
jq.js
194 ms
social.share.js
171 ms
912798c55200ef64df6f591d5d2c9824
442 ms
40eb7caf7b5f3c2487c64751763dce6c
141 ms
WidgetEmbed-socialButtonBubbles
78 ms
20x28_green-21693-2.png
80 ms
cdswidSOCIAL-v21186289283a.css%20%27%29%3B
3 ms
cdswidgets_m-c-v2102084671a.js
112 ms
cdswidSOCIAL-v21186289283a.css
110 ms
util.instances.js
40 ms
util.model.js
127 ms
helper.js
127 ms
subNavigation.js
129 ms
facebookSDKHelper.js
90 ms
CGrugV3oJ92UQ-6yJivgVQ.ttf
12 ms
mapGenerator.js
110 ms
media.gallery.js
101 ms
cookiemanager.js
89 ms
iebackground.js
92 ms
fKnfV28XkldRW297cFLeqfesZW2xOQ-xsNqO47m55DA.ttf
32 ms
Hm1qjDlZpOdVXoa-QGE7_w.ttf
33 ms
L74890HNVnUypqWjqGUt1aCWcynf_cDxXwCLxiixG1c.ttf
33 ms
layers.e5ea973510bf60b3db41.js
63 ms
300lo.json
43 ms
browser.js
40 ms
util.fbSDKLoader.js
39 ms
util.window.js
38 ms
sh.8e5f85691f9aaa082472a194.html
24 ms
documentHelper.js
32 ms
googleMaps.js
100 ms
getClosestGeoLocation.js
138 ms
growl.js
127 ms
dfa0a5d82adcb3572c4c57fffd1c9e71
507 ms
wsb-slideshow-left-arrow.png
53 ms
wsb-slideshow-right-arrow.png
48 ms
wsb-slideshow-nav-arrows-sprt.png
47 ms
js
22 ms
sf.core.pkg.js
79 ms
common.js
4 ms
map.js
16 ms
util.js
16 ms
geocoder.js
15 ms
onion.js
28 ms
openhand_8_8.cur
20 ms
AuthenticationService.Authenticate
92 ms
GeocodeService.Search
94 ms
ViewportInfoService.GetViewportInfo
207 ms
stats.js
29 ms
controls.js
25 ms
all.js&version=v2.0
81 ms
widgets.js
21 ms
plusone.js
78 ms
app.css
75 ms
transparent.png
36 ms
css
31 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
123 ms
google4.png
99 ms
marker.js
89 ms
cb=gapi.loaded_0
114 ms
cb=gapi.loaded_1
154 ms
fastbutton
198 ms
mapcnt6.png
78 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
43 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
42 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
42 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
42 ms
sdk.js
72 ms
160 ms
tmapctrl.png
54 ms
cb_scout5.png
61 ms
xd_arbiter.php
91 ms
xd_arbiter.php
117 ms
ViewportInfoService.GetViewportInfo
128 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
50 ms
spotlight-poi.png
69 ms
postmessageRelay
94 ms
like.php
94 ms
cb=gapi.loaded_0
60 ms
cb=gapi.loaded_1
61 ms
08544b1fcac4e47f78223a34be53c9ac
292 ms
69bbe8b762a9229f736a5bad7e62c434
1429 ms
731837376ce5032dd239296859e1d6be
1095 ms
13caf1ab872bcdbe04a7ea08c8fdc59a
474 ms
11728df7e4cafe3fdbef300e0410139f
624 ms
8ca67aee8bc823c8e6d0a2a55a0ea362
920 ms
3fc2ddf3c700b881f1158f9f8f63dfb3
483 ms
a3508f5d1fb51d55053abcf64000de35
492 ms
6d3603400ccc8315735cc4170368a64b
566 ms
04946b4c6fcf9ce3243cca50f294e4ba
832 ms
b4b27d3ed6299f9b25841a86c5631de0
792 ms
0b38cab2f3f5f36f92bf286f307b0ab9
1261 ms
a070f853ab3d4126615e6f9c2d279014
948 ms
9c2d62466df12ee4b19ce683a1ea81c4
1156 ms
c59367d35520ea176b9cfe9ae533d873
1071 ms
3430009b0ba91236fd9a180381364396
1112 ms
e8d90ebda43d281b69dc4e880bc29d44
1481 ms
042c1783ddad62fb208b77afebbecf7a
1337 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
76 ms
page.php
240 ms
3193398744-postmessagerelay.js
84 ms
rpc:shindig_random.js
48 ms
TY3MhkXpWJ-.js
86 ms
LVx-xkvaJ0b.png
83 ms
vt
49 ms
vt
84 ms
vt
36 ms
vt
36 ms
vt
35 ms
vt
88 ms
vt
51 ms
vt
51 ms
vt
98 ms
vt
88 ms
vt
72 ms
vt
96 ms
vt
85 ms
vt
91 ms
vt
144 ms
vt
123 ms
jot
109 ms
cb=gapi.loaded_0
6 ms
LUdypCgtRlc.css
11 ms
46icGyCHNkx.css
15 ms
7UFpPvIym7D.css
28 ms
AQCoNaHeh00.css
26 ms
1kPfZUdGrka.js
31 ms
HQ1UKbUXIBt.js
30 ms
Qd7TTBR3F_S.js
19 ms
1dEEvSwLtg5.js
24 ms
b1o_4KKMvfn.js
68 ms
1l6pDeACLON.js
90 ms
TzWCmQ2GDUt.js
87 ms
k3HgkHYQ8wO.js
88 ms
yCfZpessXwm.js
110 ms
jWwyUJH0aOO.js
108 ms
12301491_865361046910825_452034669378149434_n.jpg
184 ms
10485239_860767467370183_8556304150533503920_n.jpg
34 ms
12800335_1708741349389579_3939930103145108145_n.jpg
37 ms
1914824_1062852910432062_2334921366274872898_n.jpg
37 ms
12274726_1018955728169267_6088821252011961885_n.jpg
77 ms
577423_121403887996243_770871534_n.jpg
38 ms
12804777_10153429708302584_4924615260549924509_n.jpg
38 ms
12662566_449132375286237_473871493076172572_n.jpg
98 ms
1918616_226628374359074_2565639715555890729_n.jpg
77 ms
12801421_538432509666543_9200751614312103916_n.jpg
101 ms
10348382_347704898716634_6407703127965904980_n.jpg
39 ms
12049484_10204665529627446_8565775156662682738_n.jpg
40 ms
735006_925594274220835_5151079167286236516_n.jpg
157 ms
10441403_922984254481837_2434071922008647962_n.jpg
105 ms
12821372_920728688040727_1542815544258504727_n.jpg
182 ms
12670798_917502548363341_7464185628396998473_n.jpg
158 ms
12419919_914023595377903_1271405875_n.jpg
107 ms
wL6VQj7Ab77.png
23 ms
s7jcwEQH7Sx.png
30 ms
GtIpNnEyqq_.png
29 ms
YzFEFmGRSUa.png
32 ms
e3Spc1mcUJw.png
29 ms
R9GKCzjAnbk.js
8 ms
AWWjhOengNF.js
8 ms
YnSasnyq68i.js
8 ms
kQf_jlUv-kX.js
11 ms
20x28_green-21693-2.png
27 ms
ss4.5.gif
28 ms
grayArrowLeft.gif
25 ms
event
116 ms
like.php
58 ms
TY3MhkXpWJ-.js
8 ms
bloom-saigon.com accessibility score
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
Buttons do not have an accessible name
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.
bloom-saigon.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
bloom-saigon.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 Bloom-saigon.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 Bloom-saigon.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.
bloom-saigon.com
Open Graph data is detected on the main page of Bloom Saigon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: